toolio20

I've looked through some of the other posts but didn't see this problem mentioned - if I missed it, apologies. Anyway, I've got a fresh, stock copy of NV loaded (with a singular pistol mod downloaded as part of the tut but not activated) with NVSE installed and working properly through MO. I installed "4GB Fallout New Vegas Updated" and can run it successfully with it's own launcher. However, when I attempt to integrate it into MO via the Modify Executables interface I...just can't. I enter the correct binary location (within the root Fallout New Vegas folder) and although the "Add" option will un-grey, when I click it the entry isn't added to the list and all the fields go blank. I have tried setting the "Start in" value, to no avail. Disabled AV for a few tries, no change. Manually running as admin, btw, and have faithfully followed EssArrBee's instructions as well. I tried to add a test NVSE shortcut and it exhibited the same behavior - MO absolutely refuses to add anything to the executables list. It will happily take down the location information, enable the "Add" button and as soon as I click on it, poof, everything vanishes and the loop begins anew. Some setting has got to be screwy, but I can't for the life of me figure out what it is. Any help or insight you guys could provide would be most appreciated, as always. [spoiler=Ready to hit Add...] [spoiler=The sad result]

Wait - so even if you successfully launch via SKSE outside of MO, the game is crashing?

Your instincts were correct...about 90%, but that's good enough for me! I say partially, because the issue is twofold - concerning not just the AV but MO itself. I've discovered MO will - without any prompting or coaxing - automatically convert the SKSE path to "stylesheets" upon closing the program after the first run. Why it does that is anyone's guess, and it really threw off my troubleshooting. So in summary, this is what I would've had to do to out of the gate to mitigate this problem: Install MO/close it/add an exception in AV/open MO, install SKSE/close it/open MO, manually configure SKSE path/close it/open MO, verify path and functionality/mod and play game. If anyone experiencing the same issue sees this thread down the line, it should be noted this link is helpful as well. Dub, thanks again - I'd give reps but since that's not doable, credit where it's due will have to suffice.

Why are you not reading? There should be every need to do this before responding. As I said, deleting ModOrganizer.ini before launching the program is the ONLY WAY the utility will actually launch the game. If I close MO and re-open it without deleting the .ini, I get "Executable "" not found" errors, regardless if I choose SKSE or the vanilla launcher. I have to shut MO down, delete the .ini and open it again in order for Skryim to actually launch through the UI. Skyrim is not on a portable drive - it's in my SteamLibrary, which is on a secondary SSD apart from my OS drive, but the drive letter is not changing. SKSE launches just fine if I've deleted the .ini, so I don't believe the shortcut is to blame - but if you can assist me with checking that, I'll gladly see if that can fix it. Actually, I just did some digging - it seems the .ini that keeps spawning changes the binary path for SKSE to: Z:\SteamLibrary\steamapps\common\Skyrim\Mod Organizer\stylesheets I've tried to manually change it to the SKSE launcher executable, but the change won't "stick" - every time I restart MO the path has reverted back to the "stylesheets." In fact, if I manually set the path of SKSE correctly, select yes at the "You made changes to the current executable, do you want to save them?" prompt, if I reopen the edit tab it's already converted back to sytlesheets. This is all while the AV is disabled, MO is run as admin, and I've already taken ownership of the entire Z:\ drive. It appears to be a read/write or ownership issue, but everything looks to be set correctly. I'm stumped. BTW THANK YOU for actually trying to help with the issue instead of "derp that's weird." I'm very appreciative...

Decided to run through Skyrim again - its been a while and I wanted to try some of the newer mods that have come out. I usually manually install mods but wanted to try out MO. So far it's been...well, somewhat broken, and I'd like to find out why. I 've solved some of the frustrating issues with this forum and google - although I still can't make it past the "must download at least one file" part of the tutorial (even after downloading several mods from Nexus through the UI) at least I was finally able to get the thing to launch SKSE. Although that's fine and dandy, I have to go into the MO folder and manually delete the ModOrganizer.ini file EVERY TIME I want to start Skyrim via MO, otherwise it won't launch. And I'm not just talking about SKSE either, vanilla launcher gives the same "Executable "" not available" error. Has anyone had to deal with this crap and, more importantly, does anyone have a fix? I can see the use in this program, and would really like to start using it regularly, but this is ...

Thanks, guys - I had to go through both of these steps to get MO to download from the Nexus (in a vain attempt to get through the tutorial, which is broken) but at least the functionality is now there. Again, appreciate you sharing your knowledge...