Age of Conan

This is getting old, i crash at least once a day.Can someone explain to me why this is so hard for them to fix, Its a old problem now and there adding content but no fixes for problems they have had since beta???

OOM error is do to bad coding. They recycled code from ao.

Depending on your amount of RAM (and OS), did you try throwing the 3GB switch? It pretty much eliminated out of memory-related crashes on my part.

Yes, it's a work-around, not a fix, but at least you can play the game for an entire evening uninterrupted.

Windows 32 bits have a hard limit of 2GB by process, even If you have more ram, as soon Conan need more than these 2 GB, the game crash.

Originally posted by Teiman

Windows 32 bits have a hard limit of 2GB by process

 

... Unless you input the 3GB switch, which increases the max value of memory allocated to a single process to allow use of 3 gigs.

how do you input a 3gb switch?

For Vista, open a command prompt (cmd) as an administrator and type the following: BCDEDIT /Set IncreaseUserVa 3072
Then reboot. And voila.
 
For XP (not sure if it's doable with XP home), open the boot.ini file (and make a backup of it just in case).
Find the line that looks something like this (might vary slightly depending on your system):

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro"

Change it so that it looks like this:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro"
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro with /3GB" /3GB

Save changes and reboot.

I'm not liable if you fuck up at any point during this procedure and something implodes. :)

understood. seems too easy.

what can go wrong? or, are there any other negative impacts that can result from successfully applying this 'switch'?

It's never gone wrong when I did it, and I imagine for Vista the chances of anything going wrong must be absolutely minimal - it's essentially a command, and if you input it wrong, it simply won't change anything.

Fiddling with system files has a certain risk to it, however, and I won't make any claim to know what each and every parameter in a boot.ini file does. But if you do stick to only altering what was specified above and nothing else, I can't see anything going wrong at all. This is a switch that Microsoft themselves hand out documentation for, even if they recommend only "advanced" users take advantage of the option.

The function of the 3G switch is giving the userland applications 3 gigs of addressable memory at max, instead of the regular 2Ggigs for kernel + 2 gigs for userland approach. With 32 bit address space 4 gigs is the brick wall you cannot bypass without ugly hacks. There is technology called PAE which can surpass the 4 gig barrier using bigger granularity for addressing, but in general it's mostly a stopgap measure and using 64 bits once you need more than 4 gigs of total memory is recommended.

The drawback when giving only 1 gigs of memory to kernel is simply that much of the I/O that is done is memory mapped - for example if you have a vid card with let's say 512 megs of memory, that memory has to be mapped somewhere in the processor addressable space and the other IO devices need some RAM as well. In practise that means that you might restrict kernel having all the memory available that it could use in ideal circumstances and that is one of the reasons most of the OSes restrict the userland memory by default. I reckon that running certain card combinations in SLI could actually get hit when using 3G switch.

Core issue, which is memory bleeding away should IMHO in this case be solved by Funcom - There are several tools available, some even free(ish), that check the sourcecode and warn about the places where program does not return allocated memory back to OS after those aren't needed. The solution shouldn't be the end user adding address space or virtual memory ad nauseam.