PR Description: "In the AdvancedPreviewScene, the skysphere appears to be casting shadows. This causes the directional light to not affect the current asset and prevents the user from properly seeing their changes. This is most obvious with the material editor as well as the static mesh editor, where the asset would appear dark due to only sky lighting being present. I have reproduced this when using Lumen with hardware ray tracing and it appears to be caused by Lumen tracing against backfaces. I have not attempted to reproduce this without hardware ray tracing due to the fact that the fix is simple and won't affect non hardware ray tracing. The sky didn't have the shadows disabled because previous forms of lighting ignored backfaces. But now, with backfaces being traced against, this seems like a good idea."
#jira UE-173255
#rb ola.olsson
#fyi krzysztof.narkowicz
#preflight
PR #9965
[CL 23788293 by Kevin Ortegren in ue5-main branch]
The four places this applies include UEditorEngine::Tick, UGameEngine::Tick, FAdvancedPreviewScene::Tick, and FPreviewScene::UpdateCaptureContents. The last example is called from FBlueprintEditor::Tick and FThumbnailPreviewScene::Tick.
The counter-example is "UEditorEngine::BuildReflectionCaptures", which doesn't appear to be called anywhere from a Tick related function. It's called in startup functions, various commands, and as part of static lighting generation. If we run into further validation errors, we could add a flag to that function to differentiate those cases. Even though there's only one counter-example, I figured it was best to err on the side of not changing behavior of client code that may also be using the function, so by default "bInsideTick" is set to false.
#jira UE-153604
#rb mihnea.balta jason.nadro
#rnx
#preflight 628d89082f2409bc1e08a42e
[CL 20362380 by jason hoerner in ue5-main branch]
This enables the use of path tracing for the material editor and static mesh editors.
#rb Juan.Canada
#preflight 620c5818492761fc5ca38895
[CL 19009187 by chris kulla in ue5-main branch]
The dataprep one doesn't have to save if it can't. It recreate the setup on the next boot.
The collision one is in the project setting where there is a visual warning if the ini file is in a read only mode.
#jira UE-132811
#rb JeanMichel.Dignard
#preflight 617c0c625dbdbc00016ea668
#ushell-cherrypick of 17984359 by Julien.StJean
#ROBOMERGE-AUTHOR: geoff.evans
#ROBOMERGE-SOURCE: CL 18006564 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v885-17909292)
[CL 18006602 by geoff evans 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]
This represents UE4/Main @17774255, Release-5.0 @17791557 and Dev-PerfTest @17789485
[CL 17794212 by aurel cordonnier in ue5-release-engine-test branch]
- The profile combo is only visible when the user has more than one profile
- This was added to the Material Editor, the Static Mesh Editor and Niagara Editor.
#jira UETOOL-2775 Add preview scene background profile dropdown to asset editor vieport toolbar.
#rb Lauren.Barnes, Brooke.Hubert
#preflight 6130c00617a8610001b8ba61
#ROBOMERGE-SOURCE: CL 17402767 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v865-17346139)
[CL 17402787 by patrick laflamme in ue5-release-engine-test branch]
#fix hacky fix, adding config UProperty, to get the mutable CDO of UAssetViewerSettings transact, as its not in a package/saved
#jira UE-100441
#rb Thomas.Sarkanen
#ROBOMERGE-SOURCE: CL 16672046 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v834-16658389)
[CL 16672102 by jurre debaare in ue5-release-engine-test branch]
#fix take number of profiles-1 instead of just number of profiles when generating profile name
#jira UE-89146
#rb Thomas.Sarkanen
#ROBOMERGE-SOURCE: CL 16672040 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v834-16658389)
[CL 16672097 by jurre debaare in ue5-release-engine-test branch]
Refactored FindField into FindUField and FindFProperty to avoid confusion caused by the fact that FindField<UField> will no longer return FProperties.
#jira UE-90683
#rb Steve.Robb
#tests Basic editor functionality test, cooked and ran PC client and server, bot soak tests for two hours
#ROBOMERGE-OWNER: robert.manuszewski
#ROBOMERGE-AUTHOR: robert.manuszewski
#ROBOMERGE-SOURCE: CL 12190998 in //UE4/Release-4.25/... via CL 12190999
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v661-12148976)
[CL 12191300 by robert manuszewski in Main branch]
#rb none
#ROBOMERGE-OWNER: matt.kuhlenschmidt
#ROBOMERGE-AUTHOR: matt.kuhlenschmidt
#ROBOMERGE-SOURCE: CL 11382968 via CL 11382988 via CL 11382990
#ROBOMERGE-BOT: (v654-11333218)
[CL 11383722 by matt kuhlenschmidt in Main branch]
