Add the ability to enable auto compile when adding new C++ classes.
Fixed user feedback issues when adding new C++ classes.
#rb joe.kirchoff
#rnx
#jira UE-116958
#preflight 60cb2e884ce02c0001d278c1
[CL 16703582 by Tim Smith in ue5-main branch]
- All shared ptr/ref are being changed to default ESPMode::ThreadSafe and ESPMode::Fast is being deprecated, so this migration path is not needed.
#jira FORT-342384
[CL 16090866 by Chris Varnsverry in ue5-main branch]
PS already has a permutation (bAtomicWrites) so this primarily affects offline compilation
Leaving the function of NonNaniteVSM the same for now to minimize the surface area of the change, but the shader and other logic can be simplified in the future
NonNaniteVSM can become a dynamic debug cvar in the future once we are happy this is working
#jira UETOP-1088
#lockdown graham.wihlidal
#rb ola.olsson, krzysztof.narkowicz
[FYI] nick.whiting
#ROBOMERGE-SOURCE: CL 16057407 in //UE5/Release-5.0-EarlyAccess/...
#ROBOMERGE-BOT: STARSHIP (Release-5.0-EarlyAccess -> Main) (v789-15992632)
[CL 16061153 by andrew lauritzen in ue5-main branch]
- Moves CoreOnline headers into their own module
#jira UE-113427
#fyi Matt.Peters
#tests built EdTest, QAGame, and one internal project in DevEd Win64
[CL 16036320 by Chris Varnsverry in ue5-main branch]
Enable non-nanite VSMs by default in new projects in UE5
Submitted on behalf of Ola.Olsson.
#rb andrew.lauritzen
#ROBOMERGE-OWNER: andrew.lauritzen
#ROBOMERGE-AUTHOR: andrew.lauritzen
#ROBOMERGE-SOURCE: CL 15920930 in //UE5/Release-5.0-EarlyAccess/...
#ROBOMERGE-BOT: STARSHIP (Release-5.0-EarlyAccess -> Main) (v786-15839533)
#ROBOMERGE-CONFLICT from-shelf
[CL 15922402 by andrew lauritzen in ue5-main branch]
#ROBOMERGE-SOURCE: CL 15699268 in //UE5/Release-5.0-EarlyAccess/...
#ROBOMERGE-BOT: STARSHIP (Release-5.0-EarlyAccess -> Main) (v781-15675533)
[CL 15699295 by daniel wright in ue5-main branch]
* These map to r.DynamicGlobalIlluminationMethod and r.ReflectionMethod under the hood
* Removed r.ssgi.enable. Projects with r.ssgi.enable=1 lose SSGI being enabled, because there�s no way to do backward compatibility on cvars.
* Removed r.LumenScene. Lumen GI and Reflections are now enabled independently and Lumen Scene will be set up if either feature is enabled.
Setting �Dynamic Global Illumination Method� to Lumen in Project Settings automatically sets �Reflection Method� to Lumen and enables �Generate Mesh Distance Fields�, so you only have to change one setting to convert your project to Lumen.
Newly created projects have:
* r.GenerateMeshDistanceFields=True. Needed for Lumen Software tracing. Note this means all new projects have Mesh Distance Field memory overhead by default.
* r.DynamicGlobalIlluminationMethod=1 (Lumen)
* r.ReflectionMethod=1 (Lumen)
Added GI method and Reflection method overrides to Post Process Volume, and new Final Gather Quality and Reflections Quality for Lumen.
Changed the default for r.DistanceFields.DefaultVoxelDensity from .1 to .2, for all projects. This is needed for good software tracing quality with Lumen.
Lumen GI operates on all lights, regardless of Mobility. Precomputed shadowing on Stationary lights are ignored, and Lumen will fall back to SDF tracing to solve shadowing for these.
When Lumen GI is enabled, lightmap lighting is discarded in the shader. This breaks Static lights with lighting built, because their direct lighting is only stored in the lightmap. A future change will be needed to render Static Lights when Lumen GI is enabled.
NeedsVelocityDepth will be true on any platform that supports Lumen or Ray Tracing. Lumen needs Velocity Depth but doesn�t have a readonly cvar to use to modify shader compilation.
#ROBOMERGE-SOURCE: CL 15321505 in //UE5/Release-5.0-EarlyAccess/...
#ROBOMERGE-BOT: STARSHIP (Release-5.0-EarlyAccess -> Main) (v771-15082668)
[CL 15321508 by daniel wright in ue5-main branch]
