This is really starting to annoy me with the new ARC tap 1 for light shot and wait 4 seconds play style. If my recast timers are out by more than 4 seconds I don't get to see the timer tick away for light shot. More often than not my timers are out by around 6-10 seconds. Worst case I've had them out by almost a minute.
Fixing this requires a full shutdown of the game and starting it back up again. I have to do this every time I zone into a new region if I want to see my timers. Zoning into a dungeon doesn't seem to affect it.
Tonight was especially bad, my group decided to do some NMs and since I didn't know where we were going first I shut down the game in Ul'dah and logged back in. We went to buffalo and my timers were out after zoning into La Noscea. I went the whole buffalo fight without knowing when light shot was up. I didn't even bother relogging to fix it again as it would go bad again after going to the next NM.
It's not just an ability recast timer display issue either, it's the game's internal clock as a whole. Starting a leve will display the timer starting at say 29:45 or whatever too. Same with food/buff timers and everywhere else that displays a timer. It's just most evident in abilities. You don't lose the time, it will just hang at 0:00 for the seconds that were cut off or in the case of abilities it will tell you that action can't be used right now.
I can't believe such a massive bug exists and has done since beta. I can't think of a worse bug in the game right now. Why do timers not use your PC's clock and initiate a new timer each time an ability is used? Why is it using some internal clock which is running seconds ahead of where it should be?
I do realise not everyone encounters this but some people do, and that's enough to warrant a fix. This isn't even a bug report thread, I reported it a month ago in the correct forum. Others have reported it too. But discussion in there isn't allowed since threads are locked.
My question is, has anyone actually figured out what causes it and how to stop it happening? I'm hoping there's some temporary way to stop it until SE patch it.