Jump to content

Bashed Patch crashes New Vegas on startup


Blamethegods

Recommended Posts

I've only installed two mods so far, User Interface Organizer and NVSE.

I built the Bashed Patch and tested the game, only for it to crash before the Bethesda logo could appear. I rebuilt the patch - still crashing.

I organized my small loadout in LOOT and then rebuilt the patch. Still crashing.

Without the patch, it runs just fine.

 

A little help? I plan on installing more mods and it'd be infinitely easier if the Bashed Patch worked.

Link to comment
Share on other sites

Your problem lies elsewhere. A "bashed patch" only resolves "record conflicts" between plugins, which UIO and NVSE neither have. They are: in the case of UIO: a premature install and non-existent conflicts until you have any mods installed which require it; and in the case of NVSE: an addon library of functions that only get used by mods that call for them.

 

Most likely your problem is either 1) missing a required system file such as the correct DirectX version files (see 'Issue: Vanilla game Hangs on startup'; specifically "Cause-1" regarding DirectX9 drivers; 2) your DLC "load order" is wrong; 3) you are missing a pre-requiste such as NVSE not being installed correctly (see the 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)' and the 'Checklist Item #4' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. This may be due to an on-going series of Windows Updates for the "Meltdown and Spectre Vulnerabilities".)

 

* Are you using the 4GB Patcher with the Steam version? (DO NOT use it with the GOG version, which is already patched. Applying the patch will break it. Revert to the backup copy created if you did run it.) If not, please see the 'Maximizing use of memory' section of the "FNV General Mod Use Advice" article. If you aren't sure if it was installed or working, just re-run the Patcher again. Make sure it's 4GB Patcher. Won't hurt and it will tell you if it is already patched. (If the Windows ("Task Manager" | Processes) tab entry for the game process has more than 2GB (2,097,152KB) "Memory(Private Working Set)" used, then the 4GB patch is definitely in effect. But being below that threshold doesn't mean it isn't.)

How can you tell if the 4GB Patch (for Steam) is working? The JIP LN NVSE Plugin (recommended for everyone) has a function which can be run from the console: "GetIsLAA" (not case sensitive).
Possible return codes:
* 0=patch is not applied
* 1=patch was applied to the executable, but extra memory is not being allocated
* 2=successfully allocated extra memory from the patch and is fully working.
If "GetIsLAA" is returning code "1", try running the game from a "local administrator" account. If that is successful, you need to move the game install location out of the "C:\Program Files" folder tree, or correct the "permissions" on the folder you moved it to, as you are going to have other problems down the road. Please see the wiki "Installing Games on Windows Vista+" article for details.
Alternatively: if the Windows "Task Manager" indicates the "FalloutNV.exe" program has more than 2GB (2,000,000KB) of "Memory (Private Working Set)", then the 4GB Patcher is in effect. However, to the contrary: less does not mean it is not working. The game simply hasn't needed that much memory as yet.

I recommend anyone read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with; especially if this is your first attempt to play a modded FNV or it's been more than a year since you last did so. It is designed for someone who has never played a modded PC game before, so it tries to avoid making any assumptions, is kept "up-to-date", and covers years of "lessons learned".

 

I also suggest the "STEP Fear-and-Loathing in New Vegas" guide as to which order to install basic mods. You may have additional mods or different ones you want, but they can be installed after any listed there.

-Dubious-

Link to comment
Share on other sites

So am I. From what you say you have installed, a "bashed patch" has nothing in it. It has nothing to do. I have no experience with what happens in that circumstance. For the time being, skip making one until you have mods that are attempting to change the same records.

 

-Dubious-

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...