Nexus Mod Manager and game broken after GECK crash save?

[Draghy]

Hello, I'm using NMM 0.65.10 and was working in GECK on an esp patch when GECK unexpectedly crashed but a Crash Save file was created with most of my changes active.

 

After that happened, I can't change the load order of my plugins (it won't let me drag and drop them) or install any mods.

 

The game also freezes if I try to load a save but works allright when starting a new game.

 

Any thoughts or potential fixes for such bizzare problem?

[dubiousintent]

First a bit of advice: do not work on patches while in a mod manager. The reason is that the managers designed after FOMM (NMM, MO, MO2, and Vortex) all work from the concept of an "empty data folder" using "symlinks". The GECK should work with symlinks just fine, but it doesn't KNOW it is, and is probably making assumptions (such as exclusive file access) that do not play well with the manager. In addition, the GECK is not really suited to making "patches". Using xEdit/FNVEdit (freeware) was designed for the purpose and is much preferable. It specifically cautions against using within a mod manager to avoid the "file locking" problem.

 

My guess as to your current problem is that NMM has left whatever it uses to indicate "file locks" in place due to the CTD. (This is often a "temporary file" for each "locked" file.) You need to ask the GitHub support team how to deal with that situation as they are the only ones who are going to know how it is implemented. Otherwise you are left with uninstalling NMM, wiping that folder, and re-installing NMM. And even that might not work if the lock files are placed elsewhere (such as in the "Data" folder).

 

-Dubious-

[Draghy]

Well I was using GECK since I also can easily view the 3D model to evaluate the level of protection for armors (I was rebalancing all the armors in the game/mods)

 

 

First a bit of advice: do not work on patches while in a mod manager. The reason is that the managers designed after FOMM (NMM, MO, MO2, and Vortex) all work from the concept of an "empty data folder" using "symlinks". The GECK should work with symlinks just fine, but it doesn't KNOW it is, and is probably making assumptions (such as exclusive file access) that do not play well with the manager. In addition, the GECK is not really suited to making "patches". Using xEdit/FNVEdit (freeware) was designed for the purpose and is much preferable. It specifically cautions against using within a mod manager to avoid the "file locking" problem.

 

My guess as to your current problem is that NMM has left whatever it uses to indicate "file locks" in place due to the CTD. (This is often a "temporary file" for each "locked" file.) You need to ask the GitHub support team how to deal with that situation as they are the only ones who are going to know how it is implemented. Otherwise you are left with uninstalling NMM, wiping that folder, and re-installing NMM. And even that might not work if the lock files are placed elsewhere (such as in the "Data" folder).

 

-Dubious-

What exactly is CTD? I made an issue on the NMM team's Github.

 

I managed to fix most of the problems and can run the game now, but the load order's still bugged and it's really annoying.

[dubiousintent]

Apologies (failed my "spell out acronyms fully before using" check). "CTD" stands for "Crash To Desktop", which is what happens when a "program" such as a game does something the "Operating System (OS)" (Windows in this case) intercepts and causes the program to halt with an error message, but leave you looking at the Windows desktop and still able to run other programs (including the game again). This is different than a so-called "Blue Screen of Death (BSoD)" which is a similar condition that the OS is not able to intercept and brings the entire OS crashing down without leaving a decipherable error message. A "reboot/restart/power cycle" of the computer is your only option in this latter case.

 

In both instances however, the system is in a somewhat uncertain state in the memory and you should (in the interests of safety and avoiding potential unexpected issues) reboot the system so it comes up in a safe and predictable state.

 

As I understand it, NMM use the "load order" given in the "profile". If it also uses a "override" folder, that will also get included. If you are unable to change either of those folders, then my guess would be they are "file locked" in some manner and if the GitHub team doesn't have a solution you may need to uninstall, delete those folders, and re-install NMM to clear the locks.

 

-Dubious-

Edited September 17, 2020 by dubiousintent