PDA

View Full Version : Continued Crashing - DX Error


myska
05-13-2008, 12:55 PM
<p>I've posted on this issue before. Many many many many others have also posted on this issue.</p><p>The game randomly crashes in anywhere from 10 minutes to an hour of playtime with a DX_OutOfMemory error. Most often this happens, and happens quickly, when inside a dungeon instance, Neriak, or Gorowyn.</p><p>This is still an issue and it truly makes the game, not only incredibly UNenjoyable and frustrating, but also unplayable.</p><p>Yet another game update is in and after *years* the only information we've heard on this is that SOE is attempting to make contact with Nvidia about it.</p><p>While I hate making threats, at this point I am wasting my money by continuing to pay a subscription for a game I can't play and enjoy because the developers are unwilling to do what's actually needed to remedy this bug. I won't continue to do so for very much longer.</p><p>Since Everquest2 is the *only* up and running MMORPG with his issue, perhaps the developers should stop trying to lay the blame on Nvidia and start trying to figure out what they coded wrong. There's a plethora of other MMO examples to learn from.</p>

TSR-TrevorG
05-13-2008, 02:41 PM
Hey Myskaal,  I am sorry you are having these issues. In my years of playing, I have not encountered this error.  I am not saying it doesn't exist, just that I have been "lucky" enough not to get it.  It would seem though that the developers are working on issues like this exact issue, as the GU#44 indeed have a fix for this, and will constantly be tuning the client.<a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=414136" target="_blank" rel="nofollow">http://forums.station.sony.com/eq2/...topic_id=414136</a><span class="postbody"><ul><li>The client will automatically enable a low-memory mode when you are running low on memory. The low-memory mode will downsample far away textures and unload geometry that hasn’t been drawn in a while. The low-memory mode should generally be invisible. </li><li>Performance settings were adjusted slightly for better rendering at lower qualities without significantly impacting performance. <ul><li>Flora will now only be rendered on High Quality settings and above. </li><li>Objects will not disappear as quickly on lower settings </li></ul></li><li>The client is Large Address Aware, meaning that you are much less likely to run out of memory if you have 3GB or more of RAM and are running either the 64-bit versions of Windows or have modified your boot.ini to support 3GB user address space. </li><li>Color Profile changes: <ul><li>If you have a desktop color profile configured (or your gamma ramp changed), the client is better about restoring your settings when it exits. </li><li>The client no longer overwrites your color profile settings with its own. Instead, the gamma values in the Options -> Display -> Color Correction modify the desktop color profile settings. This means that if all of the client's Color Correction settings are left at defaults (brightness at 0.0, contrast at 1.0, gamma values at 1.0) the client will use your desktop color profile settings. </li><li>Crashes should be better about restoring your color profile.</li></ul></li></ul>Leave us any information you can. PC spec wise, so we can look into this for you.</span>

myska
05-14-2008, 09:11 AM
<p>My specs and DXDiag etc can be found in this thread:</p><p> <a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=415546" rel="nofollow" target="_blank">http://forums.station.sony.com/eq2/...topic_id=415546</a></p><p>Game Update $$ has made the problem worse for me and the *only* performance setting I can now play on for a length of time is Extreme. This - with the computer I have - is unacceptable.</p><p>I'm glad you are one of the lucky ones. Maybe you could post your own spec so the rest of us know exactly what it is that works instead of trying fruitlessly to meet whatever the unknown requirement to actually play and enjoy the game is.</p>

TSR-DanielH
05-14-2008, 03:13 PM
This problem sounds like it could be caused by a bad memory sector on the graphics card.  Do you possibly have a different graphics card you can swap out to test for the same error?  I realize not everyone has spare graphics cards laying around, but it would be good to check if you do.While Direct X errors are a common technical issue, I can't recall a contact I've handled where they were experiencing that specific error.