I'm hoping that 227j will be different because 227i it's not like has the best ever DevPath...
This is a copy of
DM-Deck16][ using current nodes - nothing moved, just building paths in 227i - Gold.
After checking paths in UT using XC assets:
Code: Select all
LostData: ________________________________________________________________
LostData: ReachSpecs missing from Paths[0-15] = 213.
LostData: ReachSpecs missing from upStreamPaths[0-15] = 228.
FixedWithSuccess: ReachSpecs successfully attached = 293.
FixFailures: ReachSpecs attaching failures - probably no place = 148.
LostData: ________________________________________________________________
SpecTest: Testing and fixing specs took:
0.048127 seconds.
SpecCheckLocator: Checking ReachSpecs Localization has been finished.
For a logic programming reason - preventing iterations, this fix might need to be applied multiple times. Last hit was unable to fix anything... because it cannot be fixed.
Code: Select all
LostData: ________________________________________________________________
LostData: ReachSpecs missing from Paths[0-15] = 52.
LostData: ReachSpecs missing from upStreamPaths[0-15] = 96.
FixedWithSuccess: ReachSpecs successfully attached = 0.
FixFailures: ReachSpecs attaching failures - probably no place = 148.
LostData: ________________________________________________________________
SpecTest: Testing and fixing specs took:
0.034943 seconds.
What's different ? New R_Fly paths unused by Bots and the rest of lost data - as usual.
With regard to "We could not recreate the bug" story... just re-build paths in said map and examine PathNode33. Look how many Paths Lines are having said node and how many are placed in Paths[0-15] using "EditActor" command. Evidence it's more than clear.
The stage reported from Mr. Garbage. ReachSpecs embedded in Navigation
Code: Select all
NumReachSpecs: This map has 1630 ReachSpecs shown as direct paths in Navigation Network.
NumReachSpecs: Also this map has 1044 ReachSpecs as shortcuts aka PrunedPaths in Navigation Network.
NumReachSpecs: These are not visible in Editor but they are used by Pawns.
NumReachSpecs: After calculation we have 2674 ReachSpecs.
ReachSpecs hunting report by testing index:
Code: Select all
MaxNumFound: I found a sum of 2887 reachspecs defined in map, from 0 to 2886.
2887 - 2674 = 213 ReachSpecs hosted nowhere.