[REVIEW] [at]Maxime.Mercier
#rb Maxime.Mercier
#jira UE-88298
#ROBOMERGE-SOURCE: CL 11294460 via CL 11294746 via CL 11295748 via CL 11295817
#ROBOMERGE-BOT: (v647-11244347)
[CL 11295887 by aris theophanidis in Main branch]
Allow to display internal debug data at different navmesh generation steps for a selected tile
Ignore height filtering while displaying the navmesh around camera position
[REVIEW] [at]Mieszko.Zielinski [at]Mikko.Mononen
#rb Mikko.Mononen
#jira UE-86730
#ROBOMERGE-SOURCE: CL 11285125 via CL 11285129 via CL 11285132
#ROBOMERGE-BOT: (v647-11244347)
[CL 11285135 by aris theophanidis in Main branch]
Fix result reserve count to prevent unnecessary allocations on the addition of the last item
Limit the number of loop iteration to the path node count
[at]Yoan.StAmant [at]Mieszko.Zielinski [at]Mikko.Mononen
#ROBOMERGE-SOURCE: CL 10951654 via CL 10951658 via CL 10951660
#ROBOMERGE-BOT: (v632-10940481)
[CL 10951661 by aris theophanidis in Main branch]
This fixes an issue where navmesh would be wrongly generated on steep slope (as a result, agents would try to reach unreachable locations).
[at]Mikko.Mononen
#rb Mikko.Mononen
#ROBOMERGE-SOURCE: CL 10933548 via CL 10933552 via CL 10933555
#ROBOMERGE-BOT: (v626-10872990)
[CL 10933561 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]
One side effect is that NavModifier aligned wiith geometry woudl not mark the navmesh even when taking into account of the cellheight.
[at]Mieszko.Zielinski [at]Mikko.Mononen [at]Maxime.Mercier [at]Yoan.StAmant
#rb Maxime.Mercier Yoan.StAmant
#jira UE-82571
#ROBOMERGE-SOURCE: CL 10656649 via CL 10656891
#ROBOMERGE-BOT: (v609-10634694)
[CL 10656896 by aris theophanidis in Main branch]
Addition property bRejectNavmeshUnderneath on PrimitiveComponent
The flag gets set in the FCompositeNavModifier and is read when rasterizing the geometry
When set, the triangles are rasterize as solid columns going to the min level of the solid heightfield preventing navmesh generation under them
[REVIEW] [at]Mieszko.Zielinski [at]Mikko.Mononen
#rb [at]Mikko.Mononen
#jira UE-82571
#ROBOMERGE-OWNER: aris.theophanidis
#ROBOMERGE-AUTHOR: aris.theophanidis
#ROBOMERGE-SOURCE: CL 10335671 via CL 10335674
#ROBOMERGE-BOT: (v594-10333955)
[CL 10353890 by aris theophanidis in Main branch]
#rb Mieszko.Zielinski Aris.Theophanidis Yoan.StAmant
#ROBOMERGE-SOURCE: CL 10092452 via CL 10092454
#ROBOMERGE-BOT: (v574-10069753)
[CL 10092455 by mikko mononen 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]
Replicated from CL# 7924370.
#rb none
#ROBOMERGE-OWNER: steve.robb
#ROBOMERGE-AUTHOR: steve.robb
#ROBOMERGE-SOURCE: CL 9279060 via CL 9279063
#ROBOMERGE-BOT: (v443-9013191)
[CL 9279836 by steve robb in Main branch]
Instead, if the region count is 0 we simply return as 'success' since no issues occured. The rest of nav generaiton process is handling this result properly.
This fix is the exact same fix done to DetourTileCacheRegion.cpp in 5624049.
#rb none
#ROBOMERGE-SOURCE: CL 5645739 via CL 5645740 via CL 5645741 via CL 5645742 via CL 5646341
[CL 5648441 by mieszko zielinski in Main branch]
Instead, if the region count is 0 we simply return as 'success' since no issues occured. The rest of nav generaiton process is handling this result properly.
#rb Stephen.Holmes, Maxime.Mercier
#ROBOMERGE-SOURCE: CL 5591513 via CL 5591521 via CL 5591527 via CL 5591544 via CL 5594685
[CL 5594727 by mieszko zielinski in Main branch]
This is the case where there are some spans, but not enough to create a walkable surface.
#jira UE-69807
#rb Lukasz.Furman
#ROBOMERGE-SOURCE: CL 4967613 in //UE4/Release-4.22/...
#ROBOMERGE-BOT: RELEASE (Release-4.22 -> Main)
[CL 4968680 by mieszko zielinski in Main branch]
Add support for MODULE_VTABLE for exposing the VTable (Also optionally if enabled RTTI) info for a given type for clang (Linux/Mac)
Rename command line arg bHideSymbolsByDefault to bPublicSymbolsByDefault, as well as now add support for setting this change the BuildConfiguration.xml file
Started from Github PR #3351 though a different way to go about it
#jira UE-42635
#rb Arciel.Rekman, Steve.Robb, Ben.Marsh, Michael.Trepka
#fyi Chris.Bunner, Chris.Gagnon
[CL 4923631 by Brandon Schaefer in Dev-Editor branch]
