Large Address Aware flag (>2Gb)

[Deathlok]

I tried CFF Explorer, the same way I had for Oblivion and Fallout 3, but it didn't work with Fallout New Vegas. I got an error when I tried to start the game, which I resolved by turning that flag back off through CFF Explorer (thankfully, as I didn't bother making a backup).

I have a Windows 7 64-bit machine with 12Gb of RAM. Is there an easy way to set the LARGEADDRESSAWARE flag for this game, something that won't require other mods or script extenders?

Does the failure of CFF Explorer have anything to do with Steam DRM?

[Mauno]

I remember doing LAA this way after launch, but it seems some patch broke it.

You can use the 4gb fix found here[newvegas.nexusmods.com], to make the game use more than 2gb, works well and significantly reduces crashing.

Edit: Scratch that, you asked for no mods. Eh, can't think of another way.

[Deathlok]

It doesn't seem to REQUIRE other mods or script extenders, unless I'm missing something.

[Mauno]

Right, yeah. The 4gb fix doesn't require any other changes / mods. There's a compatible version for the NV script extender, if you any mods you install require that too.

[Deathlok]

Oddly enough, the game has only crashed on me once, and I was really asking for it then--I accidentally tried to Quicksave during a fight, while someone was swinging a lance at me. Fallout 3 crashed all the time, even with the RAM fix. New Vegas runs a LOT better on my 64-bit Windows 7 machine than the older Bethesda games do.

I have noticed more stutter now that I've logged more hours, as I get further into the game world. So I might look at this RAM fix over some weekend.

[Xilandro]

Quick guide for everyone who have problems with running 4gb enabler (Win7)
Get the latest NVSE version. http://nvse.silverlock.org/beta/nvse_3_beta2.7z
Get the alternative 4gb loader http://nvse.silverlock.org/beta/fnv4gb_nvse.zip
Install NVSE
Install alternative 4gb loader
create a loader shortcut on your desktop. Right click. Click properties.
Add into target line -SteamAppID 22380
it should look like this:
"blablabla\SteamApps\common\Fallout New Vegas\fnv4gb.exe" -SteamAppID 22380
just like here http://img832.imageshack.us/img832/7651/39237013.jpg

Apply. Run. Play.

[Mauno]

So many necromancers among us. Scary.

[Boiling Mercury]

Thanks for the links Xilandro and for the tipp with that -SteamAppID 22380 line thing. I didn't used that with the 4Gb loader and allways wondered why all the game related things in the Overlay including Achievements weren't available.

Edit: is there a reason to use the beta version 3b2 instead of 2b12?

[Xilandro]

as far as i know many modders make mods based on 3b2, and also it's more stable than 2b12

[Boiling Mercury]

Ok thanks for the fast answer. I upgraded to 3b2 and using the 4GB loader direct from silverlock instead of the "alternate loader" on the nexus, which doesn't quite work properly with that version of NVSE and messes with DarnifedUI. Oh and if You add -SteamAppID 22380 at the end of the shortcut's targetline it just starts the game launcher... It's still kind of a shame that that Overlay stuff like Guides and Achievements don't work if you're using the 4GB Loader.

Thanks anyway!

[Deathlok]

Perhaps Bethesda can hire younger programmers who are aware computers typically have more than 2 GB of RAM? Maybe they'll even find someone who can write multi-threaded code.

[Mauno]

They use monkeys to write their dialogue and stories.

How likely do you think it is they would hire actual people to do work meant for actual people?

[Boiling Mercury]

Let's hope things get better with the new XStations and PlayBoxes have "much" more RAM and forced multithreading due to low single core clocks.

[Mauno]

Oh, by the way UberMercury:

Originally posted by UberMercury:

It's still kind of a shame that that Overlay stuff like Guides and Achievements don't work if you're using the 4GB Loader.

About this.

If you replace your FalloutNVLauncher.exe with the 4gb mod's exe, you CAN get all the Steam features in-game. Just back up the original launcher and rename the 4gb loader's exe to FalloutNVLauncher.exe, then fire up the game through Steam as usual. Works just fine.

[Boiling Mercury]

Sorry for posting in that high frequency I don't want to spam, but this doesn't work for me. Either with the 1.2 silverlock version nor the nexus 1.6. Mayebe I'm doing it wrong.
I place the fnv4gb.exe and the helper.dll in the game's folder (I know, not necessary), start fnv4gb.exe and a little loading bar shows up and the game starts as usual (but lacking the neat steam features). 1.6 creates a FalloutNV.exe in a folder named "exe" and 1.2 creates a FalloutNV.4gb in the game's folder.
So far so good.
I then rename FalloutNVLauncher.exe to *exe.bak or what ever und name the 1.6's FalloutNV.exe to the Launcher exe, the same happens with 1.2. ---> Error 51
When I replace the Launcher's exe with the fnv4gb.exe itfelf after loading steam says Game is allready running...

What am I doing wrong?

[Mauno]

Originally posted by UberMercury:

When I replace the Launcher's exe with the fnv4gb.exe itfelf after loading steam says Game is allready running...

Check your processes, you probably have a falloutnv.exe already running. This happens to me from time to time, but replacing the launcher with the 4gb exe itself is exactly what I did. Has worked fine for over two years for me now.