Jump to content
  • 0
Sign in to follow this  
13thGeneral

Mod Organizer opens FalloutLauncher Replacer window

Question

For some reason this morning Mod Organizer has suddenly decided to start launching the FalloutLauncher Replacer when clicking the FOSE option within MO - selecting the 'Fallout 3' start option in MO crashes with an error (I'm at work, will post screen later) - and I cannot figure out why. The only change from two days ago is that I installed a new graphics card (updated drivers and DirectX 11 installed).

 

I click 'play' in Steam, it opens the FalloutLauncher Replacer, I press '3', MO opens, I select FOSE, click 'start' and it opens the FalloutLauncher again. Obviously I stop there and hit 'ESC' to Exit and close the FalloutLauncher - which crashes and Fallout.exe needs to be force-quit in Task Manager.

 

If I select option '1' after originally opening from Steam, the game client opens as expected - and the vanilla game runs fine from there.

 

I can't recall if selecting option '2' in the initial FalloutLauncher to run with FOSE works or not. I'll update later.

 

I know I've seen someone else post about this issue, but I cannot seem to located that particular thread discussion. - ah, nevermind, found it.

 

I'll check the fix found in the other thread, when I can tonight, though any help would still be appreciated.

 

Seems like I just can't ever completely get through the guide without some issue rearing it's ugly head. Thank goodness Fallout 4 is out soon...

Share this post


Link to post
Share on other sites

5 answers to this question

Recommended Posts

  • 0

It was brought up in the Nexus forums, in regards to my dilemma, that it's possible the .ini files were corrupted or not generated properly with the new graphics card settings. Also that I may have to reinstall the fINIp3 files as well.

 

Not sure this was the issue - as I'm not at home to test it - but its a possibility. I'll be trying it as soon as I can.

Edited by 13thGeneral

Share this post


Link to post
Share on other sites
  • 0

Just for the obvious troubleshooting, did you do a full uninstall of the prior device drivers (using a program like Device Driver Uninstaller)?  That's one of my preferred methods for resolving graphics related issues at the start, a clean uninstall for the install of the up-to-date drivers and such.  After that, definitely checking on the .ini's naturally.

 

<snipped by SergeTroy>

Seems like I just can't ever completely get through the guide without some issue rearing it's ugly head. Thank goodness Fallout 4 is out soon...

You do remember Fallout 4 is a triple A game, right?  Bugs Galore await ... :D  I'm probably just going to keep playing my 3 - 7 year old games and watch YouTube load up with vids on it, myself.

  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0

Just for the obvious troubleshooting, did you do a full uninstall of the prior device drivers (using a program like Device Driver Uninstaller)?  That's one of my preferred methods for resolving graphics related issues at the start, a clean uninstall for the install of the up-to-date drivers and such.  After that, definitely checking on the .ini's naturally.

 

You do remember Fallout 4 is a triple A game, right?  Bugs Galore await ... :D  I'm probably just going to keep playing my 3 - 7 year old games and watch YouTube load up with vids on it, myself.

lol, yeah, that was a slightly tongue-in-cheek remark. I expect a lot of bugs, though I'm at least hoping it doesn't crash as much as Fallout 3.

 

I did a "clean install" of the ini files but it's possible that they left residual settings. I just don't see how that would be creating this issue; I removed all the .ini files and launched the vanilla client to allow it to regenerate them, but I'm still having the issue.

 

UPDATE: Tried deleting and allowing the game to regenerate the ini files, again, and replacing them with the fINIp3 files, again, as well as checking BSA management and Archive-Invalidation were checked. None of that worked. I thought about it a bit, read the FalloutLauncher Replacer, FOSE, Mod Organizer, and fINIp3 install and setup instructions again, and looked at the guide instructions again, and... I realized I had forgot to copy the new ini files into the Mod Organizer profile(s).*

 

~facepalm~

 

So, in conclusion - SOLVED

 

*I've had a bit of a cold and blame it on the fever.

 

Edited by 13thGeneral
  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0

Congrats, as long as it got worked out at the end, no real issues.  Have to admit I didn't have much in the way of suggestions beyond regurgitating what I've picked up from Gopher and Kelmych's guides, etc., sometimes a little better phrased if you're an uber layman, like me, othertimes not so much.  :P  Yeah, once the comment was made in regards backing up the originals I went mad with that, making sure to back up and 'read only' the first launcher ini's as well as the fINIp3 when first set 'vanilla.'  I haven't done my current experimental-finale of the ini's, mostly because I'm still suspicious of things.  :shrugs.

Share this post


Link to post
Share on other sites
  • 0

Congrats, as long as it got worked out at the end, no real issues.  Have to admit I didn't have much in the way of suggestions beyond regurgitating what I've picked up from Gopher and Kelmych's guides, etc., sometimes a little better phrased if you're an uber layman, like me, othertimes not so much.  :P  Yeah, once the comment was made in regards backing up the originals I went mad with that, making sure to back up and 'read only' the first launcher ini's as well as the fINIp3 when first set 'vanilla.'  I haven't done my current experimental-finale of the ini's, mostly because I'm still suspicious of things.  :shrugs.

Yeah, I've been through the guide process several times, and each time encountering a different issue, resulting in having to start over. Luckily this time was just an oversight on my part.

I've been very meticulous this time around (4th.. 5th time??) in the installation and setup, so as to know exactly what is being done. This will teach me yet another lesson; esp not to mod while ill.

I'm dreading the Merge/Bash section, because that's where it gets a bit tedious and tricky.

 

Thanks for your help in getting my brain on the right track for the solution.

Edited by 13thGeneral
  • Upvote 1

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
Sign in to follow this  

  • 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.
      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, 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 BreadWiz42
      So, after following the Clear and Present Danger guide pretty thoroughly, installing everything needed, and making sure all cleaning and tweaks were done the game CTD's after character creation. The exact point is after FWE (or whichever mod) asks if you want the alternate start or not (I choose not) and right when the brightness clears it just CTD's. I've tried most "fixes" I could find on google and none I could find worked. I am just really stumped on what's causing the crash and hoping some here has any ideas.
      Here's the load order:


  • 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.