(with some extra const)
#rb Maxime.Mercier
#preflight 61fc2b043b22793ca369a98d
#ROBOMERGE-AUTHOR: aris.theophanidis
#ROBOMERGE-SOURCE: CL 18852387 via CL 18852907 via CL 18853018 via CL 18854025 via CL 18854798
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v910-18824042)
[CL 18854824 by aris theophanidis in ue5-main branch]
#jira UE-122078
#rb Andrew.Davidson, Colin.McGinley
#preflight standard build
#ROBOMERGE-AUTHOR: fred.kimberley
#ROBOMERGE-SOURCE: CL 18817999 in //UE5/Release-5.0/... via CL 18818012 via CL 18822871
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v910-18824042)
[CL 18824721 by fred kimberley in ue5-main branch]
Submitted on behalf of fred.kimberley
#rb andy.davidson
#preflight 61f8729a5a026d2d19bb9ca6
#preflight 61f87a025a026d2d19be76ed
#ROBOMERGE-OWNER: andrew.davidson
#ROBOMERGE-AUTHOR: andrew.davidson
#ROBOMERGE-SOURCE: CL 18802361 in //UE5/Release-5.0/... via CL 18802891 via CL 18821557
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v908-18788545)
[CL 18821641 by andrew davidson in ue5-main branch]
Also removed two unnecessary tags in the nav mesh code.
The new LLM tags mirror the existing STAT_Navigation_CollisionTreeMemory functionality.
#preflight 61e9be95f160213534a34b64?step=5a6e
#ROBOMERGE-OWNER: stephen.holmes
#ROBOMERGE-AUTHOR: stephen.holmes
#ROBOMERGE-SOURCE: CL 18680481 via CL 18681738 via CL 18682025 via CL 18682845 via CL 18682857 via CL 18682876
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v902-18672795)
[CL 18682897 by stephen holmes in ue5-main branch]
In the ANavigationData::RebuildAll() flow, NavDataGenerator->RebuildAll() is called and it releases the detour navmesh to make a new one. In that flow, the new dtNavMesh params where never sets, causing m_bvQuantFactor to be 0 and navmesh queries to fail.
(not that RebuildAll() flow can be called automatically when bNavigationAutoUpdateEnabled is enabled in editor)
#jira UE-139610
#rb Stephen.Holmes
#preflight 61e9643e276892ce10921113
#ROBOMERGE-AUTHOR: aris.theophanidis
#ROBOMERGE-SOURCE: CL 18673754 in //UE5/Release-5.0/... via CL 18674060 via CL 18674106
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v902-18672795)
[CL 18674160 by aris theophanidis in ue5-main branch]
Enable usage of source control provider when building WP navmesh
Fix issue with deleted packages being added to source control
Make sure WP navmesh actor in WP levels remains empty (data is provided by navmesh chunk actors)
#jira UE-114032
#rb Yoan.StAmant
#robomerge 5.0
#preflight 61e839b93778a195dee90f08
[CL 18659327 by Aris Theophanidis in ue5-main branch]
[FYI] Stephen.Holmes
Original CL Desc
-----------------------------------------------------------------
Memory optimizations for Recast (Detour). I used UE_LOG in recast as it's already there. Also I only added [at]UE BEGIN [at]UE END for the big stuff as a hint that its been changed in case of issues.
#ROBOMERGE-AUTHOR: stephen.holmes
#ROBOMERGE-SOURCE: CL 18417786 in //UE5/Release-5.0/... via CL 18417810
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v897-18405271)
[CL 18417812 by stephen holmes in ue5-release-engine-test branch]
- Deprecated enum EActorGridPlacement and replaced AActor::GridPlacement by bIsSpatiallyLoaded.
- It makes more sense from a user perspective to set an actor as "non-spatially loaded" instead of "always loaded", especially with data layers.
- If we ever need it, having the possibility to set actors to use their location or bounds to go in the grid will be a per-grid setting.
#rb richard.malo, sebastien.lussier
#preflight 61af8bf10e59fd0ab0f93cc4
#ROBOMERGE-AUTHOR: jeanfrancois.dube
#ROBOMERGE-SOURCE: CL 18395825 in //UE5/Release-5.0/... via CL 18395836
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v896-18170469)
[CL 18395850 by jeanfrancois dube in ue5-release-engine-test branch]
1. Nanite meshes are not longer marked as always visible, and will go through the standard rendering culling / pipeline.
2. Add coarse frustum culling using the already existing scene octree.
3. Remove Distance visibility bit array, and converted only usage to using the visibiliity map. (Spoke with Kenzo about this, the original was put in due to differences between distance a vis flags, but this has been fixed)
4. Optimized Frustum culling methods across the board.
[at]Graham.Wihlidal [at]krzysztof.narkowicz [at]andrew.firth
#preflight 6137e0d1d9c85a00015375cb
#ROBOMERGE-OWNER: jon.nabozny
#ROBOMERGE-AUTHOR: brandon.dawson
#ROBOMERGE-SOURCE: CL 17459502 via CL 17911378 via CL 18360795 via CL 18361127
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18361363 by jon nabozny in ue5-release-engine-test branch]
- usable to understand (per navmesh) how many tiles we are dirtying and what the biggest offenders are
[REVIEW] [at]Loic.Devaux, [at]Guillaume.Guay, [at]Mieszko.Zielinski, [at]Aris.Theophanidis
[FYI] philippe.painchaud, Felix.Laplante, Patrick.Carroll, Guillaume.Morreel, Josselin.Francois
#ROBOMERGE-AUTHOR: luciano.ferraro
#ROBOMERGE-SOURCE: CL 18299019 via CL 18300916 via CL 18300964 via CL 18301452 via CL 18301480
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18301490 by luciano ferraro in ue5-release-engine-test branch]
