Jump to content
  • 0
grimZan

Massive falloutprefs.ini duplication in Mod Organizer

Question

Searched the whole world wide web without seeing this problem (close to it).

I use Mod Organizer for my Fallout 3 modding, and STEP has been my grail, mostly. I've modded for awhile now, so knowing what is hazardous and not, I follow STEP for MO since it's a new tool. After getting a fairly modded FO3 and running stable for hours of play, I head into the sewer entrance near Super Duper Mart, and go into county mainline sewers. Save inside, then try to load and it starts crashing. Others have had issues with this, but I don't think this is my problem.

 

I have quite a few exe's running through MO to get everything working and stable, FO3, then FOSE, with FOMM for the UI mods, then Fallout 3 Fullscreen mod, which btw is a lifesaver practically eliminating CTDs. Trying to start again the FO3Fullscreen says, "error: #maxmem full, shutting thread" and after lots of research I find my falloutprefs.ini for the MO profile has grown. A lot. Where it was 3 kb it's now 80 mb. Pull it up in Notepad ++ and what happened is the entire file has copied itself into itself, probably thousands of times, so much that I thought after hitting CTRL + END it locked up, just took awhile to get to line 3 million plus. After deleting the excess the game was perfectly playable, but it starts copying and growing like before. Thought I could make it read only, but MO won't let you run it with the RO flag. Thought it might have to do with the multiple exe's, but I've not found this problem, yet. Any ideas would be appreciated. Running 85 plugins, so let me know if you want the list, but mostly the major, popular mods, not much else.

Share this post


Link to post
Share on other sites

8 answers to this question

Recommended Posts

  • 0

Further to what @GSDFan said, try running it again then quit and examine your ini. If it is duplicated then you know it is happening each time the game initialises. Then I would try running the game without your fake fullscreen mod, whichever one that is, I know of at least three. If the ini is fine then you can safely say that's your culprit. That's what I'm placing my money on.

 

Then you will either have to try another one, determine the correct settings for the one you have or not use it.

If you are really desperate you could keep a copy of the correct ini and write a batch file to copy over the old with the new, fresh one before each game. That's only if you are really desperate though.

Share this post


Link to post
Share on other sites
  • 0

I can"t say anything specific for this problem, but make sure that no other programs loaded through MO are holding falloutprefs.ini, or any other file for that matter, open when running the game. If they are the file will grow as the file will not be released by that program when another tries to access it.

Share this post


Link to post
Share on other sites
  • 0

Hey guys, thanks for replying, would've seen these and responded sooner, but even though I have my settings to email me when I get a response, it didn't. :)

 

Anyways, Grant you were dead on. The Fullscreen mod I use (which is the Fake Fullscreen Mode Windowed - Alt Tab Fix by BUDA20) was increasing the size of the ini everytime I launched the game, exponentially, which is why it was so large after just a few times of use. Switched to using the other program he made called Game Companion, although I have to add the executable in to MO, launch it, unlock MO so I can open a second exe, then launch FOSE. Don't know if this is recommended, but it works for now. STEP doesn't seem to use any of these tools, just seems like a setting in ENBoost for borderless windowed mode might be their replacement.

Share this post


Link to post
Share on other sites
  • 0

Yep, that's what is the preferred method.

Unless there is a specific reason why you really need to run those type of tools, I would try and not use them. I am in the lucky small percentage of people that has never had any issues with alt-tabbing out of any of my games, so that means my view is biased.

Share this post


Link to post
Share on other sites
  • 0

Well my game runs great and it's stated that the performance drop is small, so I will have to switch and see if it eliminates all these problems. Thanks again.

Share this post


Link to post
Share on other sites
  • 0

I have a similar issue with my newly modded Fallout New Vegas setup with MO.   I too am/was using the fake full screen executable, but I did setup through MO to be used and it worked once just fine and no more.

 

Someone suggested that I make sure that the the .ini file had the correct 'windowed' setting in the .ini file and what is when I discovered that my FalloutPref.ini was 42mb in size.  Can I simply copy over my 'base' or 'vanilla' .ini file without any ill side affects?

Share this post


Link to post
Share on other sites
  • 0

The ini files in your MO profiles are just copies of the default inis in your My Documents folder, with some changes you may have made. Copying the original over the expanding error-filled inis is fine, although you will need to add back any specific changes you made to them.

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 83 - based on 4.1.3g
      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. Use this if a mod manager with a virtual file system (like MO) is used.
      Do not generate into any game or any mod manager folders that are part (direct or indirect) of the virtual file system.
      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, SSE-Terrain-Tamriel.esm
      TES5-Terrain-Tamriel-Extend.esm, SSE-Terrain-Tamriel-Extend.esm - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm - 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 fireundubh
      I completed my update to the bash tag autodetection script.
       
      Behold: Bash Tagger! View/Download
       
      Supported games:
      Fallout 3 Fallout: New Vegas Skyrim* *Not completely tested; limited support currently

      If anyone is willing test, I'd be grateful for your feedback. Suggestions for a better name are welcome, too.
       
      Requirements:
      xEdit svn1839 or older, or xEdit svn1876 or newer (latest xEdit dev version) patience a credit card Instructions:
      Download the script to your FNVEdit "Edit Scripts" directory. Run FNVEdit and load the plugin you want to test. Right-click that plugin and click Apply Script. Select the script and click OK. Like the original script, you can run the script on only one plugin at a time.
       
      Roadmap:
      v1.1 - Initial release (based on zilav's BASH tags autodetection v1.0 script) v1.4 - Mostly complete TES4 and TES5 support v2.0 - No bugs whatsoever
    • By lv1234
      I have tried forcing fawkes to use the melee option in game but he keeps using his gatling gun. With the melee option, he should be using ranged against enemies far away and melee when enemies are close. I even tried giving him his super sledge but no luck there either. Weirdly enough this goes same for all of my companions even when I force them to use melee. After further testing and narrowing down the issue, it seems that arwen realism is the cause of this issue since this only occurs when arwen realism is activated. Could someone else verify this also?
      Current load order nontest: https://pastebin.com/mTFbdAHt
      Current test load order with arwen realism: https://pastebin.com/
      As for how I Installed the arwen realism mod, I simply installed it by downloading it and adding it through MO2 which prompts a fomod setup install for the mod and chose my selected arwen plugins above accordingly. 
  • 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.