Test Server Crashing?

[Arielle Nightshade]

<p>I keep getting the 'eq2client has stopped working' windows notice, and then crash when trying to log on to the Test server. (hope this is the right forum for this).</p><p>This is happening right after I get the 'logging in as..' notice (ie, I'm almost in game, then it crashes)</p><p>The last time it did this, it was that patch.vpk problem, but that file isn't there anymore.  Can anyone help?</p>

[TSR-DanielH]

<p>Greetings,</p><p>Are you using a custom user interface?  If so, that is probably the issue.  Apparently the current patch has problems with some custom UI's.  That is a known issue and is being discussed in the following thread:</p><p><a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=457841" target="_blank" rel="nofollow">http://forums.station.sony.com/eq2/...topic_id=457841</a></p>

[Barx]

<p>Just to add on...</p><p>A general rule of thumb is any time a major update (eg a GU) hits the Test server you're better off going to the default if *any* UI or crashing issues occur.</p>

[Arielle Nightshade]

<p>Yep, I am indeed.  I'll get rid of it for the time being - thanks Daniel and Barx, as always <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /></p>

[Possessive]

<p>I'm using profitui.  How would I disable that for the test server, but not touch it for the regular server.  Is that possible?</p>

[Wingrider01]

<p><cite>roy33pdx wrote:</cite></p><blockquote><p>I'm using profitui.  How would I disable that for the test server, but not touch it for the regular server.  Is that possible?</p></blockquote><p>look for the directory under the eq2 with the label Test Server, this is a duplicate of the game. Remove the eq2.ini there, but first try going into  the profit UI directory under the test server and delete theses two files</p><p>eq2ui_journals_active and eq2ui_journals_quest</p><p>See if that fixes it</p>

[TSR-KenC]

<p>Before I let this thread delve on to the abyss, is anyone else having this sort of trouble currently? Or has the current test server build remedied the issue for you folks?</p>