Hello good people!
I hope this is the right section, as it may be a Nifskope thing!
A few weeks ago I uploaded a mod to Nexus and it kept crashing people's games. The issue I initially thought might have been because I do not have my install in C\ProgramFiles\Bethesda Softworks. After all, we are told not to do that with Windows 7. Mine is C\Games\Bethesda Softworks\Oblivion.
As it was only one (albeit complicated) mesh I created a dummy directory and got Nifskope to do it's thing with the texture paths. But the revised version still crashed people so I took the mod down. I wonder if the problem is that the TESCS is in my working OB install as it has to be, and is fouling it up?
I would very much appreciate some advice for this noob modding apprentice! What do you think might be happening here?
My mod crashed people's games!
Started by
Ginnyfizz
, Sep 06 2011 12:05 PM
10 replies to this topic
#1
Posted 06 September 2011 - 12:05 PM
#2
Posted 06 September 2011 - 12:08 PM
Are you certain that NifSkope has its file paths selected properly? I had a problem with my first mod doing that, but it didn't crash anything like that.
It could also be a problem with the mesh. Is it made from scratch or a retexture or something?
It could also be a problem with the mesh. Is it made from scratch or a retexture or something?
#3
Posted 06 September 2011 - 12:39 PM
Just taking a shot in the dark here, but are all the NiTriStrips above the NiNodes in the block list?
Perhaps upload the mesh to a file host somewhere so we can download it and check it out?
Perhaps upload the mesh to a file host somewhere so we can download it and check it out?
#4
Posted 06 September 2011 - 03:03 PM
It doesn't matter where you have installed the game, as long as the folder structure of your mod is standard Oblivion/Data/Meshes, Oblivion/Data/Textures.
Make sure that Nifskope is giving you a virtual path ... ie; the texture path starts with Textures and not a static path .. ie; that it starts with C:\Oblivion\Data\Textures. In Nifskope, under Render, go to Settings, Render tab, and click on Auto Detect Game Paths. Also click on Add Folder, and browse to and select your Textures folder, so that it shows ./textures in the box below it. Repath your texture and it should start from the Textures folder.
Have someone test it and if it still crashes, there are further problems.
Make sure that Nifskope is giving you a virtual path ... ie; the texture path starts with Textures and not a static path .. ie; that it starts with C:\Oblivion\Data\Textures. In Nifskope, under Render, go to Settings, Render tab, and click on Auto Detect Game Paths. Also click on Add Folder, and browse to and select your Textures folder, so that it shows ./textures in the box below it. Repath your texture and it should start from the Textures folder.
Have someone test it and if it still crashes, there are further problems.
#6
Posted 06 September 2011 - 07:36 PM
Yep, the texture paths are definitely one problem. Fix that first and test.
Not sure if the "upperbody" being called Foot is going to be a problem or not.
Not sure if the "upperbody" being called Foot is going to be a problem or not.
#7
Posted 06 September 2011 - 08:04 PM
There's also a lot of NiTriStrips that are not parented to the scene root - this will definitely cause crashes.
I've cleaned up the parenting and texture paths and sent the mesh via PM. See if it still crashes.
I've cleaned up the parenting and texture paths and sent the mesh via PM. See if it still crashes.
#8
Posted 07 September 2011 - 08:23 AM
For what it's worth, PyFFI can correct most of this sort of thing. Definitely the texture paths and the orphaned nodes, and possibly other issues that are not obvious.
#9
Posted 07 September 2011 - 08:41 AM
I am really grateful to you guys for your advice. Hopefully I will get a chance to play and test later, will report!
Edited by Ginnyfizz, 07 September 2011 - 08:41 AM.
#10
Posted 08 September 2011 - 07:00 PM
Yes! Is working for me!
#11
Posted 08 September 2011 - 07:05 PM
Good to hear Ginny. 
And Arthmoor, I'll take up your suggestion of using PyFFI since nifs can be so pedantic at times.
And Arthmoor, I'll take up your suggestion of using PyFFI since nifs can be so pedantic at times.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
















Back to top







Sign In
Create Account


