Releases: JMPZ11/nifskope-sf-mesh
NifSkope "Meshageddon" Edition v0.1.2-alpha
v0.1.2-alpha of Starfield 1.11.33 Mesh Migration Tool
Contents:
nifskope-sf-mesh
Custom version of NifSkope - unofficial, unendorsed - with two new spells for fixing .nifs individually or in bulk.
If you didn't get this from Nexus or GitHub, please redownload it for safety.
Nexus Url: https://www.nexusmods.com/starfield/mods/9234
Source code (and Linux version) is available here: https://github.com/1OfAKindMods/nifskope-sf-mesh
Changes:
-
Data set now contains a complete list of ALL old vanilla meshes. No more ambiguous "looks like:" the tool now knows what it doesn't know, so it can tell you exactly which meshes it was unable to fix.
(Note: mapping stats are unchanged: 88% of total; 99.9% of those referenced in .nifs the Blender plugin can handle) -
Addition of a new spell: "Bulk Update to SF 1.11.33 Mesh Paths" that will automatically repair and save all .nif files in a folder tree.
-
Meaningful statistics in follow-up report - includes count of total unmapped meshes encountered.
If unmapped count is zero, the .nif should be fully restored and good to go -
Detailed logging - both for individual and batch runs.
Step-by-Step:
-
Single File Processing:
- Open a .nif file that is or will be broken by the 1.11.33 update in this version of NifSkope.
- Go to
Spells -> Update to SF 1.11.33 Mesh Paths
. It will immediately update the meshes. - A popup will show the number of modified Mesh Paths and the number of paths encountered that have not yet been mapped. If unmapped is zero, you are all set.
- To see the changes, you must first Save (or Save As), then reload.
- Save.
- Move on to the next model.
-
Batch Processing:
- MAKE SURE YOU HAVE A BACKUP BEFORE EVEN THINKING ABOUT IT!
Updates .nifs in-place. - Ensure you do not have any unsaved work - there is no need to have a file open first.
- Go to
Spells -> Bulk Update to SF 1.11.33 Mesh Paths
. - A folder selector will pop up - select the root folder to process.
NOTE: As soon as you press OK, it will start updating every .nif file (it can) in and under the selected folder. There is no confirmation until the job is complete. - The tool will process all .nif files in the selected directory and subdirectories.
- A log file with detailed changes and a summary will be created in the root folder.
- MAKE SURE YOU HAVE A BACKUP BEFORE EVEN THINKING ABOUT IT!
Things to Note
- Currently cannot detect if a NIF failed to load or save (except for read-only files). These things are in events, and spells can't really connect to QT events. i.e., big lift (for me).
- Will not fix mods that replaced vanilla meshes. These simply need to be moved/renamed. You can search in the data file to find the correct path. In the future, replacing vanilla meshes should be considered verboten.
- Until now, we haven't been tracking changes to meshes, so past updates may have included one-off breaking changes, creating strange bugs. Going forward, we have a process to stay on top of it.
- I have updates to the Blender plugin that will further mitigate this going forward by making local copies of all meshes with meaningful names in your subdir of choice. With LODs working. And materials. Might be helpful, IDK.
Log File Format
As each .nif is processed, an entry is made to a log file (beside the open file, or in the root). The file name is based on the version of the mapping file with a timestamp. When an old vanilla mesh is encountered, a log of the BSGeometry object name (supposed to be unique...), old and new paths is made. If there is an unmapped mesh, it is indicated by ERROR something.
Stay safe out there!