The logic in DCRA related to the viewport manager has been slightly reworked: the viewport manager is only created when it needs to be used for rendering.
#jira UE-195151
#rb Alejandro.Arango, Vitalii.Boiko
[CL 27885668 by peter tarasenko in ue5-main branch]
[FYI] sara.schvartzman
Original CL Desc
-----------------------------------------------------------------
RigVM: Remove unnecesary includes
#rb trivial
#rnx
[CL 27879800 by sara schvartzman in ue5-main branch]
- Remove force OnDemand clipping when using a Text Scroll Style
[REVIEW] [at]daren.cheng, [at]vincent.gauthier
[CL 27875549 by jc authier in ue5-main branch]
- Remove specialized Audition object in favor of directly using UMetaSoundSource for Source builders
#rb phil.popp
#jira UE-194159
[CL 27861100 by rob gay in ue5-main branch]
* Fixed observer not being called when batch adding entities with tags but not fragments that overlap the current observer set
* Fixed observer not being called when single entity added with archtype that contains an observed tag or fragment
* Fixed observer not being called when single observed fragment added to entity
* Fixed observer not being called when single entity removed that has archtype containing observed tag or fragment
* Fixed observer not being called when single observed tag or fragment removed from entity
#rb Mieszko.Zielinski
#jira UE-195269, UE-181474
[CL 27854142 by logan buchy in ue5-main branch]
When handling these operations, as triggered by commands, we assum the archetype-less entities have been reserved and never check it. This CL adds some checking so that we know when it happens in the future, but also the CL changes how we treat invalid entities while creating `FMassArchetypeEntityCollectionWithPayload`, which is the tool commands are using to batch together updates to diverse collections of entities.
This fix has been prompted by project-specific code issuing commands outside of Mass processing, and before Mass processing actually starts there's gameplay code that synchronously kills off relevant entities. That behavior is not recommended and the project-side code will be updated, but Mass needs to handle this case gracefully.
[CL 27833407 by mieszko zielinski in ue5-main branch]
