edit: blast my spelling!
Modifié par Tikkas, 14 novembre 2009 - 07:20 .
Modifié par Tikkas, 14 novembre 2009 - 07:20 .
Modifié par RaySiilu12, 14 novembre 2009 - 08:03 .
RaySiilu12 wrote...
It just makes your windows read more than 3 GB ram. Its not a true fix for memory leaks. On retail 1.0 ver i have no long loading times and i have 2 GB ram.
But it would be nice to know, if people with 4GB+ ram have memory leaks or not
RaySiilu12 wrote...
It just makes your windows read more than 3 GB ram. Its not a true fix for memory leaks. On retail 1.0 ver i have no long loading times and i have 2 GB ram.
But it would be nice to know, if people with 4GB+ ram have memory leaks or not
Modifié par Tikkas, 14 novembre 2009 - 08:36 .
RaySiilu12 wrote...
It just makes your windows read more than 3 GB ram. Its not a true fix for memory leaks. On retail 1.0 ver i have no long loading times and i have 2 GB ram.
But it would be nice to know, if people with 4GB+ ram have memory leaks or not
RealPoseidon wrote...
You might just explain how to make it aware...
a) make a back up copy of 'Fallout 3.exe'.
put Fallout3.exe in the utility folder
c) double click 'START.BAT'
d) follow the instruction in the command window
e) once made 'large Address aware',
JironGhrad wrote...
a lot of the "memory leaks" are CPU affinity issues check the troublshooting FAQ for the fix here
Modifié par Tikkas, 14 novembre 2009 - 05:30 .
JironGhrad wrote...
hacking the game may have worked for you (and yes, that processor isn't one of the ones on my list) but telling people to hack the game is silly unless you plan on helping every one of them fix their problems when they occur... I link my posts because none of the things we do might break the game and force a reinstall
judgejosh wrote...
hahahaha, destroyed, get of him jironghrad lol. im launching DAO from my steam platform and im having a hard time finding the exe. so im not sure i can do it the way you did? any help?
Modifié par Tikkas, 14 novembre 2009 - 07:13 .
JironGhrad wrote...
a lot of the "memory leaks" are CPU affinity issues check the troublshooting FAQ for the fix here