Moving conditions allowing the property to take effect from ARecastNavMesh::PostInitProperties() to ARecastNavMesh::PostLoad() and delaying the check to discard navdata if there is no navigation system yet.
Removing previous ShouldDiscardSubLevelNavData() function that would fallback to read value from NavSysCDO when there is no navigation system.
#rb Yoan.StAmant, Maxime.Mercier
#jira UE-113463
[RN] fix Warning: UNavigationSystemV1 bShouldDiscardSubLevelNavData property was not working in some cases. With this fix navdata from sublevel will be properly discarted if the property is true (it's default value).
#preflight 62323fb4736af8e0822c951b
#ROBOMERGE-AUTHOR: aris.theophanidis
#ROBOMERGE-SOURCE: CL 19412570 via CL 19414029 via CL 19427618 via CL 19427717
#ROBOMERGE-BOT: UE5 (Release-Engine-Staging -> Main) (v930-19419903)
[CL 19429581 by aris theophanidis in ue5-main 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]
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]
#rb johan.torp
GetLinkerUE4Version renamed to GetLinkerUEVersion
#ROBOMERGE-SOURCE: CL 15859222 in //UE5/Release-5.0-EarlyAccess/...
#ROBOMERGE-BOT: STARSHIP (Release-5.0-EarlyAccess -> Main) (v786-15839533)
[CL 15859586 by mark lintott in ue5-main branch]
This was caused by the unwanted and undefined behavior of passing fltmax to some int flags (causing flags to SkipStringPulling)
#rb Yoan.StAmant
#jira UE-88980
#jira UE-88035
Integration from CL 11616045
[CL 11657720 by Aris Theophanidis in Main branch]
#rnx
#rb none
#ROBOMERGE-OWNER: ryan.durand
#ROBOMERGE-AUTHOR: ryan.durand
#ROBOMERGE-SOURCE: CL 10869210 via CL 10869511 via CL 10869900
#ROBOMERGE-BOT: (v613-10869866)
[CL 10870549 by ryan durand in Main branch]
ANavigationData now marks package as dirty when rebuilding
[at]daniel.lamb [at]sebastien.lussier
#rb daniel.lamb, sebastien.lussier
#ROBOMERGE-OWNER: Yoan.StAmant
#ROBOMERGE-AUTHOR: yoan.stamant
#ROBOMERGE-SOURCE: CL 10309310 via CL 10309311
#ROBOMERGE-BOT: (v593-10286020)
[CL 10309444 by Yoan StAmant in Main branch]
Exposing the minimum CostLimit parameter in NavigationTestingActor
Renaming MaxCost to CostLimit
[at]Guillaume.Guay [at]Maxime.Mercier
#jira UE-82572
#ROBOMERGE-SOURCE: CL 10055783 via CL 10055784
#ROBOMERGE-BOT: (v565-10026848)
[CL 10055786 by aris theophanidis in Main branch]
DetourNavMeshQuery -> Fix issue in updateSlicedFindPath not behaving like findPath (missing check for DT_UNWALKABLE_POLY_COST)
Looking forward to merge those or to make sure that the NavigationTestingActor uses the same pathfinder to generate its path than the one use to display debug steps
[at]Mieszko.Zielinski [at]Maxime.Mercier [at]Mikko.Mononen
#jira UE-82572
#ROBOMERGE-SOURCE: CL 10015638 via CL 10015644
#ROBOMERGE-BOT: (v562-10004402)
[CL 10015651 by aris theophanidis in Main branch]
[at]Ryan.Gerleve, [at]Brian.Bekich
#rb None
#ROBOMERGE-OWNER: jon.nabozny
#ROBOMERGE-AUTHOR: jon.nabozny
#ROBOMERGE-SOURCE: CL 9290108 via CL 9290249
#ROBOMERGE-BOT: (v452-9288972)
[CL 9290520 by jon nabozny in Main branch]
#rb none
[at]Stephen.Holmes, [at]Mikko.Mononen, [at]Yoan.StAmant
#ROBOMERGE-SOURCE: CL 9037487 via CL 9043823 via CL 9044034
#ROBOMERGE-BOT: (v443-9013191)
[CL 9047329 by mieszko zielinski in Main branch]
While modifying NavigationData.cpp I've refactored all UE_LOG into UE_VLOG_UELOG for better vislog coverage
#rb Yoan.StAmant, Stephen.Holmes, Mikko.Mononen
[at]Yoan.StAmant, [at]Stephen.Holmes, [at]Mikko.Mononen
#ROBOMERGE-SOURCE: CL 8974874 via CL 8974876 via CL 8974878
#ROBOMERGE-BOT: (v441-8974111)
[CL 8974880 by mieszko zielinski in Main branch]
#rb yoan.stamant, mieszko.zielinski
#ROBOMERGE-SOURCE: CL 7935933 via CL 7935935 via CL 7939399
#ROBOMERGE-BOT: (v391-7919777)
[CL 7939564 by guillaume guay in Main branch]
Notable changes:
- Added FNavigationOctreeController that wraps up what used to be NavigationSystemV1's navoctree-related logic
- Added FNavigationDirtyAreasController that wraps up what used to be NavigationSystemV1's DirtyAreas-related logic
- Added FNavigationDataHandler that is a helper struct that wraps up what used to be NavigationSystemV1's logic related to operation involving both navoctree and dirty areas
- Deprecated both FNavDataConfig.NavigationDataClass and FNavDataConfig.NavigationDataClassName and replaced them with a single NavDataClass property
- FNavigationOctree is not responsible for hashing element objects and storing their ElementId
- NavOctree elements how know about the octree they belong to (via a member property).
[at]Yoan.StAmant, [at]Maxime.Mercier, [at]Guillaume.Guay
#rb Yoan.StAmant
#ROBOMERGE-OWNER: mieszko.zielinski
#ROBOMERGE-AUTHOR: mieszko.zielinski
#ROBOMERGE-SOURCE: CL 7249089 via CL 7262555
#ROBOMERGE-BOT: (v369-7254125)
[CL 7262559 by mieszko zielinski in Main branch]
