[AoC]Og der var min account ferdig

[s1gnal]

Til info JohnRichard, så er det 32-bit klienten som har minnelekasje. 64bit klienten har spart deg for litt irritasjon. Har vel egentlig ført til at jeg spiller 1-3 timer pr dag, ettersom det er så lang tid det tar før jeg får grått kart. Det tar jo vinter og vår (3-5 min) å starte klienten på nytt, så det gidder jeg ofte ikke.

 

Hvorfor fikser du ikke bare problemet da? Fiksen har vært ute i en mannsalder nå, og den fjernet både minne-lekasje problemet og det grå kartet for meg.

 

Sant det at han bør bruke midlertidig fix. Uansett er det smålig at ikke en slik bug blir ordnet ved roten av problemet som er i selve spillet. Om ikke de klarer det, så blir det nok et irritasjons moment for mange å måtte lage egne fix for å kunne spille AoC bugfritt. ^^

[blackbrrd]

Til info JohnRichard, så er det 32-bit klienten som har minnelekasje. 64bit klienten har spart deg for litt irritasjon. Har vel egentlig ført til at jeg spiller 1-3 timer pr dag, ettersom det er så lang tid det tar før jeg får grått kart. Det tar jo vinter og vår (3-5 min) å starte klienten på nytt, så det gidder jeg ofte ikke.

 

Hvorfor fikser du ikke bare problemet da? Fiksen har vært ute i en mannsalder nå, og den fjernet både minne-lekasje problemet og det grå kartet for meg.

 

Sant det at han bør bruke midlertidig fix. Uansett er det smålig at ikke en slik bug blir ordnet ved roten av problemet som er i selve spillet. Om ikke de klarer det, så blir det nok et irritasjons moment for mange å måtte lage egne fix for å kunne spille AoC bugfritt. ^^

 

Jeg vet ikke om hva denne fiksen er...

 

Har sett noen nevne Virtual memory size. (Den står på 2048-4096 på PC-en min...)

 

Hadde vært fint hvis du sa hva fiksen er

[Hr. Jenssen]

http://forums-eu.ageofconan.com/showthread.php?t=134

 

Since it's so popular, here's my complete roundup to managing user-mode memory on 32-bit Operating systems with 4GB physical memory:

 

 

Intro: What is this all about ?

 

a 32-bit OS such as Vista or XP has a few limits when it comes to memory use. To sum them up they are:

 

1.The Operating itself can only "see" 4GB minus the amount of reserved memory space by the Bios (because the bios is a layer that stands between the hardware and the operating system itself) The larger the memory on your video card for example, the less memory is left for your OS. This why one person sees only 2.8GB in windows and another sees 3.5GB while they both have 4GB of physical memory installed. Regardless of which edition of an OS you have, ALL 32-bit XP and Vista are subject to this rule.

2. 32-bit XP and Vista are designed in such a way that they need a part of the total addressable (= amount of memory that the OS can "see") for themselves. For this reason, Microsoft designed both XP and Vista in such a way that a certain process could only get up to 2GB of memory, and then the remaining memory would remain available for kernel processes (= itself), even though it does not in fact always need a full 2GB. In fact a clean XP might only need 300MB at some point if only 1 game is running and nothing else installed. Vista will require more kernel memory because it's bigger by design. As more stuff runs, the OS itself might need up to 1.5-2GB of memory for it's kernel. By default the balance in 32-bit XP and Vista is such that it's 2GB for a given user-mode process (= a program = Age of Conan) and 2GB for the kernel (= OS itself) If the virtual size of a process such as Age of conan reaches a total size of 2GB, the program is terminated by the OS BY DESIGN to prevent it from infiltrating the kernel reserved memory space. The user experiences this as a program crash straight into windows. For age of conan, my tests have shown that it's virtual size reaches 2GB at about when the physical memory usage size reaches around 1.5GB (this is what you see in windows task manager). This is why people keep crashing all the time without understanding why. Well, at least until now...

3. 32-bit Processes (=programs) themselves have a built-in little extra mini switch that's called a 'flag' that prevents them from groing bigger than 2GB. Even if you configure the OS using the above to allow up to 3GB for a process, it would not be able to do so if it's built-in switch is set to "not Large Address Aware" because that settings limits the process to a max of 2GB memory. If it's set to "Large Address Aware" however the 32-bit process is allowed to grow up to 3GB on a 32-bit OS or up to 4GB on a 64-bit OS, which is again the maximum for ANY 32-bit process.

 

 

Now there is a switch that makes it possible to shift the balance a bit from 2GB/2GB (program/kernel) to 3GB/1GB. This switch allows us to change the max mem limit for user-mode process so that Age of Conan can continue to grow in virtual size up to 3GB instead of only 2GB and that equals a physical memory usage of at least 2.2GB. The game will crash again when it reaches that new limit. My testing has shown that if you zone enough and roam about, the game wil go beyond 3GB physical usage and 3.5GB virtual size as of now. For this reason you can still crash. However, further testing has shown that the game reaches 1.5 physical usage in the first hour easily when zoning around Tortage (quite easy to simulate) while reaching the 2.2physical usage takes at the very least lots of zoning and usually a few hours to reach. For this reason the following switch (ONLY IF YOU HAVE 4GB MEM) may solve alot of problems for you

 

 

Great news! So how do I set the switch ??

 

Under Vista 32-bit:

1. Under Vista 32-bit (with at least 4GB memory installed regardless how much you see of it in windows) go START

2. Navigate to programs...etc until you see a black icon named "command prompt"

3. rightclick it and select: run as administrator. A big black box appears

4. In the big black box, type the following command: BCDEDIT /Set IncreaseUserVa 3072

5. Press enter to execute the command

6. reboot your computer

 

7(optional). If you don't like it for some reason you can revert the switch the same procedure but replace step 4 with this: entering bcdedit /deletevalue increaseuserva (this undoes the switch)

 

Under XP 32-bit:

 

the equivalent of that switch on Vista for xp is simply by modifying the boot.ini file (it's a hidden system file under c:\) and add the /3GB switch to the line that looks like this:

 

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Pro"

 

so it becomes:

 

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Pro" /3GB

 

then reboot to activate the change

 

to remove the switch under XP: remove the /3GB and reboot

 

 

 

Is there a catch ? Any danger to this switch ?

 

Yes, there is. You limit the available memory to the OS itself. If the OS tries to use more, windows will crash and you will have to reboot and start your programs up again. Is this most likely to happen ? Nope, generally it's not. But it can whenever the OS requires alot of memory, more than is available. Let's say someone has 4GB installed, but he uses 2*8800GTX (the type with 768MB per card) so his OS only "sees" 2.8GB. On top of that his computer is not cleanly/newly formatted. It's filled with tons of previously installed programs, antivirus and whatever else that uses memory. Then on top of that he's playing AOC with the switch so it's using over 2GB of memory...you can see where this is going and you know how to avoid it...

 

Vet ikke om det var denne du mente, men den funket fint for meg, i alle fall.

[blackbrrd]

Jeg har 2gb ram, så den guiden der hjelper lite. Den er for folk med 4gb ram.