Mod Organizer 2 And Wrye Bash not getting along...

[DOHstep2013]

I have had more weird issues in the last two weeks than ever before with any of these utilities, both with Skyrim SE and Fallout 4. It's making me nuts. A bit.

 

Basically everything worked find a few weeks ago, and then I was unable to use LOOT, Wrye Bash, or Xedit from within Mod Organizer. I switched to the Portable version of MO2 and now everything is working, except Wrye Bash.

 

The current problem is occurring as I attempt to get Fallout 4 set up. Wrye Bash does run from it's executable outside MO2.

 

I have tried all the versions of WB except Python. Everything is current. When I link it in Mod Organizer 2 it sort of starts to load (I see the Wrye Bash logo for a second) and then it doesn't. I think I've configured Modify Executable properly, and the install is the recommended type and has never been an issue before.

 

I could certainly use some assistance, and I would greatly appreciate any offered. Thank you.

Edited March 18, 2018 by DOHstep2013

[GrantSP]

I'm currently off my desktop and on my backup laptop which is a Linux machine, so I can't offer up-to-date insight on this.

Have you tried in the Discord server? Here's a link if you haven't been there yet.

https://discord.gg/MM5SA5

[DOHstep2013]

Thank you for replying GrantSP.

 

I cannot make heads or tales of the Discord link you provided. Is that a place to ask questions? Is this not a place to ask questions? Oh I'm so confused..

[GrantSP]

That server is where the devs are discussing the latest bugs and releasing test builds. Testers are encouraged to use them and provide feedback.

I believe the Nexus downloads are a little behind the time and there may be a fix for this issue. I do recall some chatter about this lately.

 

Sadly my desktop system is broken and I am unable to do any testing on MO/MO2 until it is fixed so I'm not paying as much attention to fixes as I used to.

[DOHstep2013]

Thank you for the help. I will check that out.

[DOHstep2013]

I found an updated version of MO2 that apparently has solved the problem. Thank you again.