Falout 3 freezes on main menu if open via MO 1.3.11

[StuardBr]

Hello guys!

 

I'm starting to play with fo3goty and i'm having some trouble in start.

 

I installed Steam version, started Fallout 3 Launcher, ultra setiings, play, tested a new game, everything ok. So, i installed FOSE. Tested him and ok too. Installed MO 1.3.11, default options, run FOSE and... the game freeze on main menu. I need to "Alt + F4" to exit. Tried open FOSE and Fallout3.exe and same problem. Tried open Fallout 3 Launcher too and it open without problems.

 

Searching what can be happening, i note that, if i go to the MO, create a new profile (test for a ex.), go to the "ModOrganizer/profiles/test" and put ANY ini file under "Read Only" and try to open FOSE or Fallout3.exe the thing start fine.

 

Tried copy the default ini files from "Users/MyUser/Documents/My Games/Fallout 3/" to "ModOrganizer/profiles/test/" and same problem...

 

Anyone can help me with this problem?

Edited July 3, 2017 by StuardBr

[StuardBr]

OK, i think THIS TIME i found the cause of the problem.

 

I reinstalled my system as i do every 6 months and with this, i can know if the problem is something in my PC. Backup, list of programs installed, etc... Reinstalled win10, drivers, steam and Fallout3 (and dependencies). Tested and ok. Installed FOSE, tested and ok, tested MO and... Ok too... So, let's install the other programs to test.

 

After reinstall all previous programs, the problem back. So, closing one after one, i found that a program that i use, OverWolf, is causing the problem with MO.

 

Overwolf provide some functionalities when i'm playing, like automatic gifs, statistics, etc but, to work,it needs to do some type of "overlay", like steam. This overlay is ok for FO3, but apparently is incompatible with MO. Closing the OverWolf in system tray solve the problem.

 

The only thing is in my head is, WTF a third party software will cause problems in the way the MO use the "archives.txt" and with some other mods... I found a post in the Nexus Forums (https://forums.nexusmods.com/index.php?/topic/1550213-freeze-on-startup-seems-to-be-induced-by-awop/) with a similar problem, but with the NewVegas. All is pointing to a mod problem, but in the end, was Overwolf too... I think is a good thing to put in the guide of STEP, close this type of program if problems appear.

 

Anyway, thank you all for the attention and help :)

[Kelmych]

Immediate failures when starting FOSE usually happen because there is a missing plugin file or the ini configuration or dll files in the the SKSE folder have an error. Does this happen when you are just using the vanilla FO3 files? It can also be caused by bad ini files in the profile folder. Did you use BethINI to create the INI files?

[StuardBr]

Immediate failures when starting FOSE usually happen because there is a missing plugin file or the ini configuration or dll files in the the SKSE folder have an error. Does this happen when you are just using the vanilla FO3 files? It can also be caused by bad ini files in the profile folder. Did you use BethINI to create the INI files?

1-Fose works fine when opened alone, without MO;

 

2- SKSE Folder? FOSE folder right? I have no mods installed, so, the folder is empty;

 

3- No, this don't happen if i open the original Fallout3.exe/fose_loader.exe WITHOUT MO;

 

4- Yes, i used BethINI, default ini files, everythine MO open Fallout3.exe or FOSE this thing happens.

[Kelmych]

Did you try starting FO3 using the vanilla Fallout Launcher through MO?

[StuardBr]

Did you try starting FO3 using the vanilla Fallout Launcher through MO?

Yes. I started Fallout launcher through MO, i can change configs and everyhing, If i hit Play, same issue, freeze on the  main menu

[Kelmych]

It sounds like there is a problem with the installed MO. Is MO or the game installed in a UAC Directory? Have you been able to use MO with any other Bethesda games?

[StuardBr]

It sounds like there is a problem with the installed MO. Is MO or the game installed in a UAC Directory? Have you been able to use MO with any other Bethesda games?

MO is installed in another HD, with the permission in the folder set to "Everyone" modify. If i delete the "ModOrganizer.ini", reopen the MO, choose Skyrim, Skyrim works fine. Tried some older versions, same problem.

 

PS: Run as administrator, same problem.

Edited July 4, 2017 by StuardBr

[StuardBr]

Well, i found a WORKAROUND about this problem...

 

For some reason, the "archive.txt" file, generated by MO in the profile folder is the cause of the problem... 

 

I tried remove the MO to manage the files, using the workaround option disable "force-enable game files" but NOTHING solve this thing.

 

The ONLY thing that "solved" the problem is, before launch the game, set the file to "Read-Only"...

 

Someone know why this happen?

[GrantSP]

Going back to your opening post, just how exactly did you install FOSE?

The actual DLL must be installed manually outside of the MO environment, only plugins that rely on FOSE may be installed via MO.

 

Since that is the only variable in your setup that is yet to be examined closely we'd like to know more about that. MO works "out of the box" with Fallout3/NV.

[StuardBr]

Going back to your opening post, just how exactly did you install FOSE?

The actual DLL must be installed manually outside of the MO environment, only plugins that rely on FOSE may be installed via MO.

 

Since that is the only variable in your setup that is yet to be examined closely we'd like to know more about that. MO works "out of the box" with Fallout3/NV.

Like i said, if I open WITHOUT MO, all works fine, but answering you, yes, FOSE was installed manually, in the data folder.

 

As i said in my last post is a MO file that cause the problem. If i use WITHOUT MO, everything works fine. If I use FOMM, works fine too. But, sadly, if i set "achives.txt" read-only as i said before, mods appear to don't work, so my problem persist...

 

I don't know what to try next... Maybe this is more one "Windows 10 x Fallout 3" bugs? I don't want to use FOMM or NMM, but i tink the MO is dead for me in FO3...

Edited July 9, 2017 by StuardBr

[GrantSP]

All that 'archives.txt' does is set the order of the BSAs, so make sure you have MO managing your archives AND that ALL the vanilla BSAs are checked in the 'Archives' tab.

 

Just did a check on my system and if I disable archive management and then re-enable it all the DLC BSAs are left unchecked which results in an instant crash.

[StuardBr]

All that 'archives.txt' does is set the order of the BSAs, so make sure you have MO managing your archives AND that ALL the vanilla BSAs are checked in the 'Archives' tab.

 

Just did a check on my system and if I disable archive management and then re-enable it all the DLC BSAs are left unchecked which results in an instant crash.

My problem isn't a crash, is a freeze in controls, like i said in the first post. And as i said in a previous post, i tried enable and disable but same problem.

[GrantSP]

Clear out the 'logs' folder, run it again and then post the logs here.

No one ever has reported a case like this or mentioned anything like the alleged culprit being archives.txt, it truly is a one in a million problem.

 

I can't replicate exactly your conditions because I have the retail disc version and none of the executables run in Win 10 except for FOSE, so I can't run FO3 outside of MO or call the game or the launcher from within.

However making any INI in my profiles read-only has no effect.

 

To clarify you have installed nothing with NMM or FOMM?

[GrantSP]

If you told us originally of ALL the software you had installed perhaps you could have sped up your resolution of this issue.

One of the stickied topics in the MO support forum is this which outlines the types of software that routinely interfere with MO.

 

At any rate I'm glad you can now continue with modding/playing your game.

[Kelmych]

It will be added to the list in the guide of overlays that cause problems with the Bethesda game engine and/or MO. Sorry it took so long to find it.