Large Address Aware

[FordGT90Concept]

Was that what Process Monitor caught? The Sims 3 crashes between 1.6 and 1.7 GiB. Maybe it has to do with how much memory is allocated to the video card. I see you have a 1 GiB card and since you are increasing the texture sizes, it is possible that the game could be reserving 800 MiB to the video card while TS3 reserves around 300 MiB. VRAM is really the only possible explaination why it isn't always 1.99999 GiB before it crashes.

[Mussels]

yeah it was process monitor.

i too think it may be video card related, my guess was the .ini tweak raised it far above the normal limits (and the reason for the poor textures at high res was probably a developer idea to lower the memory usage - singularity did the same thing recently, and it was another unreal engine game)

[FordGT90Concept]

I remember seeing weird texture stuff in Singularity. It seems like I remember looking at a surface up close and thought, "that looks like crap." I'm usually not one to notice those sort of things either. I wonder if there is a way to detect how much VRAM an application has tied up. I think it is pretty specific to the game though so nothing I could add to Process Monitor.

[Mussels]

Originally Posted by FordGT90Concept

I remember seeing weird texture stuff in Singularity. It seems like I remember looking at a surface up close and thought, "that looks like crap." I'm usually not one to notice those sort of things either. I wonder if there is a way to detect how much VRAM an application has tied up. I think it is pretty specific to the game though so nothing I could add to Process Monitor.

it may be related, since its the same engine (well, very similar unreal engine)


basically, as you turned the res up, the game would lower textures to prevent memory usage going over a certain limit.


In singularity, that resolution limit was 1280x720, thanks to the consoles. you could disable the limit crash free even at 1080p, so it wasnt neccesary at all on PC, just a leftover bug.

[Johnny_Utah]

First, I would like to thank you for this program. I was referred here by player-x who had a similar problem in WOW with the storage problem. My question is simple and I think Mussels explained it, but how I am a bit worried, as Blizzard indicated that we should back up the original program as updates might have problems after running this wonderful LAA program.

How exactly should I go about doing this? I have my wow folder, there is a Launcher.exe. and then the actual program wow.exe. Should I simply make a copy of wow.exe then rename one to OLD?
Then run the LAA program and link to the NON old wow.exe? I just dont want to make things hard on myself.

Thank you!

[Mussels]

Originally Posted by Johnny_Utah

First, I would like to thank you for this program. I was referred here by player-x who had a similar problem in WOW with the storage problem. My question is simple and I think Mussels explained it, but how I am a bit worried, as Blizzard indicated that we should back up the original program as updates might have problems after running this wonderful LAA program.

How exactly should I go about doing this? I have my wow folder, there is a Launcher.exe. and then the actual program wow.exe. Should I simply make a copy of wow.exe then rename one to OLD?
Then run the LAA program and link to the NON old wow.exe? I just dont want to make things hard on myself.

Thank you!

yes. thats exactly how you should do it.

if you have a patch fail or something, simply replace the exe with the non modded one.


In my case i've had no problems with games patching the modified files, i've just had to re-do the LAA mod again afterwards.

[FordGT90Concept]

Because the application only modifies one bit (a true/false value) it always finds the same way, backups really aren't necessary. If the program doesn't run as expected with LAA enabled, simply run the program again, select the same executable, and disable it by clearing the checkbox or setting LAA to false (depends on the current "mode" being used).

[Mussels]

resurrecting this thread since its useful for skyrim.

[Delta6326]

Awesome DUDE! Using this for Skyrim!

[Easo]

Thanks, remembered about this for Skyrim.
P.S.

You can remove WoW from that list, it uses LAA from patch 4.1 (it was deployed in the end of April ).

[Mussels]

holy crap...


i guess spamming links to this thread on various game forums really did help.

[Cold Storm]

Originally Posted by Mussels

holy crap...


i guess spamming links to this thread on various game forums really did help.

http://img.techpowerup.org/111118/Capture014201.jpg

And with that.. we should sticky the thread..

Who else thinks so?

[Easo]

Yes, sticky it please, probably i am not the only one who has to google it after doing Shift+Del. xD

[UchihaItachimk]

sorry for this stupid question i dont understand /noexecute=optin /fastdetect /3GB this is how is supposed to be for 32b with 3gb

[FordGT90Concept]

There's a limit in 32-bit Windows that forbids a single application from using more than 2 GiB of RAM. The /3GB switch bumps the limit up to 3 GiB. /userva can further customize the amount in megabibytes.

[UchihaItachimk]

Originally Posted by FordGT90Concept

There's a limit in 32-bit Windows that forbids a single application from using more than 2 GiB of RAM. The /3GB switch bumps the limit up to 3 GiB. /userva can furth customize the amount in megabibytes.

how much you recomend with /userva and how to do that with command prompt ?

[Mussels]

Originally Posted by UchihaItachimk

how much you recomend with /userva and how to do that with command prompt ?

just go with 3GB. you still have a 4GB maximum, and some must be left for windows/other programs.


the only true solution is to move to a 64 bit OS.

[UchihaItachimk]

just got blue screen of death on skyrim first time when i did this

[FordGT90Concept]

Skyrim on I think it was 1.2 patch has compatibility issues with large address aware. It might work again in the next patch assuming they didn't patch it to be large address aware anyway.

[Mussels]

Originally Posted by FordGT90Concept

Skyrim on I think it was 1.2 patch has compatibility issues with large address aware. It might work again in the next patch assuming they didn't patch it to be large address aware anyway.

there is a third party 'skyrim 4GB fix' that works as a loader/launcher to add in LAA, and you need a seperate fix for crossfire as well (possible for SLI as well, unsure)

[FordGT90Concept]

They use different executables?

[1Kurgan1]

Yep, but it also screws any driver enhancements that have been made for the game.

[FordGT90Concept]

Wow, Skyrim is apparently full of fail with large address aware compatbility.

[Mussels]

Originally Posted by FordGT90Concept

Wow, Skyrim is apparently full of fail with large address aware compatbility.

the fix is a .dll that makes the launcher use skyrims crossfire profile, the idea is to bypass steams messing with the .exe

[Black Panther]

I've read that to make Skyrim LAA aware and also have the driver enhancements you should download the 4GB mod which gets installed in a separate folder not in your Steam folder. Then create a shortcut to Skyrim4GB.exe. In the shortcut, change the path to:

"C:\[your path here]\skyrim4gb.exe" -laaexe .\TESV.exe

Many at the official forums are saying they're getting great fps with AMD crossfire using this little trick (because it changes the process from skyrim4gb.exe to tesV.exe and so the AMD graphic driver recognizes it).

I tried it but I get stuttering, sound looping and crash to desktop, exactly as if I weren't using the 4GB fix at all. Probably just me doing something wrong... or just my luck...