Jump to content

Clannfear, Daedroth head stretching, now game crashes.


Lamae Bal

Recommended Posts

For a while now I've had a problem where Clannfear and Daedroth heads stretch to infinity. This happened at about the time I installed Creature Diversity http://www.nexusmods.com/oblivion/mods/26634/? and RRSC http://www.nexusmods.com/oblivion/mods/38427/? (Just the Realistic Physics and Force Update). Now when I tried to look up the problem I got these answers: http://forums.nexusmods.com/index.php?/topic/473038-marts-monster-mod-and-clannfear-textures-stretching/ and http://www.loverslab.com/topic/3491-heads-stretching-to-infinity/ The first one says it's a conflict between FCOM and UOP. RRSC also conflicts with the skeletons of Daedroths and Clannfears added by UOP (I do not use FCOM, just OOO). I uninstalled RRSC and the problem persisted. I have NIF files "Daedroth.NIF" "Clannfear.NIF" and "Clannfear_Head.NIF" and others added by some unknown mod, maybe Underdark (which is just an Omod so I can't inspect the files), and when I tried to move Daedroth.NIF and Clannfear.NIF out of the data folder, the game crashed when loading different saves from different characters. So I put them back, and tried adding the UOP skeletons that had been deleted by RRSC. Still crash. So I reinstalled the RRSC mod. Everything is now the way it was the night before, when the game wasn't crashing, but it's now crashing when I load any save. So things got from bad to worse. Please help.

 

Load order: http://pastebin.com/hRXWw7Vs

 

EDIT: NVM, fixed this, it was just the OSR heap being weird again. Turned that off and the Daedroths and Clannfears are back to normal, so the UOP NIF's worked :D

Link to comment

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, see our Privacy Policy & Terms of Use