Update Navmesh/NAVI definitions/decoding#1273
Conversation
Changed "Navigation Mesh" & related to "Navmesh" to match the CK Decoded PathingDoor on NAVI \ NVMI \ Door links Decoded NAVI \ NVMI Categories Decoded NAVM \ Edge Links \ Type Also added sorting on some arrays on NAVI that are confirmed sort-able. Still testing the ones under NVPP As well as added includeFlag(dfCollapsed) on virtually all of the collapseable nodes which has shown a rather significant performance improvement when looking at/comparing/editing the NAVI record in xEdit. And/or comparing multiple NAVIs across several plugins at once. Updated other names to better reflect the data they actually represent.
|
I don't like some of these name changes |
|
Well the term "Navigation Mesh" doesn't actually exist anywhere, the CK always uses Navmesh. and in the case of Navi its specifically called a Navmesh Info Map with the NVMI array entries called Navmesh Infos. Other then that its just Navigation Mesh or Mesh to Navmesh where applicable. Seems reasonable to me. The name changes within the NVMI Array i suppose are not as certain, but the ones i have in there are accurate as to what the field is listing. For Edge Links, its a list of navmeshes that the given Navmesh has edge links with. Preferred Edge links is the same, where the triangles on either side of at least one edge link are flagged as preferred. |
Updated NVPP Name to Precomputed Pathing as that is what the CK/Engine actually calls it/uses it for. Renamed Path Index to Road Index as thats what the CK/Engine uses it for. Structure of the first array under NVPP needs to be changed, but as of yet I don't know how to set it up, will post a write-up in the Decoding channel First array cannot be set to sorted, although the CK on save will the lists in a specific order anyway, it just isn't sorted by form id. The second array can be sorted by the Index number, as that will put the second array in a matching order with the "indexes" in the first array. Need some though on the names the Second array is a list of every navmesh on which a Road Marker sits, and the navmeshes listed are the Start/End points of each of the precomputed paths in the First Array.
Corrected several broken callbacks. I also have to update the 2 included navmesh Clean/Check Edges scripts, will put those in the next Commit.
Update the Clean/Check Edge links in navmeshes script to go along with the other changes in this PR
|
The update to the Check Edge Links script includes an update sent to me by Zilav that is contained in Issue #1091. |
Shortened the names of the 3 Category Integers. Also comments explaining what the actual relevance is. Open to better names.
Navmesh now has the Initially Disabled flag in the CK.
Define ONAM, PNAM, and NNAM.
Added $03 to Edge Links Type List, and input better names to mirror FO4/FO76
Add Edge Link Type list to the Simple Records version of Edge Links.
Changed "Navigation Mesh" & related to "Navmesh" to match the CK
Decoded PathingDoor on NAVI \ NVMI \ Door links
Decoded NAVI \ NVMI Categories Decoded NAVM \ Edge Links \ Type
Also added sorting on some arrays on NAVI that are confirmed sort-able. Still testing the ones under NVPP
As well as added includeFlag(dfCollapsed) on virtually all of the collapseable nodes which has shown a rather significant performance improvement when looking at/comparing/editing the NAVI record in xEdit. And/or comparing multiple NAVIs across several plugins at once.
Updated other names to better reflect the data they actually represent.