[Epic Games ver] Mod Organizer 2 fails and then runs from system instead.

[temakixai]

I've searched all over the internet for help with this and haven't been able to find anything to help.

Whenever I run the game from MO (I know you're meant to load the game's main executable, not the NVSE launcher), it starts to load the game and brings up the launcher window, with all the data files from mods visible, but then when I hit Play, it comes up with a number of flashes of command windows before Mod Organizer fails and the locked message disappears. Then the launcher window re-opens, but this time it has none of the mods' data files visible. it's as if it's instead ran straight from the disk and not from MO.

 

Before I picked this up from the epic games free game a few weeks ago, I also did the same with Fallout 3, and I didn't have this issue at all.

 

I have used the epic games patcher.

I'm running using the FalloutNV.exe or FalloutNVLauncher.exe (result is the same).

The game open and runs fine, it just won't actually run through MO and runs from the disk instead as described above. But I've gotten past the opening cutscenes and character creation without crashes or anything.

Even if I disable all mods, it still does the same thing. I even created an entire new instance and installed just one mod that was not likely to cause an issue just to test it, and the same issue occurs every time.

I've checked all the paths in MO.

I've tried running MO as an administrator and without.

I've tried disabling my antivirus.

 

I have some clips to show exactly what's happening if you would like to see it visually [LINK]

I also made a copy of the log file right after recording the above clip. [LINK]

 

I'm on Windows 10 Pro,

If there's any other needed info, let me know.

 

But this is highly annoying. I was interested in trying this game right off of completing the main story in Fo3, and set up a bunch of mods, and can't play it now. >:/

[showler]

It looks like MO2 is doing it's thing with the Virtual File system, but thinks that the Epic Game Launcher is the game itself. So as soon as the EGL stops, MO2 thinks you've shut down the game and it turns the VFS back off.

 

You need to figure out how to make it only turn off when you close the actual game rather than when that launcher shuts down.

[temakixai]

It looks like MO2 is doing it's thing with the Virtual File system, but thinks that the Epic Game Launcher is the game itself. So as soon as the EGL stops, MO2 thinks you've shut down the game and it turns the VFS back off.

 

You need to figure out how to make it only turn off when you close the actual game rather than when that launcher shuts down.

Your speculation is more insight than I've had in the past couple days so thank you so much for your input!

 

Now I just... have no idea how to do that XD

I have a basic level understanding of how mod organizer instances and file management works compared to other mod managers. but I don't know about virtual file system or what that is exactly.

[showler]

I stopped using MO2 because of quirks like this, but my first question would be whether MO2 is up to date. Epic's Fallout NV only came out recently and might have required an update to MO2 to deal with the EGL getting in the way.

[temakixai]

I stopped using MO2 because of quirks like this, but my first question would be whether MO2 is up to date. Epic's Fallout NV only came out recently and might have required an update to MO2 to deal with the EGL getting in the way.

Darn I thought you were on to something because I haven't thought about updating in ages. but I guess it does it automatically anyway and I checked and it says it is up to date.

But good idea though.

 

Yeah I think any mod manager is occasionally gonna have something buggy but I switched to MO years ago with skyrim sometime before the legendary edition even came out specifically cus so much was breaking due to file overwriting each other when I installed mods and I wanted MO because it keeps them all separate. It's much cleaner and has led me to so much fewer crashes and bugs than I had before.

But you're right in that the way it does things is weird enough that sometimes quirks happen. It's a trade-off I suppose.

 

 

Maybe someone else knows how to check the virtual file system or whatever it is.

Cus definitely something weird is going on with the launching process you're right.

 

I don't really want to have to resort to getting a crack just to isolate it from the epic store launching process if I can help it.

Edited June 15, 2023 by temakixai

[showler]

When I was googling for clues I saw a Reddit thread that had step by step instructions for modding the EGS version of FNV. I'm phone posting right now, but maybe you can find it?

[temakixai]

I'll give it a go!

[temakixai]

When I was googling for clues I saw a Reddit thread that had step by step instructions for modding the EGS version of FNV. I'm phone posting right now, but maybe you can find it?

I read through what I think is the page you were talking about, it said to rename the folder in the My Games folder to remove the _Epic suffix from the name. Unfortunately the game's launcher just remakes the folder and acts like it now has to redetect your graphics settings and stuff.

Which leads me to believe the game is using the ini files there, but I thought mod organizer had it's own place for the ini files, hmm...