CPU overclocking >>> Timers Off

[Rutelor]

At some point, after one of the 1.17 updates, I started noticing that most of my action and leve timers, were off by a solid amount of seconds, sometimes minutes (in the case of long cool-down periods, or leves.) The first time I noticed, I was frantically trying to finish a leve in the amount my timer stated (seconds left,) when one of my party members said, in relief, that it seemed apparent we had plenty of time to finish the leve. Apparently my timer had eaten, or misplaced, about 3.5 minutes of the leve's allocated time. When it hit 0, it just flashed the red figures for minutes.

Then I started noticing the actual cool-down of my spells, when playing THM or CON, would end up being a few seconds longer than the timer seemed to imply. After the timer reached zero, the action continued to appear grayed-out for long seconds at a time.

I double checked with all of my LS mates and in-game friends, and nobody seemed to be experiencing the same issue. Then it occurred to me to reset my MoBo's overclocking to zero, and the problem disappeared.

Has anybody else in this forum experienced this? Does it make sense that the game timers would depend on the raw pulses (rather than the translations of the same as time measurement that the Bios or the OS can provide?) Be mindful that I'm not referring to GPU over-clocking here.

Thanks in advance for your thoughts, or ideas on ways for me to recover my overclocking advantage without losing my timers.

[origamikitsune]

This is very interesting, however it would not surprise me. SE has been shunting a lot of the server side functions to the client side, and it would not surprise me if non-essentials are entirely client side. For example, while the calculation to determine how much time is left on a timer is set server side, the display is sent client side. Just a guess. This of course means that faulty programming can lead to incorrect displays.

Also, SE has a history of not knowing how to handle overclocking. There was, for a very long time, an issue in 11 where players were getting flee-like ability for no apparent reason. SE's official response was to disable adaptive overclocking. AMD had introduced a new system that allowed their procs to overclock on the fly, so the game would launch, then the proc would speed up later and cause your character flee - which according to SE was a violation of the terms of service for using 3rd party enhancements. -.-

So yeah.

[Rydin]

wasn't there just a maint. fix for an incorrect cooldown timer?

[AuctionGirl]

this is due to memory leaks... after a few days I notice the same thing on my computer, a simple logout and log back in seems to fix this.. so if you have been logged in for days and going to a dungeon, do a quick logout and login.

[Coldfire]

This has nothing to do with overclocking. It's a known issue and it's most likely caused by client/servers async data. The exact problem is hard to determine though as it happens too rarely.

[Rutelor]

this is due to memory leaks... after a few days I notice the same thing on my computer, a simple logout and log back in seems to fix this.. so if you have been logged in for days and going to a dungeon, do a quick logout and login.

This has nothing to do with overclocking. It's a known issue and it's most likely caused by client/servers async data. The exact problem is hard to determine though as it happens too rarely.

Much as I appreciate your responses to my query above, Coldfire and Auctiongirl, I have to insist that my issue (I'm not commenting about the one that afflicts you, Auctiongirl) is directly correlated to overclocking. I have set my overclocking up, and back down to zero, repeatedly, during the last few days, and the results of the experiment are unvarying and consistent: Every time CPU overclocking is on, the timers (action cool-down counters as well as guildleve timers) are off by a significant amount of time; every time overclocking is turned off, the timers regain their accuracy. Simple and plain.

Furthermore, the time differential (the period by which timers are off) consistently matches the percentile of the overclocking. So, for instance, if I overclock my CPU by 15%, a one minute timer will be off by 9 seconds, every time.

[Coldfire]

Maybe you get 60fps when overclocking and ~50fps when not.

[Hazmatyre]

Much as I appreciate your responses to my query above, Coldfire and Auctiongirl, I have to insist that my issue (I'm not commenting about the one that afflicts you, Auctiongirl) is directly correlated to overclocking. I have set my overclocking up, and back down to zero, repeatedly, during the last few days, and the results of the experiment are unvarying and consistent: Every time CPU overclocking is on, the timers (action cool-down counters as well as guildleve timers) are off by a significant amount of time; every time overclocking is turned off, the timers regain their accuracy. Simple and plain.

Furthermore, the time differential (the period by which timers are off) consistently matches the percentile of the overclocking. So, for instance, if I overclock my CPU by 15%, a one minute timer will be off by 9 seconds, every time.

I got the same issue a few days after the patch came out, but the issue lasted only for that particular day. I haven't noticed anything else after that. I overclocked my quad core Intel processor from 2.8ghz to 3.4ghz.

[indira]

im overclocked i got right timing, maybe you need a processor optimization driver they do exist might want to search intels site.

[Coldfire]

I'm also pretty hardcore overclocked and only got this problem when tanking (and really rarely then).