Jump to content
  • 0
Sign in to follow this  

No Main Menu


Hi everyone,


I recently decided to do another playthrough of FO3/ FNV (with TTW) and I wanted to use MO instead of FOMM to do so. So EssArrBee's F&L guide was perfect (thanks so much!)


Now here comes the "however" and backstory:


I followed the guide to the T, but I did not install all the mentioned mods. Items I knew I wouldn't need/ use I excluded. But I did follow all the directions for the mods I did install. I did the "does it work" test after UIO and indeed, it worked fine. I had also installed TTW and some fixes by then. But as said, it worked fine. I was born!

So I merrily followed the guide to the end, picking the mods I wanted. Did the FNVLODGen, LOOT and BAshed patch. No missing masters etc. So far so good, eh?

Then finally I was ready to start the game, so I selected 4GB in MO, ran it and... "Exception 0xc0000417 (unknown software error)". Hmm, doesn't sound good. Went into MO and checked for errors. Nothing wrong! Ah wait... there is a newer version of MO! Duh. So I updated to 1.3.7. And tried again. YAY! It starts. I got the ENB Boost messages, but wait... there is no main menu? The background images loaded, but no Vaultec dude's head and no main menu to actually start the game. I had to close via Task manager.

So I went to this forum and I saw someone else also had this issue, but... apparently it was never resolved?? Anyway, I followed the suggestions made in that post. I extracted all the bsa's (except Spice of Life and the Bethesda bsa's). Alas, no change. The game also has no main menu/ Vaulttec dude head when I start with NVSE or the official starter.


So now I turn to you for help, my Brethren in Modding. Does anyone have any idea what could be causing this? Or more importantly, how I can resolve it?

Below is my mod list.


Thanks in advance!

[spoiler=Mod List]# This file was automatically generated by Mod Organizer.
+Bashed Patch
-Generated LOD
+Gun Runners Actually Run Guns
+Delay DLC - TTW
+A Few More Map Markers
+Armour Repair Kits
+CONELRAD 640-1240 - Civil Defense Radio
+Audleys Misc Textures
+no modulationttw
+ttwfixes 2 1 9
+Point Lookout Reborn
+SexoutNG - Data
+SexoutNG - Core
+Run The Lucky 38
+NVSE Extender
+TTW Fallout Character Overhaul
+Super Mutant Mesh Replacer v1
+Clean QuickSave
+citadel fix
+grave script fix
+Spice of Life
+Distributed Necklaces and Chains Neck Seam Concealer
+Type3 Body and Armor replacer
+nov 2011 book of steel
+BnB BodyExtender Compatability Skeleton
+Roberts Male Body
+New Vegas Redesigned 3
+Improved LOD Noise Texture
+Fallout Character Overhaul
+Animated Sweat Effect
+Wasteland Flora Overhaul
+Vurt's Flora Overhaul TTW Edition
+Interior Lighting Overhaul
+Old World Blues - Path Lighting
+NMC combined pack
+NVInteriors Project
+Traits Menu DarNified
+FNV Classic Worldmap
+Lutana's NVSE Plugin
+UIO - User Interface Organizer
+One HUD (oHUD) Darnified Patch
+One HUD (oHUD)
+darnui ttw 3 0alpha8
+The Mod Configuration Menu
+Project Nevada - Extra Options
+Project Nevada
+JIP Companions Command and Control
+Advanced Recon Thermal Nightvision
+Advanced Recon Range Finder
+Advanced Recon Trap Detection
+New Bison Steve Version 107 MASTER FILE VERSION
+NVAC - New Vegas Anti Crash
+NX 16
+Tale of Two Wastelands Options
+Tale of Two Wastelands Main
*Unmanaged: CaravanPack
*Unmanaged: MercenaryPack
*Unmanaged: TribalPack
*Unmanaged: ClassicPack
*Unmanaged: GunRunnersArsenal
*Unmanaged: LonesomeRoad
*Unmanaged: OldWorldBlues
*Unmanaged: HonestHearts
*Unmanaged: DeadMoney
*Unmanaged: FalloutNV


Share this post

Link to post
Share on other sites

7 answers to this question

Recommended Posts

  • 0

Thank you guys for the tips!


Unfortunately they didn't have any effect.

So I decided to do the tedious thing and unticking all the mods I added since I knew it DID work (up until UIO) and then adding them back in blocks of 3. After adding these blocks of mods, I LOOTed and Wrye Bashed. And of course, the very last one I added back was the culprit... It was a TTW Quest mod called "Point Lookout Reborn". This mod apparently had two different ESM, because I didn't merge but overwritten (DUH me). After "optionalising" one of them, I got the Vaultec Dude head and the menu overlay! YAY! So it wasn't actually a F&LNV issue.


Unfortunately I am aware that this was a very specific issue that not many people will have, unless they also use this mod and have two ESM. For others who may not get the main menu overlay: this issue is (I expect) very similar to not hiding BSA's after extracting them and/or setting esm/esp from merged patches to optional! So make sure you check, double-check and even triple-check if you indeed did that.


Thank you for the help and I hope this will help someone else in the future.


- Moo.

Edited by Vachnic

Share this post

Link to post
Share on other sites
  • 0

I was having the same problem, but I read in another thread about this. Adding SRB's INI tweak worked for some, but not me. Further down in the thread a guy figured out his extra weapons was somehow causing it. Disable that plugin, all the weapons, and rebuild the bashed patch. That worked for me.


Here's the link in case you don't see it: https://forum.step-project.com/topic/7741-fonts-do-not-display-in-main-menu/

Edited by AtomicFire

Share this post

Link to post
Share on other sites
  • 0

Sometimes merges get messed up since it's trying to combine a ton of records and not everything goes according to plan. Just disable the merged plugins one by one and see it that fixes it. Then find the one that messed everything up and redo it.

Share this post

Link to post
Share on other sites
  • 0

Hey EssArrBee! 

Thank you for making such a detail modding guide for Fallout New Vegas! I can't wait to jump on in and start playing once I get everything fixed up. 


I did run into the same issue as Vachnic though and my menu and mouse were gone completely once I started the game. I would alt-tab and it would then crash.


I followed your advice on unticking all the Merged Plugs and I found that Millenia's Additional Weapons and EssArrBee's Additional Weapons were causing the issue for some strange reason. It seems both of them are doing something they shouldn't (or at least one of them is)


Did I do something wrong when I was following the guide? Should I just simply redo the merge for both of them? 


Thank you for the help! 

Share this post

Link to post
Share on other sites
  • 0

Maybe retry the merge, but I'm going to update those pages to be in line with 1.9 of the merge script. I was absent from STEP for a while and now I'm updating the guide bit by bit. Should be done later today.

Share this post

Link to post
Share on other sites
  • 0

I believe it was the Additional Weapons page. It was out of date until yesterday.

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 Drak
      Hello There,
      I did a fresh install following STEP recommandations (FNV not in program files, modding directory neither, I started FNV after installing it).
      I can start the game with all mods from STEP except Step Patch - Conflict Resolution.

      I tryied to pinpoint my problem and as soon as I add the Step patch (then LOOT order dirladada) I get the following error in 
      nvac.log :
      23190643 _ NewVegasAntiCrash FalloutNV.exe
      23190643 _ 17E90000 07050000 nvac.dll
      23190643 i 008BFBC1 0441B60F FalloutNV.exe
      23190643 _ 17AE0000 06020050 nvse_1_4.dll
      23190643 _ 77170000 0A004A64 ntdll.dll
      23190646 a 0072607A 0048A1DF FalloutNV.exe
      23190647 h 181A42EB 8B48088B nvse_stewie_tweaks.dll (100342EB)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 h 181A42EE 8B01FF10 nvse_stewie_tweaks.dll (100342EE)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 h 181A42F0 FF1068F0 nvse_stewie_tweaks.dll (100342F0)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 m 000003EC 219C46E0
      23190647 r 10001432 00000009 d3dx9_38.dll (10001432)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 h 100034E0 834104FF d3dx9_38.dll (100034E0)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 h 100034E6 C7010000 d3dx9_38.dll (100034E6)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 u 00F0B4FA C0000409 FalloutNV.exe
      23190647 ! CRASHSAV E_FAIL_0 FalloutNV.exe
      23190648 q 00F0B4FA C0000409 FalloutNV.exe
      23190648 ! CRASHSAV E_FAIL_0 FalloutNV.exe
      I also tryed to use Cobb Crash Logger 
      Cobb Crash Logger Version 3.0.0, build 0.
      If this file is empty, then your game didn't crash! Probably!
      Exception C0000409 caught!
      0x00F0B4FA ==> EntryPoint+0xFFFFFFFF in FalloutNV (0x0019F138) 
      0x771F88B4 ==> RtlInterlockedCompareExchange64+0x1B4 in ntdll (0x0019F204) 
      0x771E4EE6 ==> KiUserExceptionDispatcher+0x26 in ntdll (0x0019F208) 
      0x0019F21C ==> ¯\(°_o)/¯ (Corrupt stack or heap?)  (0x0019F20C)
      0x0019F26C ==> ¯\(°_o)/¯ (Corrupt stack or heap?)  (0x0019F21C)
      GAME CRASHED AT INSTRUCTION Base+0x00B0B4FA IN MODULE: C:\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe
      Please note that this does not automatically mean that that module is responsible. 
      It may have been supplied bad data or program state as the result of an issue in 
      the base game or a different DLL.
      Help welcome, I am at a loss..
    • By z929669
      Step Fallout: New Vegas Guide 1.0.0 released!

      Guide Link | Changelog | Feedback & Bug Reports
      Nexus Link
      Many thanks to @Majorman for working on this guide for the past 6 weeks as our official FNV guide Curator!
    • 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
      xLODGen beta 86 - based on 4.1.4b
      Unzip into a dedicated folder outside of any Steam, game or mod manager folders or special Windows folders like Program Files.
      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.
      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.
      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.
      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.
  • 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.