 Issue Data
|
|
||||||||||||||||||||||||||||
Issue #27309: Navmesh missing in random encounter zone near trigger 0023A9EC
This is the trigger for RETravel type encounters on the road north of Wildwood Cemetery, in cell WildwoodCemeteryExt05 (-4, 17).
There's nothing wrong with the navmeshes in that area. Most likely, the NPCs for the encounter were placed while the markers (where they are placed at) were in unloaded area. RETravel type encounter zones have two clusters of markers at a large distance, usually on two sides of a long stretch of straight road. In this case, these two clusters are more than two cells apart and the trigger itself sits on a cell boundary. RE triggers send a story event when they load, Starting the quest and setting up the enemies takes some time, and while you approach, the distant part of the encounter zone is eventually loaded. When you turn around and move away from the zone, the trigger unloads and the quest shuts down. When you stop however after the trigger has just loaded, a situation where NPCs are placed in unloaded area should not be too difficult to reproduce. I only wonder now why I haven't seen such errors in my game more often.
There's nothing wrong with the navmeshes in that area. Most likely, the NPCs for the encounter were placed while the markers (where they are placed at) were in unloaded area. RETravel type encounter zones have two clusters of markers at a large distance, usually on two sides of a long stretch of straight road. In this case, these two clusters are more than two cells apart and the trigger itself sits on a cell boundary. RE triggers send a story event when they load, Starting the quest and setting up the enemies takes some time, and while you approach, the distant part of the encounter zone is eventually loaded. When you turn around and move away from the zone, the trigger unloads and the quest shuts down. When you stop however after the trigger has just loaded, a situation where NPCs are placed in unloaded area should not be too difficult to reproduce. I only wonder now why I haven't seen such errors in my game more often.
Showing Comments 1 - 1 of 1