#rb header and class name replacement
#ROBOMERGE-AUTHOR: lauren.barnes
#ROBOMERGE-SOURCE: CL 20078276 via CL 20078825
#ROBOMERGE-BOT: UE5 (Release-Engine-Staging -> Main) (v943-19904690)
[CL 20106316 by lauren barnes in ue5-main branch]
*) 'Overview' shows skin cache on/off, recompute tangents on/off
*) 'Memory' shows skin cache memory consumption per sk mesh, includes RT if sk mesh uses a separate RT entry
*) 'RayTracingLODOffset` shows RT LOD index offset from raster LOD index
#jira UE-136542
#rb jeremy.moore
#preflight 622bb12b902b7ca699df8755
[CL 19383862 by Josie Yang in ue5-main branch]
Lit->Lumen
Added Lit->Lumen submenu with 4 view modes - Lumen Scene, Lumen Reflection View, Lumen Surface Cache and Overview:
* Lumen Scene - same as ShowFlags->VisualizeLumenScene. Visualizes Lumen scene representation in highest possible quality, with highest possible view distance
* Lumen Reflection View - Lumen Scene, but with current reflections settings. Basically represents how things look in the reflections
* Lumen Surface Cache - visualizes surface cache and marks with pink missing surface cache coverage
* Overview - 3 Lumen view mode tiles, overlaid on top of normal view
Show->Lumen
Added Show->Lumen submenu with 6 flags, which allow to disable specific trace types (screen space, detail, global, far field), disable secondary bounces (radiosity) and disable Screen Space Directional Occlusion.
Show->Visualize
Removed �Lumen Scene� (replaced by Lit->Lumen->Lumen Scene view mode) and �Lumen Global Illumination� (replaced by r.Lumen.Visualize.IndirectDiffuse) from
Advanced visualization modes are accessible through r.Lumen.Visualize.Mode, which overrides current Lit->Lumen-> settings.
Misc changes:
* Renamed VisualizeLumenScene* to LumenVisualize*
* Moved shared visualize parameters to LumenVisualize.h
* Lumen HWRT visualize now uses same ray footprint as SWRT visualize
* Replaced HALF_WORLD_MAX with Lumen::MaxTracingEndDistanceFromCamera and Lumen::MaxTraceDistance in preparation for the LWC WORLD_MAX changes
#rb Patrick.Kelly, Daniel.Wright
#preflight 61e73339b56c33b8ecf753b2
#ROBOMERGE-AUTHOR: krzysztof.narkowicz
#ROBOMERGE-SOURCE: CL 18658215 in //UE5/Release-5.0/... via CL 18658227 via CL 18658249
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v900-18638592)
[CL 18658268 by krzysztof narkowicz in ue5-main branch]
For each pixel it shows the worst case missing mip level in all of the virtual textures sampled at that pixel.
Useful to analyze where late virtual texture page streaming is happening.
#rb ben.ingram
#preflight 615b5ecb255462000117288c
#lockdown michal.valient
#ROBOMERGE-OWNER: jon.nabozny
#ROBOMERGE-AUTHOR: jeremy.moore
#ROBOMERGE-SOURCE: CL 17716764 via CL 17979410 via CL 18366649 via CL 18366731
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18366789 by jon nabozny in ue5-release-engine-test branch]
This permutation will allow the path tracer to evolve independently from other RT passes in the engine. First end-user visible feature is that we disable RayTracingQualitySwitch for this permutation (so that path tracing can see the "full" material quality).
Introduce r.PathTracing cvar to guard the feature so that projects that don't need this functionality don't have to pay for the extra permutation.
Move raytracing clip/ddx/ddy into Common.ush
#jira UE-72537
#rb Patrick.Kelly, Yuriy.ODonnell
#preflight 60a7339365d94d0001bce99d
[CL 16415068 by chris kulla in ue5-main branch]
- Overhauled in viewport toolbar
- Updated active viewport outline and hidden tab dock icons
#rb none
[CL 13307248 by Matt Kuhlenschmidt in ue5-main branch]
#rnx
#ROBOMERGE-OWNER: rex.hill
#ROBOMERGE-AUTHOR: rex.hill
#ROBOMERGE-SOURCE: CL 12382023 via CL 12382025 via CL 12390417
#ROBOMERGE-BOT: (v671-12333473)
[CL 12392050 by rex hill in Release-Engine-Staging branch]
Together with cl 11724687 this saves quite a lot of shaders
#rb Yujiang.Wang, rolando.caloca
#ROBOMERGE-OWNER: jonas.meyer
#ROBOMERGE-AUTHOR: jonas.meyer
#ROBOMERGE-SOURCE: CL 12197646 via CL 12198192
#ROBOMERGE-BOT: (v662-12191386)
[CL 12198195 by jonas meyer in Main branch]
#rb none
#rnx
#ROBOMERGE-OWNER: rex.hill
#ROBOMERGE-AUTHOR: rex.hill
#ROBOMERGE-SOURCE: CL 11511340 via CL 11514106 via CL 11514347
#ROBOMERGE-BOT: (v654-11333218)
[CL 11517218 by rex hill in Main branch]
#rnx
#rb none
#ROBOMERGE-SOURCE: CL 10869241 via CL 10869527 via CL 10869904
#ROBOMERGE-BOT: (v613-10869866)
[CL 10870586 by ryan durand in Main branch]
New feature: Added the capability of adding Radio buttons to the submenu main button (not only to its entries).
This CL is the first of 2 CLs that introduce multiple improvements on the "View Mode" menu of the Viewport, including a new feature request from JIRA UE-81469. However, we isolate this particular new feature into an isolated CL given that it can be applicable anywhere in the Editor, not only for "View Mode".
Issue: If any subcategory of "View Mode" was chosen, the user could not know in which category it was located (unless the user manually looked into each category until he found the selected one).
Solution: Added the checked functionality (with a radio button) to each one of the categories, behaving similarly to any subcategory. This way, both the radio button of the category and the one from the specific subcategory will be checked simulatenously.
More technical details:
Adding this functionality to "View Mode" means adding the functionality of "FUIAction::FIsActionChecked" into "AddSubMenu", which includes modifications to "MultiBox", "SMenuEntryBlock", and "MultiBoxBuilder".
1) We are changing a submenu so it has a radioButton
2) To specify a radio button a developer has to use a different API that includes a delegate (FUIAction) to say if it should be checked or not before this CL
3) The different API for AddSubMenu was not passing along the command list for that child submenu to use
4) The updated code now passes the command list along for the child submenu to use
#rb rex.hill
[CL 10228324 by Gines Hidalgo in Dev-Editor branch]
