This represents UE4/Main @18073326, Release-5.0 @18081140 and Dev-PerfTest @18045971
[CL 18081471 by aurel cordonnier in ue5-release-engine-test branch]
This represents UE4/Main @17911760, Release-5.0 @17915875 and Dev-PerfTest @17914035
[CL 17918595 by aurel cordonnier in ue5-release-engine-test branch]
#ROBOMERGE-SOURCE: CL 17405434 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v865-17346139)
[CL 17405547 by matt kuhlenschmidt in ue5-release-engine-test branch]
- Keep a reference to the data layers actor in the level to ensure initial loading.
- Always create a data layers actor when creating a new partitioned world.
#rb richard.malo
[CL 16183601 by JeanFrancois Dube in ue5-main branch]
- Keep a reference to the data layers actor in the level to ensure initial loading.
- Always create a data layers actor when creating a new partitioned world.
#rb richard.malo
#preflight 608c0838a0d23c000116164c
[CL 16168385 by JeanFrancois Dube in ue5-main branch]
GetViewports, GetActiveViewport, SetAllowsCinematicControl, GetAllowsCinematicControl.
PilotLevelActor, EjectPilotLevelActor, EditorSetGameView, EditorGetGameView now take an optional config key to indicate which viewport should be set/get. Default is none, which acts on the active viewport (no change in existing behavior)
#jira UE-108941
#rb brooke.hubert
[CL 15522119 by Max Chen in ue5-main branch]
SActorDetails now operates on a given UTypedElementSelectionSet (removing its dependence on the global selection), and also operates based on the list of selected top-level elements rather than the selected actors.
UTypedElementDetailsInterface provides the interface needed for an element to be used with the details panel, with ITypedElementDetailsObject being the underlying glue object.
The ITypedElementDetailsObject instance will exist as long as the details panel is using it, so gives a lifetime to potentially synthesized UObject instances that are created purely for editing (eg, on instances).
This change removes almost all direct use of UpdateFloatingPropertyWindowsFromActorList, with only a single use-case in the reference viewer remaining.
Most code was already using UpdateFloatingPropertyWindows anyway, which now emits an extra OnElementSelectionChanged event in addition to its previous OnActorSelectionChanged event.
UpdateFloatingPropertyWindowsFromActorList now only emits an OnOverridePropertyEditorSelection event and no longer emits an OnActorSelectionChanged event.
SActorDetails is updated from both OnElementSelectionChanged and OnOverridePropertyEditorSelection, with the OnActorSelectionChanged event remaining for backwards compatability with existing code.
#jira
#rb Chris.Gagnon, Brooke.Hubert
[CL 15037524 by Jamie Dale in ue5-main branch]
