It's a single source that has 100 percent of New Vegas customers though :disguise:

Your point is? XP has been and is going to continue to lose marketshare outside of the business environment. You can't lump gamers in with typical home users that use their computer for nothing other than web browsing and the occasional word document.



Thats a very good point.

Use http://www.ntcore.com/4gb_patch.php. I never understood why everyone (in Oblivion and FO3 communities) insisted on using highly specific LAA enablers that only work for the specific games when there are plenty out there on the web that work universally. The patcher I linked automatically makes a backup .exe as well as works with every .exe out of box.

Since NV is the first Steam game I've had that I'll eventually need to eventually use it on I'm not 100% how it will work with the overlay if there is some quirkiness or it works fine or what, so keep that in mind. (Maybe that's why the previous patchers were so specific? I never looked into them to much.)

Doesn't work on the encrypted executable.

Made me chuckle.

Chuckle more by reading deeper into that survey. Over 50% of users of steam rely on 32bit operating systems. Dismissing gamers who don't use a 64 bit system is trite, to say the least. Gamers like you and me may use 64 bit systems but most still rely on 32 bit and are the larger share of the market.

Forcing the user to use 4GB would alienate the 32bit market. Allowing people to use it doesn't.

Just because you flag it for http://en.wikipedia.org/wiki/Physical_Address_Extension doesn't touch 64-bit.

Any modern gaming machine capable of playing NV without a slideshow is going to support PAE.

So they should now include an insert teaching people how to boot their system so PAE is enabled? I don't even trust some of my friends, who are hardcoe gamers, to set their computer up properly without my help and now you want them to fiddle with the startup?

I was chuckling at the fact that you "Don't rely on a single source" despite that source having 100% of the market share of Fallout New Vegas customers. I've got a survey here from Mums.net, do you think that might be more relevant?




Yeah because if they included a large address aware executable for 64 bit customers then all the 32 bit customers would explode.

Back in the day.

Vista/7 (and XP post SP2 AFAIK) automatically enable it if the hardware is present.

" This very little tool patches x86 executables in order to let them have 4GB (instead of only 2) of virtual memory on x64 platforms"

Already don't trust it. LAA only enables the use of 3GB for 32-bit applications, not 4.


And more information about why there is no 64-bit version. Both 64 and 32 bit applications not linked with LAA can only use 2GB, so we would still need to make the game LAA regardless of if there were a 64-bit version.

I still dual boot XP 32 bit due to compatibility issues with older games I still play. It doesn't automatically enable it. As far as Vista and Win 7 32 bit, what I have read so far suggests the user must enable it in startup options.

http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx

In 32 bit systems, a 32 bit program can only access up to 3GB if IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT. However under 64 bit windows, 4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set.

Ah, missed that memo XD

Well personally I dont want it to do that as I only have 4GB. Would there be a way to manually set it to 3? I would prefer having that 1GB purly for OS use and other background processed.

You can still use it and it will only use 3GB

http://msdn.microsoft.com/en-us/library/bb613473%28v=VS.85%29.aspx

Immaterial. I agree most 32 bit users probably have 2 gig. Bu the game should recognize and use any additional RAM over and above that amount.

I use 32 bit and have 4 gigs of ram...

So is there any way to get this to work with more ram usage?

2.75GB, or 3GB if you've added the /3 option to your windows .ini. Only server editions of 32-bit windows are able to use more than that.

NVSE cannot help with this; the flag is read when the executable is loaded, which is before we are involved in the boot process. The file on disk must have the large-address-aware flag set to access the full 32-bit address space, once DLLs (aka us) get around to loading it's way too late.

I think what people meant is that you guys are the most likely to get an unencrypted exe off of Valve/Bethesda/Obsidian or whoever which would open the door for this fix.

You realize that even if the memory is set to go to 4GB or whatever, that doesn't mean that the game will USE 4GB. It will detect the extra memory and if it NEEDS it, it will use it, but until it actually needs the extra memory, it's not going to use it. On top of that, your kernel can take memory away from any process at any time it wishes, so you are not guaranteed to be able to use the entire 4 GB of ram for the game and if you have exactly 4 GB of ram, I can tell you with complete certainty you will never devote 4 GB of ram entirely to one process.

Out of curiosity however, how much RAM does this program actually use for you? I've only ever seen it use 800 MB tops of my 4 GB.

Exactly. :nod:

Ironically it works fine with other Steam games.