Jump to content
  • 0
Sign in to follow this  
jackdaeuble

New Vegas will not launch thru Mod Organizer

Question

I'm using this new patcher https://www.nexusmods.com/newvegas/mods/62552/?tab=12&navtag=http%3A%2F%2Fwww.nexusmods.com%2Fnewvegas%2Fajax%2Fmodchangelog%2F%3Fid%3D62552%26v%3D&pUp=1

 

I ran the exe, it patched my game exe, and I can launch the game if I directly launch the exe's from the game folder. However, if I try to launch them via Mod Organizer, I get "FalloutNV.exe has stopped responding". I don't know what the cause of this issue is, and googling the issue has solutions that don't work for me. Anyone got anything?


I would also like to note that I just tested launching thru MO without the patcher installed, and it still did not launch. Gave me the same not responding error as before.

Share this post


Link to post
Share on other sites

9 answers to this question

Recommended Posts

  • 0

Are you sure you are running the patched game executable and not the launcher or NVSE?

I've been using that patcher since Roy first released it and there are no inherent issues with the process, in fact it is noticeably faster on execution and less fiddling in MO to get it set up.

 

Assuming you are doing things correctly, try a redo of your MO setup. Delete the ModOrganizer.ini and set things up again.

If you wish you can post that ini here first so we can examine it.

Share this post


Link to post
Share on other sites
  • 0

Try redoing the INIs in MO. Or deleting the INIs in the documents folder and running from Steam one more time.

I deleted all of the INI's for Mod Organizer, as well as the INI's in my games and the specific profile INI's, and it works. I'm not sure what tweaks I made that caused the issue, but it's resolved. Thank you!

Share this post


Link to post
Share on other sites
  • 0

Are you sure you are running the patched game executable and not the launcher or NVSE?

I've been using that patcher since Roy first released it and there are no inherent issues with the process, in fact it is noticeably faster on execution and less fiddling in MO to get it set up.

 

Assuming you are doing things correctly, try a redo of your MO setup. Delete the ModOrganizer.ini and set things up again.

If you wish you can post that ini here first so we can examine it.

Created an account here just for this problem. I was following Fear and Loathing guide and everything was working until I got to the 4GB patch step. The Nexus link takes you to the deprecated mod so I downloaded the new patcher and ran it. Now the game stops working when I try to launch. I went ahead and downloaded the original 4GB file listed. I can launch the game by double clicking fnv4gb.exe as well as nvse_loader.exe from the root folder but whenever I try to launch them via Mod Organizer the game crashes at launch.

 

I deleted the FO NV .ini files in My Documents as well as MO .ini and it's still not working. I have Windows 10 which I have read may be an issue. I also already have the ENB wrapper version files version 308 (from classic Skyrim) successfully installed.

 

Any help is appreciated

Edited by Rescorla

Share this post


Link to post
Share on other sites
  • 0

Created an account here just for this problem. I was following Fear and Loathing guide and everything was working until I got to the 4GB patch step. The Nexus link takes you to the deprecated mod so I downloaded the new patcher and ran it. Now the game stops working when I try to launch. I went ahead and downloaded the original 4GB file listed. I can launch the game by double clicking fnv4gb.exe as well as nvse_loader.exe from the root folder but whenever I try to launch them via Mod Organizer the game crashes at launch.

 

I deleted the FO NV .ini files in My Documents as well as MO .ini and it's still not working. I have Windows 10 which I have read may be an issue. I also already have the ENB wrapper version files version 308 (from classic Skyrim) successfully installed.

 

Any help is appreciated

If you ran the patcher then the executable that you call needs to be the newly patched exe. DO NOT try and run the NVSE loader or the previously used patch.

FNV4GB.exe, and any files in the 'exes' folder should be removed from your system as they are no longer needed. This means you should also ensure your executables list in MO is pointing to just the game, nothing else.

Share this post


Link to post
Share on other sites
  • 0

I've updated the guide to include the newer patch and removed all references to the older one.

Share this post


Link to post
Share on other sites
  • 0

If you ran the patcher then the executable that you call needs to be the newly patched exe. DO NOT try and run the NVSE loader or the previously used patch.

FNV4GB.exe, and any files in the 'exes' folder should be removed from your system as they are no longer needed. This means you should also ensure your executables list in MO is pointing to just the game, nothing else.

I have run the 4GB patcher and the FalloutNV.exe file is dated yesterday when I ran it.   When I use MO to launch FalloutNV.exe, all I get is a black screen.  I can't even alt-tab or kill the falloutnv.exe in Task Manager.  I have to ctrl-alt-delete and signout of Windows 10 completely in order to get out of the game.   

Share this post


Link to post
Share on other sites
  • 0

What happens if you delete the patched game exe and run the unpatched exe from MO?

If you can run the game from that then the patching process is broken, try running the patcher as ADMIN as detailed on the patcher's Nexus page.

If you also go to a black screen with the unpatched exe then the current profile in MO is not loading all the required assets.

Share this post


Link to post
Share on other sites
  • 0

What happens if you delete the patched game exe and run the unpatched exe from MO?

If you can run the game from that then the patching process is broken, try running the patcher as ADMIN as detailed on the patcher's Nexus page.

If you also go to a black screen with the unpatched exe then the current profile in MO is not loading all the required assets.

I deleted the patched file and redownloaded from Steam.   Confirmed the game will launch pointing to the default falloutNV.exe with MO.  Ran the 4GB patcher and was able to successfully launch with MO.

 

No idea what the problem was but it appears to be working now.

 

Now on to the next step of the guide.

 

Thanks for your help

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 Majorman
      Discussion topic:
      FNVLODGen by zilav
      Wiki Link
    • 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 Majorman
      Discussion topic:
      ShowOff NVSE Plugin by The Dormies - Demorome and Trooper
      Wiki Link
  • 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.