Landon Bablandananavan Posted May 31, 2019 Posted May 31, 2019 So first off thanks for reading what's sure to be a long winded question Next, what all I've got: Win 10 16 GB of RAM running on a 1 TB SSD drive, nVidia GTX1080 w 16 GB of RAM. The current version of FO4 - 1.10.130 I believe The current version of F4SE - 0.6.16 rel 19 I use Mod Organizer 2 - v 2.2.0 rev 179a738 which is set to run using admin privileges I hadn't played Fallout in a while and a couple of weeks ago got the urge so I fired up MO2 and after many updates, started F4SE. I got a brief black screen as if the game were starting up but then it closed and I was back to MO2 which quickly closed the "MO is locked while the executable is running" pop up. Much fruitless troubleshooting takes place and I now know the following: Validated the install files using Steam. I'm able to start the vanilla game from Steam and get to the main menu so it seems that the problem isn't with the game itself. Removed all of the mods and tried starting F4SE via MO2 which gave me the black screen then back to MO2 just like before. Glad I have a copy of the mods I can't recall if I created them or MO2 did so automatically, but in my run list I have Fallout and the Fallout launcher. I tried running Fallout from MO2 (it's running C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Fallout4.exe) and got the black screen then back to MO2 again. The Launcher does run normally though. If I open the C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\ folder and select F4SE_Launcher.exe and run it with admin privileges it starts the game up - progress! Except it doesn't seem to be running any of the brief list of mods I've reinstalled. The Settings menu off of the main menu does indicate F4SE is running but Looks Menu doesn't come up when I start a new character. For what it's worth I also use MO2 for both Skyrim LE - the non-Steam version, and Skyrim SE - the steam version - and both of them start up just fine. Before I wipe and restart from scratch, does anyone have any suggestions? Thanks again!
D_ManXX2 Posted June 1, 2019 Posted June 1, 2019 try launching the game from the normal executible first and see if it works outside of mo. if it does make sure mo is run as adminitrative rights and the executible of fallout 4 is also run in administrative mode. Also you could try deleting ini files and let the fallout 4 regenrate them again bad ini edits can cause all sorts problem espeicially if you also run with mo2. btw what version of mo2 are you using you could always try the latest version sometimes previous version has bugs in them and newer one fixes those for you. Are you using the same mo2 for all games ? you can only use 1 mo2 per game so if you use mo2 for skyrim you need to create a new mo2 with a different game you cannot use the same mo2 for different games but you can install multiple copies of mo2 and use each for different games.
Landon Bablandananavan Posted June 2, 2019 Author Posted June 2, 2019 Whatever it is it's got to do with MO2, which is running the most recent version and starts as Admin. I tried a wipe and re-install of F)4 and got pretty much the same thing. Then on a whim installed Nexus' Votrex and when I run F4SE from it everything seems fine. Next is trying to get all those many many mods moved over. Thanks for your suggestions
Nebuchadnezzer2 Posted June 3, 2019 Posted June 3, 2019 On 5/31/2019 at 9:44 PM, akaTwoSheds said: The current version of FO4 - 1.10.130 I believe The current version of F4SE - 0.6.16 rel 19 I use Mod Organizer 2 - v 2.2.0 rev 179a738 which is set to run using admin privileges F4SE would tell you if the version mismatched, and those are both the latest. On 5/31/2019 at 9:44 PM, akaTwoSheds said: Validated the install files using Steam. I'm able to start the vanilla game from Steam and get to the main menu so it seems that the problem isn't with the game itself. Removed all of the mods and tried starting F4SE via MO2 which gave me the black screen then back to MO2 just like before. Glad I have a copy of the mods I can't recall if I created them or MO2 did so automatically, but in my run list I have Fallout and the Fallout launcher. I tried running Fallout from MO2 (it's running C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Fallout4.exe) and got the black screen then back to MO2 again. The Launcher does run normally though. If I open the C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\ folder and select F4SE_Launcher.exe and run it with admin privileges it starts the game up - progress! Except it doesn't seem to be running any of the brief list of mods I've reinstalled. The Settings menu off of the main menu does indicate F4SE is running but Looks Menu doesn't come up when I start a new character. For what it's worth I also use MO2 for both Skyrim LE - the non-Steam version, and Skyrim SE - the steam version - and both of them start up just fine. Good start, at least. Did you install F4SE via MO2 or manually? It's doable via MO2, but much more work, and manual works out simpler and easier to use/fix if something breaks. The Non-starting sounds like something's not being loaded correctly, like an *.esm. And yes, MO2 automatically has Fallout4.exe and the Launcher.exe as available executables by default. I assume when you're running F4SE via MO2, you're doing so the same way? [Added as an executable, while the f4se_loader.exe sits in the same folder as Fallout4.exe, run via MO2] Due to how MO2 works [VFS] you need to run everything through it, or it won't find any of the files, as you found out running F4SE as admin Set F4SE to run as admin in it's properties [compatibility, run as admin checkbox at the bottom], and ensure MO2 runs as Admin as well. I'm also curious if you've deleted the base *.ini's the game creates, and run the Launcher to re-generate them, or if you've still got modified *.ini's through MO2 that are causing issues. INI editor & window that comes up. Be sure to hit 'save' at the bottom when you're done. Alternatively can hit the small folder icon with a dropdown above your mod install list, and select 'open INIs folder', and do it that way. Just don't mess with the other MO2 created *.ini's in there. Can also delete those and re-run the game launcher, and that should sort them out. You can also click on the Data tab and look at what files are attempting to be loaded and along with the Plugins tab, ensure there's no issues there either. In particular, if you're disabling everything, those two can help you check that everything's unloaded. The another thing to check is MO2's file paths [Spanner & Screwdriver icon]. Other than that, as MO2 also mentions at the bottom of the Paths tab in settings, "Important: All directories have to be writeable". Friend of mine had issues with that getting started recently. Also look in the Workarounds tab under Settings, and make sure 'force enable game files' is checked. (I will laugh if that's what caused the issues, even if I feel bad while doing it :P)
Landon Bablandananavan Posted June 5, 2019 Author Posted June 5, 2019 I fear that I've fiddled with it just a little too much cause now Skyrim LE is behaving oddly as well. It loads but the screen looks - for lack of a proper term - like looking through a car window during a heavy rain. Very interesting but pretty unplayable As my saintly old father used to say "if it don't work, hit it with a hammer, if it breaks it was time to replace it anyway". I've hammered and now - metaphorically - it's time to replace it any way Just in case someone else manages to FUBAR things in a similar manner and might find some use from this: I installed F4SE manually, I wasn't even aware that there was a way to do it using MO2. Yes, I manually added the F4SE executable - f4se_loader.exe - to the MO2 loader. It's located in the F)4 directory per the F4SE readme. Both MO4 and the link to F4SE are set to run as admin. I hadn't checked the INI files, but since I reinstalled FO4 that's probably moot, right? After the re-install I was still unable to run F4SE from MO2, but it loaded up fine using Vortex. Of course I have other problems with Vortex most likely due to not having half a clue what I'm doing with it Thanks for your help, I'm off to back up saved games, presets, and load orders
Nebuchadnezzer2 Posted June 5, 2019 Posted June 5, 2019 35 minutes ago, akaTwoSheds said: I hadn't checked the INI files, but since I reinstalled FO4 that's probably moot, right? After the re-install I was still unable to run F4SE from MO2, but it loaded up fine using Vortex. Of course I have other problems with Vortex most likely due to not having half a clue what I'm doing with it That's only 'moot' when you delete them, as they're created by Fallout 4 when it "first" runs, and isn't considered part of the install. Deleting them and running Fallout 4 via it's launcher re-creates them. If reinstalling F4SE doesn't solve the boot from MO2, check that the executable is running from the right file/folder [Start in:C:\Program Files (x86)\Steam\steamapps\common\Fallout 4, Binary:C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\f4se_loader.exe, for mine]
D_ManXX2 Posted June 5, 2019 Posted June 5, 2019 Also have you tried making shortcut from Mo2 link of f4se on your desktop and tried launching fallout 4 through that ?? this method will not load all of mo2 only vfs will loaded i did noticed when doing this mo2 loading fallout 4 more quickly.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.