CTD without a cause

[hentaishinri]

Also, when I install a certain mod and it asks me to 'extract the BSA' should I click yes? Because I've been clicking no so far and the installed mods only appear in the MO, Wrye Bash doesn't show them and Sky Launcher doesn't show them

[ripple]

@gamefever

If you are happy with your current setup and you are not installing new mods, then there is probably no reason to really switch to MO. If you are installing new mods again, you can migrate slowly to MO from NMM by installing new mods through MO rather than NMM (and using MO to manage the load order). I think 1.2.4 also has some features to ease the process or migrating mod installations from NMM. I just never tried them because I already migrated a long time ago (through a complete reinstall of mods).

 

@hentaishinri

Try and set BOSS GUI.exe as the executable and see if that helps. Also, you didn't install BOSS through MO, right? Utilities like BOSS, Wyre Bash, TES5Edit, should be installed normally and not through a mod manager. Try running BOSS outside of MO and see if it works first. Then try running it in MO. This way you know which one is causing the problem.

 

Unpacking BSA: there are mix feelings about this. Most people suggest you retain the BSA file, while I tend to unpack them into loose files when I install (the installation guide on G.E.M. also suggests choosing mod versions with loose files instead of their BSA versions). I don't know why G.E.M. installation guide suggests loose files over BSA, but the reasons I unpack some of the BSA files of mods I install through MO are:

 

1) you can see file conflicts in the MO virtual data folder if they are loose files. You can't if they are compressed into the BSA.

 

2) MO does not install files into the game data folder, but keeps mods separate in their own folders, so the idea that loose files might be left behind after you uninstall a mod (which is typical of traditional mod installation methods) does not apply here.

 

Now, I don't unpack *all* BSA of mods I install. I usually just unpack those that I suspect might include conflicting textures/meshes/scripts. For example, retextures of body replacers, or any kind of retextures intended to replace default or mod base textures (although most retextures usually don't come in BSA format, except those 'overhaul HD retexture of every item' mods). Unpacking them allows me to see the conflicting files in the MO virtual data folders so I can decide who should 'win' the load order contest. I've had to unpack SkyUI 3.1's BSA when it was having that 'hiccup' with a previous version of MO (other people got it to work just by unchecking the BSA). So...yeah, for the most part, it doesn't really matter for MO users, but I wouldn't recommend unpacking every BSA (because BSA does, at least, tend to save disk space....). Rather, I'd recommend unpacking BSA when you suspect it contains resources that conflicts with other mod resources. This way, you can see the conflict.

[DarkZuriel]

Okay, i think this is getting away from Topic. I had Skyrim installed on my old PC, it just worked fine and i often installed many mods without caring, if they would crash my game. Now ive got a new PC and i installed Skyrim, just the blank Vanilla thing from Steam. I started the game just as normal, without SKSE. I get the Bethesda screen, then clicked on new game. And then i experienced the CTD. I really dont understand, i googled and the fix with the sound qualitiy just wont work. And since the 2GB issue is fixed i am runnig out of solutions so please help and stop talking about BOOS an MO and NMM please

[ripple]

Okay, i think this is getting away from Topic. And since the 2GB issue is fixed i am runnig out of solutions so please help and stop talking about BOOS an MO and NMM please

 

Hentaishiri started this thread. We are troubleshooting his issues. I think you may have confused this thread for another thread that you have started, because this is the first I've heard of your troubles. If you haven't started a thread about your issues, please don't post your issue in other users' active troubleshooting threads. Just start your own thread detailing your issues so they don't get confused with other users' issues.

[hentaishinri]

@DarkZuriel I'm sorry if this thread isn't helping you much, we're just trying to resolve how NMM and installing mods without Wrye Bash and MO can result in CTD's.

And that brings me back on the topic, which is I can't thank you enough ripple. Everything is going more smoothly than ever. I installed half of the mods I had before, I played for around 3 hours - not a single crash. Not even a freeze. And even some npc's that were acting weird before are acting normal now.

In two words:

Update: The game is working perfect for now. (I was also able to make BOSS run, hooray!)

Here is my MO screenshot:

 

http://i.imgur.com/ikspCj4.png

 

The only thing I still can't get through is how to make the mods visible in wrye bash.

The game loads them, everything is perfect, but Wrye Bash doesn't load mods installed by MO. Only those installed manually.

Other than that everything is perfect and I can't thank you enough ^.^

[ripple]

The only thing I still can't get through is how to make the mods visible in wrye bash.

The game loads them, everything is perfect, but Wrye Bash doesn't load mods installed by MO. Only those installed manually.

Other than that everything is perfect and I can't thank you enough ^.^

 

No problem. Wrye Bash: have you set it up as an executable in MO just like BOSS? If you launch Wrye Bash through MO, it should display all the esp's.

 

We're only half way through :) The next step is to download TES5Edit and set it up an an executable in MO as well. You'll need it to clean esp's when BOSS tells you to.

Edited January 23, 2013 by ripple

[hentaishinri]

The only thing I still can't get through is how to make the mods visible in wrye bash.

The game loads them, everything is perfect, but Wrye Bash doesn't load mods installed by MO. Only those installed manually.

Other than that everything is perfect and I can't thank you enough ^.^

 

No problem. Wrye Bash: have you set it up as an executable in MO just like BOSS? If you launch Wrye Bash through MO, it should display all the esp's.

 

We're only half way through :) The next step is to download TES5Edit and set it up an an executable in MO as well. You'll need it to clean esp's when BOSS tells you to.

It won't do that, I'm at a pause about this :(

Whenever I try to load anything else than SKSE this comes up:

http://i.imgur.com/9V4pHwF.png

and even if I start steam it doesn't start....

I tried both with Wrye Bash and BOSS

BOSS starts, but as I said, crashes, saying "BOSS.exe has stopped working"

Edit: I read something about the 'Load Mechanism' does this have anything to do with it :/

Update: Nope, can't get it to work. Nothing through MO starts.

Edited January 23, 2013 by hentaishinri

[ripple]

Try and set BOSS GUI.exe as the executable and see if that helps.

 

If you run BOSS outside of MO then it won't order any of the mods you install through MO (only those in the game data folder). For all these utilities to work, you need to launch them through MO so they will load the resources in the MO 'virtual data folder.' That error message should not come up when you are just trying to run a third party utility that does not require Steam. Click 'no.'

[hentaishinri]

Try and set BOSS GUI.exe as the executable and see if that helps.

 

If you run BOSS outside of MO then it won't order any of the mods you install through MO (only those in the game data folder). For all these utilities to work, you need to launch them through MO so they will load the resources in the MO 'virtual data folder.' That error message should not come up when you are just trying to run a third party utility that does not require Steam. Click 'no.'

It doesn't work, they don't load :( Not BOSS gui, not anything.

[ripple]

Ok. Let's go back a step. Where did you install BOSS? What's the directory path?