Spell icon tint is updating too slowly

[Leucippus]

<p>I recently updated my computer and the tint on my spell icons is taking too long to refresh.</p><p>I can cast the spells normally, but the spell icons are still tinted when I start casting.</p><p>Any suggestions? I suspect this situation results from the multicore CPU support.</p><p>-Leucippus</p>

[TSR-DanielH]

<p>The problem you're describing is usually caused by a system clock that is out of sync.  You might want to check the system clock in your BIOS to make sure that it is set correctly.  Have someone help you if you are uncomfortable modifying the BIOS.</p><p>Since the game uses the system clock to display things like timers, a problem with that clock will cause this type of issue.</p>

[Leucippus]

<p>The time of day clock seemed to be setup ok. This computer's time was a few minutes slow though I updateded it.</p><p>The situation is more interesting...</p><p>The refreshing of the spell icon's tint will fix itself, then update too slowly again.</p><p>Crafting is a good way to check if this situation is occuring.</p><p>Another player in my guild notices the same icon tint behavior.</p><p>And, get ready for this...</p><p>I found away to make it go away, fix itself!</p><p>Ready: switching to full screen mode from windowed mode makes the situation go away!</p><p>It would be most interesting to learn how, and why, the game's timing varies depending on if the game is being played full screen or windowed.</p><p>Things get even stranger. If the timing gets far enough off, the sound starts to get lagged, really bad, and then CRASH, Vista 64 locks up!  The computer has to be reset with the reset button. It does not respond to network requests either. How an application can hang a quad core CPU is beyond me. So much for Vista. If someone reading this post is having trouble with system crashes, try switching to full screen mode and see if those crashes go away.</p><p>Oh yeah, the multi-core CPU support option does not seem to have any effect on this icon tint situation.</p><p>End of my rambling for now.</p><p>-Leucippus</p>

[TSR-DanielH]

<p>Greetings,</p><p>What processor are you using on that computer?  Some of the older AMD dual core CPUs can have trouble with the game, processing certain things slower or faster than others.  That could be the problem in this case and AMD has actually released a 'dual core optomizer' that will usually correct it.</p>

[Leucippus]

<p>I am running one of AMD's new Phenom II quad core processors.</p><p>I found that fix you refer to before I posted. That fix does not apply to the processor I am using.</p><p>I find it very odd that the invalid icon tint behavior only occurs when EQ2 is running in windowed mode, as opposed to full screen mode, very strange.</p><p>-Leucippus</p>

[TSR-DanielH]

<p><cite>Leucippus wrote:</cite></p><blockquote><p>I am running one of AMD's new Phenom II quad core processors.</p><p>I found that fix you refer to before I posted. That fix does not apply to the processor I am using.</p><p>I find it very odd that the invalid icon tint behavior only occurs when EQ2 is running in windowed mode, as opposed to full screen mode, very strange.</p><p>-Leucippus</p></blockquote><p>Try setting the game to use only a single core temporarily and see if that corrects the problem.  You can do so by starting the game, opening the task manager, and selecting the processes tab.  You'll then want to choose EQ2 from the list, right click, and select 'Set Affinity'.  Make it so that only one of the boxes is checked on that screen.  That will let us know whether the dual core is causing this issue.</p>

[Leucippus]

<p>No simple answer to your request is seems.</p><p>The short answer would be setting "EverQuest2.exe *32" to run on CPU 0 only had no effect on this problem.</p><p>But, the answer is not that simple.</p><p>It seems I am unable to use task manage to set the affinity to CPU 0 only. The game will reset the affinty to use all four CPU cores even if I set the game to use CPU 0 only using task manager.</p><p>So, it seems I am unable to perform the test you requested after all.</p><p>Also, this test can only be performed in windowed mode. In full screen mode, one can not access task manager.</p><p>I did notice something else. Switching from full screen mode to window mode (while crafting) recreated the problem. Switching back to full screen mode did not correct the problem, until after I camped to myself.</p><p>-Leucippus</p>

[TSR-DanielH]

<p>Where do you have the game installed on your computer?  If you have it installed to the Program Files directory then that might explain why the processor affinity is not saving correctly.  Vista tends to put greater protection on those programs and will reject changes like the one I suggested. </p><p>You should still be able to perform that operation if you move the Everquest 2 directory somewhere else like C:Games.  Simply cutting and pasting the folder will work since the game doesn't need any registry keys.  Just keep in mind that you'll have to create a new desktop shortcut if you like using one.</p>

[Leucippus]

<p>The game is installed in C:EQ2, I give it its own subdirectory off the root.</p><p>I used your copy file trick to install the game from my old computer. Although, I may have just copied the *.paks and the initial executable. All one needs is the initial executable it seems. If you run that one application, it will install the entire game, very nice. Copying the *.paks first (in the proper subdirectory) saves a lot of install time though.</p><p>Also, the affinity setting stuck while I was on the character select screen. After I logged my character in, I noticed the affinity has changed back to all four CPU cores.</p><p>-Leucippus</p>

[Leucippus]

<p>The mystery deepens</p><p>I had the problem start to occur in full screen mode while crafting in my guild hall today. (The time the icons take to refresh slowly lengths, sometimes)</p><p>So, I exited the game and let the computer sit idle for a while.</p><p>The computer was locked up when I returned! It seems the lockup crash will still occur, even after EQ2 is closed. I could not check if EQ2 had actually closed, or if the process was still running with no windows.</p><p>I am beginning to think this behavior is related to the random crashes others are experiencing.</p><p>-Leucippus</p>

[TSR-DanielH]

<p><cite>Leucippus wrote:</cite></p><blockquote><p>I am beginning to think this behavior is related to the random crashes others are experiencing.</p><p>-Leucippus</p></blockquote><p>That might be the case with the crash, but I still think that the problem with the spell icons is being caused by the AMD multicore.  To correct that I would advise creating a restore point and using the AMD dual core optomizer.  Bad timers are are almost always caused by a bad system clock or errors with consistent processing speed.  The optomizer locks the CPU to the time stamps and should correct the problem.</p>

[Leucippus]

<p>I am running an AMD Phenom II quad core processor.</p><p>The link to the AMD drivers for that processor is:</p><p><a href="http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_15259,00.html" target="_blank" rel="nofollow">http://www.amd.com/us-en/Processors...1_15259,00.html</a></p><p>Notice the dual core optimizer is not listed for the processor I am using.</p><p>Also, if you check the AMD forums, some else tried installing the dual core optimizer on a system similar to mine. It installed, then promptly crashed their system, forcing a rebuild if I remember correctly.</p><p>The link to the programing you are refering to can be found on the drivers page for the Athlon X2 processor, here:</p><p><a href="http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html" target="_blank" rel="nofollow">http://www.amd.com/us-en/Processors...1_13118,00.html</a></p><p>I remembered reading on about the dual core optimizer and though for sure that program would solve the problem. I was confused when I could not find that program on AMD's website, until I realized it is apparently not supported, or not needed perhaps, on the Phenom II processors.</p><p>-Leucippus</p>

[TSR-DanielH]

<p>While I have used that tool to correct similar issues for customers with AMD chips, I agree that we should avoid using it if your processor isn't on the list.</p><p>I still think it's a timing issue related to AMD, but we'll have to try something else.  Do you feel confident enough to flash your BIOS and upgrade your chipset drivers?  Doing so could resolve this issue but there is a significant risk to your computer if you flash the BIOS incorrectly.  If you're sure you can do it then I would suggest trying, if not then you might want to have a friend/professional assist you.</p>