WoW 'Large Address Aware' Patch

[Cypher]

v4.0.3.13329
http://dl.dropbox.com/u/74751/Wow_13...ess_NoSign.zip

Large address support enabled, code signing disabled.

[Dariss]

Last file uploaded is wrong version of Wow.exe. Version uploaded is 13205, not 13329.

[Cypher]

Fixed, thanks. I actually uploaded the correct file, but I copied the wrong link from Dropbox. >.<

[wetwlly]

quick question Cypher, is it possible for wow under 64-bit to use more than 4gigs of ram with this patch? or did you just set it to use 4gbs, if so, how can it be utilized to use more than 4gigs and would it be too much to use more than 4gigs haha.

[_Mike]

quick question Cypher, is it possible for wow under 64-bit to use more than 4gigs of ram with this patch? or did you just set it to use 4gbs, if so, how can it be utilized to use more than 4gigs and would it be too much to use more than 4gigs haha.

That's impossible. A 32-bit application cannot address more than 2^32 bits (4 GB) of data.

[wetwlly]

edit: sorry I read wrong. I understand what you mean thank you.

edit(2): off-topic, think blizzard will ever make it a 64bit app? haha.

[Cypher]

I doubt it. There's no compelling reason for them to just yet. WoW doesn't use enough memory to justify it, and they'd have to port Warden to x64 too.

[malu05]

Interesting. It actually works pretty well with the client you have provided.
Extending the loaded ADT grid from 8x8 to 9x9 and 10x10 along with the view distance works well and doesn't cause the client to crash.
However extending the detail doodad range did cause the client to crash, i guess they use diffrent methods to allocate, or maybe the texture budget just goes beyond what the client can handle (doubt that).
So i guess in that regard there are no "pratical" use for it just yet (does look quite weird with that hard line where the detail objects are being rendered coming over to clean terrain), but interesting non the less.

Thanks for sharing.

[Scorpiona]

Replying to a post talking about the rules... with an image macro that's against the rules. Cool!

[andy012345]

Bump.

This might be a good thread for a sticky. Blizzard tech support posted today that if a scan for large address aware was ever done, no action will be taken on accounts that the scan gives results on.

They also recommend reverting the change during a patch as it can mess the patcher up.

Source: OK to use Large Address Aware Flag with WOW? - Forums - World of Warcraft

[DarkLinux]

WoW, so Blizz is kool with this? Nice to know really. Dident think they would like it lols.

[Cypher]

Bump.

This might be a good thread for a sticky. Blizzard tech support posted today that if a scan for large address aware was ever done, no action will be taken on accounts that the scan gives results on.

They also recommend reverting the change during a patch as it can mess the patcher up.

Source: OK to use Large Address Aware Flag with WOW? - Forums - World of Warcraft

Thanks for the link.

[natt_]

WoW, so Blizz is kool with this? Nice to know really. Dident think they would like it lols.

Why should they take an action into it?.... Its like when Multi-boxing came and everyone cried "ooh lol blizzard thought it was okay :S".

[Mc-fly]

with this my WoW Supports the 6GB of ram? did I understand it right?

[wetwlly]

Alright! so I finally got 16gigs of ram, don't ask me why so much. and tested this patch out.

So far, maybe a slight change on everything loading faster i guess in-game, but it seems to still take my comp a bit to register org and then every npc pops up. maybe its my connection, but its still a nice improvement thanks Cypher!