When exporting a STAT record containing a navmesh from a Starfield .esm, the gridcells sub-container is not split into separate gridcells, but rather contains a single gridcell with the unparsed data for all the gridcells.
Spriggit 0.18; SF1Edit 4.1.5d
It gives the impression that gridcells are parsed, but they are not. My suggestion would be to either parse them, or not include the gridcell object at all (as what is labeled a "GridCell" is in fact an "UnparsedGridCellArray"
The attached esm has an example of a static with a navmesh that should contain 4 gridcells according to SF1edit, but in the spriggit yaml it is stored as one.
When exporting a STAT record containing a navmesh from a Starfield .esm, the gridcells sub-container is not split into separate gridcells, but rather contains a single gridcell with the unparsed data for all the gridcells.
Spriggit 0.18; SF1Edit 4.1.5d
It gives the impression that gridcells are parsed, but they are not. My suggestion would be to either parse them, or not include the gridcell object at all (as what is labeled a "GridCell" is in fact an "UnparsedGridCellArray"
testnavmesh.zip
The attached esm has an example of a static with a navmesh that should contain 4 gridcells according to SF1edit, but in the spriggit yaml it is stored as one.
Made up example:
Current output (non-data commented)
Expected Output:
Alternatively if such parsing is undesired, the structure is inaccurate - the GridCell node should be collapsed into parent:
Non-ideal alternative
(I have yet to see if Mutagen has the same issue)