[EDIT=Original first post]
Hello everyone,
I just downloaded the latest patch and was majorly annoyed when I found out that they didn't fix the nvidia graphics driver crash. As I hope to, eventually, at some point, actually play this game (10-30 minutes doesn't count as "playing"), I will have to try and find a solution...
I already read all the posts I found on this forum and on the web about cleaning the registry and drivers and reinstalling everything but so far none of their solutions (except complete reinstall which I'd hope to avoid) seem to fix anything...
So here goes fact gathering to hopefully find a pattern...
First up, my setup:
- Windows 2008 64bit (read: Vista64 with a different set of configurations)
- NVIDIA 8800GTS 320MB (Gainward GS), latest drivers. <-- Suspected culprit, the low RAM in particular.
- Gigabyte Mainboard with ATi 790FX+SB600, latest drivers.
- AMD 9850BE, stock clock.
- 8GB G.Skill ram, down-clocked to 800MHz.
- 4 WD Raptors at 74GB each, working as Raid0, used as boot-device, containing all of windows and my games-folder.
- all disks freshly de-fragmented.
Game Setup:
- 1920x1200 resolution
- "High" preset
- Bloom enabled
- Shadows reduced to low because anything higher seems to kill my VGA's very limited RAM.
- Most of the sliders somewhere in the (lower)middle to get me my targeted 25-30fps
- That RAM-offloading-for-laptops enabled, even though I don't have a laptop... could this cause such a thing without shared memory?
Here are some facts I gathered so far:
- The driver actually fails (windows reports it as such) and recovers... but not completely, leaving the driver in an incredibly fragile state. after that it will crash again every 5-60 seconds and will keep doing so until I reboot.
- I never had any driver failure in any other game or application, and I try a lot of different engines.
- The game likes to crash the driver...
* after zoning... probably caused by lots of content-loading paired with (potentially) failing depth/range-checks due to incomplete content.
* in large zones where you can see very far, often while turning around to see even more (when the game has to load the content that wasn't visible before)
* while moving quickly through an area that is very open (far view again, paired with content loading)
- The new
NVIDIA beta drivers (
177.92 http://www.nvidia.com/object/winvist...7.92_beta.html ) do NOT fix the problem, but reduce the frequency of crashes (down from 5-10 minutes to about 15-20 minutes, or it might just be me)
- The (outdated)
d3dx10_36.dll in the AoC folder seems to add to the problem, deleting it helps a bit. Although you will have to skip the updater to start AoC because the updater would just download it all over again...
-> more facts about that dll:
* the 36 version of that dll in my system folder was last modified "02 October,
2007-10-02, 09:56:30"... making that baby almost
one year old... a year in which no one thought an update would be in order... the
latest version is 37 and dated 2008-02-05.
* the dll in the AoC folder
does not match the dll in my system32 folder, it even has a different size.
- The console output (which you get by avoiding the updater and starting AgeOfConan.exe) keeps spaming several things... for one, there's tons of meshes that fail to map to skeletons... and it increasingly spams those things shortly before a crash:
[14:03:50 #172729] ERROR Cheetah - Error linking bone array: mesh 325715, skeleton 18251 - bones do not match
If anyone else has similar symptoms, please post your setup and findings in order to help (me or FC) identify the cause and hopefully fix it...
I'm going mental rebooting every 20-30minutes...
regards.
[/EDIT]
I just started a little experiment...
I deleted the d3dx10_36.dll from the AoC folder and replaced it with the d3dx10_37.dll (note the version difference) from my Windows/system32 folder. (I obviously had to rename the d3dx10_37.dll to d3dx10_36.dll)
Even though the game had crashed the drivers earlier I have now been dashing around Conall's Valley, trying to force a driver failure, for almost 10 minutes... and it's perfectly stable. The log still spams error messages about failing to map bones to meshes... but nothing crashes...
Will investigate further.
Note: The game used to crash the graphics drivers after a failure within seconds, over and over again. this is not the case now and I will not reboot until I forced another failure...