Mod Organiser & Bodyslide

[TJHinSkyrim]

I've recently updated my MO and BS, but seem to be having some problems.

 

Whenever I try and export a nif from OS, it throws up an error message that the "path does not exist", despite just having loaded a nif from that same path. I don't have the error if I'm overwriting the file that I loaded, but the error occurs if I try and give the exported file a new name.

 

Similarly, when I try and build or batch build from Bodyslide, it will (only sometimes, not all the time) throw up errors at me that it can't save the relevant files.

It seems that for some reason, BS & OS aren't using the simulated paths that MO2 provides. Does anyone know how I can fix this problem?

[Varithina]

14 hours ago, TJHammersmith said:

Similarly, when I try and build or batch build from Bodyslide, it will (only sometimes, not all the time) throw up errors at me that it can't save the relevant files.

It seems that for some reason, BS & OS aren't using the simulated paths that MO2 provides. Does anyone know how I can fix this problem?

This I have had a fair few times, usually along the lines of cannot find xxx file .nif, though only when batch build with more than 1k items being built, as far as I can tell bodyslide seems to be trying to build them quicker than it can process them and basically jumps files and then reports a missing file, normally in that case I then take note of which files cause the error then just batch build those files again, which for me usually sorts the error out.

 

I get it with all three games skyrim, skryim se, and fallout 4.

[TJHinSkyrim]

Thanks, but I really think it's a MO problem rather than a BS problem.

 

I just tried to use TES5Edit and it threw up error messages about not being able to save the backup files. (Although it appears to have saved them in the Overwrite folder)

 

I'm not sure of the significance, but the save process created extra folders in the overwrite folder, so now I have:

Skyrim/Data/Mod Organizer 2/overwrite/Mod Organizer 2/overwrite/TESEdit 5 Backups/

 

 

[Varithina]

7 hours ago, TJHammersmith said:

Thanks, but I really think it's a MO problem rather than a BS problem.

 

I just tried to use TES5Edit and it threw up error messages about not being able to save the backup files. (Although it appears to have saved them in the Overwrite folder)

 

I'm not sure of the significance, but the save process created extra folders in the overwrite folder, so now I have:

Skyrim/Data/Mod Organizer 2/overwrite/Mod Organizer 2/overwrite/TESEdit 5 Backups/

 

 

That does pretty much imply there is something odd going on with mo, I am guessing by updating mo it was the update for the changes in the nexus log in page that somebody posted on nexus, if so it might be worth asking them if they have any idea what is going on as it sounds like they may have changed something they did not need to, personally on seeing that update I switched from mo to mo2 for skyrim, it sorta works, in that I need to do some work so that it loads properly, but I can not really be bothered with skrim either of them just now.

[TJHinSkyrim]

Found the problem. I had MO installed in the same directory as the game.

 

It wasn't an issue when I was using v1.x.x, but when I upgraded to v2, it clearly is a no-no.

[Varithina]

6 hours ago, TJHammersmith said:

Found the problem. I had MO installed in the same directory as the game.

 

It wasn't an issue when I was using v1.x.x, but when I upgraded to v2, it clearly is a no-no.

Ahh, you did not say you were using mo2, I assumed (bad idea I know) that you were using 1, yeh it can be a bit odd as for me in fallout 4 I have mo2 in the game directory and everything works fine for sse I did until one of the mo2 updates at which point things like xedit/bodyslide stopped working and I had to move it out of the game directory which was annoying as hell.

 

Glad you got it sorted though which is all that matters in the end.

[TJHinSkyrim]

Yeah, I tend to think of MO and MO2 and essentially being different versions of the same program, so I just refer to them as MO.

 

But unfortunately, I think I've celebrated too early. I'm still having issues with Bodyslide, even though I've got TES5Edit to work. *sigh*

[TJHinSkyrim]

I think I'm up and running now. Moved it all the way out of Program Files into a stand-alone directory and it's behaving, after faffing about with path names for the executables.

 

Thanks for all your help!

 

 

[Nazzzgul666]

28 minutes ago, TJHammersmith said:

I think I'm up and running now. Moved it all the way out of Program Files into a stand-alone directory and it's behaving, after faffing about with path names for the executables.

 

Thanks for all your help!

 

 

MO2 is made for SE and FO4, if you're playing Skyrim legendary there is no real reason to upgrade from MO1. Since it sounds like you have to reinstall it anyways, going back might be the best solution.

[worik]

Maybe a thing to avoid all that re-installation of mods when switching between MO1 and MO2 .. you may want read this first. Might save you some precious time

 

https://www.loverslab.com/topic/101906-read-before-doing-anything/?tab=comments#comment-2284701

 

 

 

[TJHinSkyrim]

23 hours ago, Nazzzgul666 said:

MO2 is made for SE and FO4, if you're playing Skyrim legendary there is no real reason to upgrade from MO1. Since it sounds like you have to reinstall it anyways, going back might be the best solution.

 

40 minutes ago, worik said:

Maybe a thing to avoid all that re-installation of mods when switching between MO1 and MO2 .. you may want read this first. Might save you some precious time

 

https://www.loverslab.com/topic/101906-read-before-doing-anything/?tab=comments#comment-2284701

 

 

 

I thought I had to update from MO1 to MO2 because MO1 no longer supported downloads from the Nexus. I swapped over months ago, but only recently had the Bodyslide/TES5Edit issues become too much to tolerate.

 

I wasn't aware of the FNIS/MO2 compatability issues though

[worik]

6 minutes ago, TJHammersmith said:

I thought I had to update from MO1 to MO2 because MO1 no longer supported downloads from the Nexus

On the MO2 page for SSE scroll down.. there you can find an updated MO1 version which can login to the nexus again

MO2 still has some more problems with Skyrim LE and with LE mods than that.  Nothing without a workaround so far but they eat up constantly on your time and nerves.

[Grey Cloud]

On ‎6‎/‎20‎/‎2018 at 9:49 AM, TJHammersmith said:

I think I'm up and running now. Moved it all the way out of Program Files into a stand-alone directory and it's behaving, after faffing about with path names for the executables.

 

Thanks for all your help!

 

 

That sounds like a permissions issue. Your previous MO executable had permissions to work from Prog Files but the new one hasn't. Right-click and 'Run as Administrater' being the thing needed.

[Pinute]

On 6/20/2018 at 1:49 AM, TJHammersmith said:

I think I'm up and running now. Moved it all the way out of Program Files into a stand-alone directory and it's behaving, after faffing about with path names for the executables.

 

Thanks for all your help!

I've forgotten who gave this advice but when I build nifs in MO2 now I open the Bodyslide settings and change the game directory to overwrite.

 

That serves two purposes.

 

One, it avoids overwriting the original nifs, or even worse the nifs in another mod. An example of this the the Book of UUNP CBBE sliders. If I just run Bodyslide it overwrites the nifs in the original UNP version since the sliders don't come with generated nifs. 

 

The second is it is incredibly easy to just make that output in overwrite into a mod, allowing you to switch between different builds without having to run BS again.

 

 

[TJHinSkyrim]

On 6/20/2018 at 7:20 PM, Nazzzgul666 said:

MO2 is made for SE and FO4, if you're playing Skyrim legendary there is no real reason to upgrade from MO1. Since it sounds like you have to reinstall it anyways, going back might be the best solution.

 

Yeah..... I did just that in the end. Oh well, lesson learned.