-
Posts
947 -
Joined
-
Last visited
Nexus Mods Profile
About Xaranth
Profile Fields
-
Country
United States
-
Currently Playing
Fallout: New Vegas
-
Favourite Game
Xenogears
Xaranth's Achievements
-
If you're not getting a missing master error in FNVEdit, it's almost certainly a broken or missing menu config file. Try renaming the 'menus' folder in your data folder to something else; see if it boots. If it does, you're in for some fun trawling of XML while you try and figure out just what include is failing hard on you.
-
[WIP] Russell, a new companion by Someguy
Xaranth replied to someguy2000's topic in Fallout New Vegas's Discussion
He should sing. :wink: Edit: Also, you have a footnote marker, but didn't put the footnote in...- 183 replies
-
Just deleting the ini files won't do you any good; some of them are constructed by the installer as opposed to the launcher. If the launcher isn't picking up your Video Card, make sure that (If you replaced the old one) your old drivers and device entries have been completely removed from Windows. If you just installed a new card and had been using, for example, onboard video, make sure that the onboard video is disabled in both windows and the bios. Then run FalloutNV's default launcher, and the setup options. If that doesn't work, completely reinstall FNV by: 1) Delete Local Cache through Steam. 2) Delete your SteamApps\Common\Fallout New Vegas\ folder through Windows Explorer. 3) Delete your My Documents\My Games\FalloutNV\ folder through Windows Explorer. 4) Reinstall FalloutNV through the Steam Library.
-
Full screen crash on startup
Xaranth replied to Merrt's topic in Fallout New Vegas's Mod Troubleshooting
So do I. :P They don't matter. @merrt - If the crash is only on full-screen, it's likely that you have a bad interaction going on somewhere with another program. Try running it in fullscreen mode at your native resolution, and start shutting down graphics apps - things like RadeonPro, CCC, nVidia Control Panel, etc. It might also be your AV if that's cranky. -
FNV uses three different inis, and which one it actually pulls the settings from is a crapshoot depending on how you launch the game and what kind of mood steam is in. In My Games\FalloutNV you need to edit Fallout.ini and FalloutPrefs.ini, and in SteamApps\Common\Fallout New Vegas\ you need to edit fallout_default.ini. More importantly, the default launcher WILL override changes to all three if it doesn't like them, so every time you launch the default launcher (FalloutNVLauncher.exe), you will probably need to re-edit those ini files.
- 11 replies
-
- resolution
- settings
-
(and 1 more)
Tagged with:
-
Crash when attemping to save
Xaranth replied to waterbottles's topic in Fallout New Vegas's Mod Troubleshooting
That's actually an FNVEdit foulup, not a game foulup. I know, I know, hard to believe. There's nothing wrong with a creature ref being an owner of stuff. :P That's an oversight by the FNVEdit guys. -
I'm hoping that's not sarcasm and that it worked; if it didn't work, please be less subtle about castigating me for providing the blatantly obvious troubleshooting step. :smile:
-
Go to one of the goodsprings houses and wait for four days.
-
That symbol means the game cannot find a mesh. This is a sign of one of three problems. A) A Mod was not installed correctly. - There are various ways to determine which mod it is. The simplest is probably to use the NVSE command 'GetBaseObject' on one of the items displaying the 'missing mesh' symbol, note the mod index, and figure out which mod is being loaded at that index. B) Archive Invalidation isn't working properly. - If using FOMM or NMM, toggle Archive Invalidation OFF, and then ON again. If using AII, find someone else to help you. C) Too many plugins loaded. - There is a well-known engine bug which prevents the game from properly addressing more than 139 plugins beyond the FalloutNV.esm plugin. Get those plugin numbers down.