Jump to content
  • 0
StuardBr

Falout 3 freezes on main menu if open via MO 1.3.11

Question

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 by StuardBr

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

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 :)

Share this post


Link to post
Share on other sites
  • 0

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?

Share this post


Link to post
Share on other sites
  • 0

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.

Share this post


Link to post
Share on other sites
  • 0

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

Share this post


Link to post
Share on other sites
  • 0

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

Share this post


Link to post
Share on other sites
  • 0

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?

Share this post


Link to post
Share on other sites
  • 0

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 by StuardBr

Share this post


Link to post
Share on other sites
  • 0

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?

Share this post


Link to post
Share on other sites
  • 0

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.

Share this post


Link to post
Share on other sites
  • 0

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 by StuardBr

Share this post


Link to post
Share on other sites
  • 0

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.

Share this post


Link to post
Share on other sites
  • 0

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.

Share this post


Link to post
Share on other sites
  • 0

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?

Share this post


Link to post
Share on other sites
  • 0

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.

Share this post


Link to post
Share on other sites
  • 0

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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By sheson
      This is a beta of [FNV|FO3|FO4|FO4VR|TES5|SSE|TES5VR|ENDERAL|ENDERALSE]LODGen/Edit with terrain LOD meshes and textures generation.
      This is for experienced mod authors and users that know how to use xEdit, xLODGen or DynDOLOD already.
      Installation and Setup
      Download
      xLODGen beta 85 - based on 4.1.4
      Unzip into a dedicated folder outside of any game and Steam folders or special Windows folders like Program Files.
      (Pro users can merge with existing xEdit installation. Make sure to overwrite older LODGen.exe/LODGenx64.exe TexConv.exe/TexConvx64.exe in Edit Scripts. All other files with the same filenames are the same as the latest version of xEdit.)
      Rename xLODGen.exe to [game mode]LODGen.exe (TES5LODGen.exe for example) or start with command line parameter -fnv, -fo3, -fo4, -fo4vr, -tes5, tes5vr, -sse, -enderal, -enderalse
      Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder.
      Do not generate into any game or any mod manager folders.
      Requirements
      Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 - Required by LODGen.exe/LODGenx64.exe and Texconv.exe/Texconvx64.exe. Get matching platform x86/x64 depending on which xLODGen.exe (x86) or xLODGenx64.exe (x64) is used.
      RTFM and Share Results
      See the included Skyrim-Occlusion-Readme.txt for a brief explanation of the Skyrim TVDT Occlusion data generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions or give feedback in the dedicated Skyrim TVDT - Occlusion Data thread.
      See the included Terrain-LOD-Readme.txt for a brief explanation of the settings for terrain LOD generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions about terrain LOD in this thread for a more in-depth explanation if required and share feedback (with screenshots) about results or problems.
      These tools generate LOD meshes and textures "exactly" like CK, but not like the meshes and textures which are shipping with the games (they are often manually edited).
      However, these tools provide more options and higher resolutions (use the x64 version if there are memory errors because you believe you require 4k or higher) and can be updated to add more useful features and options.
      I did some testing in the different games, but finding the best combinations of options and settings requires lots of testing and are a matter of personal opinion and which game is used, the load order, mods, even different worldspaces probably.
      That means, I am only able to give generic guidelines and hints to send you off to find and test for yourself and share your results. My main interested is that generations works correctly and without problems for now.
      Check out the thread xLODGen Terrain Settings Compare. Also refer to any modding guide which has a list of relevant mods close to your load order.
      The object and tree LOD generation is the same as the current versions of xEdit / xLODGen. Refer to their respective descriptions and explanations.
      Obviously, users of Skryim/Enderal/Skyrim SE/Skyrim VR/EnderalSE continue to use the easier and more comprehensive DynDOLOD for drastically improved object and tree LOD generation and only use xLODGen for terrain LOD (and maybe Occlusion) generation.
      First Time
      Here are suggestion to start without going crazy and that should be quick enough to generate:
      Set quality of meshes for LOD4 to 5 and then +5 for each next level. Or just set levels 8/16/32 to 10.
      Check protect cell borders (yes it fixes the ugly terrain drops at outer cell borders that still exist in Fallout 4).
      Use the max vertices setting only if you want to hard limit max file size.
      In Skyrim Special Edition or Skyrim VR, if you notice terrain briefly flickering when new areas are loading in, set [Display] bEnableLandFade=0 in Skyrim.INI
      Set Optimize Unseen to off for LOD4 for first generation. Start experimenting with a value of 550 with a quality setting of 10 or lower for LOD32 (used for map) and compare coastlines and file size to other settings.
      To quickly generate terrain LOD meshes just for the map, check only terrain LOD Meshes, check the Specific Chunk checkbox and set drop down to 32. Leave SW fields empty for complete map or set SW cell coordinates to same values as a *.btr filename to test a specific area with lots of water, river etc.
      Set texture sizes to 512 for a start. Larger sizes and large world spaces will take a considerable time (like 15 to 30 minutes or more easily). Each higher resolution means quadruple the work.
      Use DXT1 for diffuse and 565 (DXT1 if on Windows 7) for normal maps. If generating for Skyrim Special Edition use BC7. Uncheck mipmaps, raise steepness and Bake normal maps.
      For now, leave the Brightness, Contrast and Gamma at 0 and 1.0 respectively. It seems that only Skyrim CK and Skyrim SE CK are manipulating the intensity of the textures to adjust for the noise.dds and the god awful "improved" snow shader of Skyrim SE (just turn that thing off, really). If textures seem too dark in the game, brighten the noise.dds instead or vice versa. That way you can get perfectly matching LOD textures that look just like the textures in the loaded cells. For Skyrim a good average color of the noise texture seems to be around #C0. See below for a couple noise texture downloads.
      If you want to test larger texture sizes, use the chunk option to limit the number of textures that need to be generated. For example, check [x] Specific chunk, leave the drop down empty and set WS to the lower left cell coordinate of an 32x32 area, like 0, 0. It will then generate all textures up to 31,31. Not all worldspaces have their origin at 0,0 so you will have to check already generated meshes/texture filenames for their lower left coordinates.
      Questions and Feedback
      Obliviously anything related to terrain LOD should be posted in this thread.
      Posts related to Occlusion should be made here.
      Recommended Optionals
      TES5-Terrain-Tamriel.esm (Mega), SSE-Terrain-Tamriel.esm (Mega)
      TES5-Terrain-Tamriel-Extend.esm (Mega), SSE-Terrain-Tamriel-Extend.esm (Mega) - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm (Mega) - Entire map from -96,-96 to 95,96 with northern ocean extension. Useful for mod authors.
      Put in game data folder obviously. Adds back terrain for Skyrim (Tamriel worldspace) at the outer edges so there is no missing terrain meshes/textures when generating terrain LOD for Skyrim.
      Load as early with lowest priority as possible, so that any other plugins overwriting or adding land records or cells with the same coordinates take precedence.
      Only required to be loaded when generating terrain LOD. No harm done when loaded in-game but typically the player can not get close to these areas. There are no effects outside the far away added cells.
      Noise
      Single color flat noise, Adjusted vanilla noise, HD Terrain Noise Texture SE
      Examples for Skyrim. Install to game folder like any other texture mod. The noise texture is applied in-game on top of terrain LOD textures, so no effect for LOD generation.
      Only the red channel is used in case the textures is not a grey channel format. MipMaps are ignored. The textures is tiled 3x3 per LOD quad, e.g. for LOD level 4, the noise texture is repeated 3 times to cover 4 cells, for LOD level 8, the noise texture is repeated 3 times to cover 8 cells and so on.
      Test-Terrain-Tamriel.7z
      For testing terrain LOD distances. Plain color terrain LOD textures for Tamriel with coordinates for every LOD quad. Green for LOD 4, yellow for LOD8, blue for LOD 16 and red for LOD 32.
    • By se7enex
      Lucas Simms himself is missing his arms. I can see his gloves but his actual arms are invisible. I can't even begin to imagine what the fluff could be causing that. I did have issues with .32 and Mausers having big red exclamation marks but that's because it REQUIRES (listed in mod guide as optional) the individual weapon remakes. 

      Springvale Sewers, a AWOP location crashes consistently when I try to enter it. 

       
    • By Dennai
      Is there a way to make GaryBash work with MO in Fallout 3? I tried to use it as executable, but MO wouldn't recognized the Wrye launcher as such. It surprised me, because MO had no problem recognizing the Wrye Bash launcher for Oblivion, but I don't have the same luck with Wrye Flash. When I browse the Moppy folder to try to find the Binary, Wrye Bash Debug is the only application the MO can see.
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.