nifskope crashes when deleting assets

[nognow]

nifskope is driving me insane. It crashes whenever I delete assets (nodes, shapes etc.)

I tried everything: reinstalling, running as admin, adding to antivirus exceptions, trying different versions of nifs (FNV, FO4) etc.

Currently, I have to delete an asset and quickly save with the reflexes of a cat before it crashes. Then I have to reopen and continue. When there are a lot of assets that need to be removed, and without the ability to select multiple items, it's a game of delete, quick-save, crash, reopen.

Has anyone encountered this problem? If they exist, where are the crash reports stored? are there any alternatives to nifskope?

[dubiousintent]

You should always start troubleshooting from any error messages you can see. (They are your best "clue"; and why they exist at all.) We don't expect you to be able to interpret those messages, but reporting such accurately and in detail (i.e. screenshots) is an essential first step.

Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog because both the game engine and Windows itself was not able to predictably handle the error. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article. These errors need to be dealt with first.

Logs generated by the game itself (not Windows) are found in the game folder, where the "FalloutNV.EXE" file is located. They generally have the ".log" file extension, or a filename with "_log" in the name and a ".txt" extension.

 

Don't know if NifSkope generates any logs, and the first place to look is where it is installed as it is an "independent tool" separate from the game.

 

-Dubious-

[M48A5]

Since there are so many, which version of NikSkope are you using?

[nognow]

You should always start troubleshooting from any error messages you can see. (They are your best "clue"; and why they exist at all.)àààWe don't expect you to be able to interpret those messages, but reporting such accurately and in detail (i.e. screenshots) is an essential first step.Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog because both the game engine and Windows itself was not able to predictably handle the error.àPlease see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article.àThese errors need to be dealt with first.Logs generated by the game itself (not Windows) are found in the game folder, where the "FalloutNV.EXE" file is located.àThey generally have the ".log" file extension, or a filename with "_log" in the name and a ".txt" extension.àDon't know if NifSkope generates any logs, and the first place to look is where it is installed as it is an "independent tool" separate from the game.à-Dubious-

 

Â

 

There are no error messages. It just freezes for a second and closes. There are no log files (that I can find)

 

ÃÂ

Since there are so many, which version of NikSkope are you using?

The latest 2.7 Edited March 7, 2021 by nognow

[M48A5]

The latest release I can find is NifSkope 2.0 Dev 7. Are you sure about the version number? Or, did you mistakenly post the Blender version?

[nognow]

The latest release I can find is NifSkope 2.0 Dev 7. Are you sure about the version number? Or, did you mistakenly post the Blender version?

I was referring to 2.0 dev 7

[Pixelhate]

This is not normal behaviour for NifSkope.

 

- Where and how did you install it?

- Describe exactly each step you are performing till crash.

- If it happens with one nif in particular, please share it so I can have a look.

[nognow]

This is not normal behaviour for NifSkope.

 

- Where and how did you install it?

- Describe exactly each step you are performing till crash.

- If it happens with one nif in particular, please share it so I can have a look.

1. Downloaded the latest version from here https://github.com/niftools/nifskope/releases and unpacked it into a non-system folder.

2. Removing an asset, any asset, crashes 50% of the time within a few seconds. Adding assets, batch processing, converting etc. work flawlessly. It also crashes occationally when adding resource paths.

3. It started when I was tinkering with these meshes: https://www.nexusmods.com/newvegas/mods/67667

they were poorly generated and despite working well in-game, Sniff can't process them (returns "Not a valid NIF file"). So I remade them. It was a while ago though and the aforementioned meshes are no longer used or opened.

[Pixelhate]

Install & version seems OK.

In more than 10 years of use I can count NifSkope crashes on one hand, mostly due to my mistakes.

There are several ways to delete or remove a Node or an Array in a nif. (I guess that's what you mean with "assets")
The correct (and long one) is:
1. Unlink the Node from its parent.
2. Select the Root Node -> Rclick -> Crop to Branch
3. In menu select Spells, -> Sanitize
A.-> Collapse link Arrays
B.-> Reorder link Arrays
C.-> Reorder Blocks
4. Save
This should ensure a safe result (if the nif is originally healthy).

The nifs you linked are indeed bad with NiTriStrips and NiTriShapes mixed. I can't pinpoint other error at first sight but the fact that it can't be proceeded in Sniff with "not a valid nif" message says it all. Troubleshooting deeper might be uncertain.

I could remove parts without crashing, with NifSkope giving an error message one time on closing.
I would stay away from such meshes unless you are able to import/export from a 3D app with the correct settings.

If the issue you've described persist with other know clean nif then you might need to reinstall NifSkope.

[nognow]

Install & version seems OK.

 

In more than 10 years of use I can count NifSkope crashes on one hand, mostly due to my mistakes.

 

There are several ways to delete or remove a Node or an Array in a nif. (I guess that's what you mean with "assets")

The correct (and long one) is:

1. Unlink the Node from its parent.

2. Select the Root Node -> Rclick -> Crop to Branch

3. In menu select Spells, -> Sanitize

A.-> Collapse link Arrays

B.-> Reorder link Arrays

C.-> Reorder Blocks

4. Save

This should ensure a safe result (if the nif is originally healthy).

 

The nifs you linked are indeed bad with NiTriStrips and NiTriShapes mixed. I can't pinpoint other error at first sight but the fact that it can't be proceeded in Sniff with "not a valid nif" message says it all. Troubleshooting deeper might be uncertain.

 

I could remove parts without crashing, with NifSkope giving an error message one time on closing.

I would stay away from such meshes unless you are able to import/export from a 3D app with the correct settings.

 

If the issue you've described persist with other know clean nif then you might need to reinstall NifSkope.

 

 

I remade those nifs:

They seen fine now https://filebin.net/my7ubm6q623y7jnk

Is it better to use tristrips or shapes?

Regardless, the issue persists with all nif and obj files.

by "deleting assets" I mostly meant NiTexturingProperty and NiMaterielProperty from imported OBJ files and NiNodes.