WoW:CVar timingTestError: Difference between revisions
Jump to navigation
Jump to search
3. Re: Meaning of "timingTestError" in Config.wtf | 2010-03-03 20:18 | <span style="color:#ffac04;">Datth</span>
No edit summary |
m (Move page script moved page CVar timingTestError to CVar timingTestError without leaving a redirect) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Stub/API}} | {{Stub/API}} | ||
{{cvar}} | |||
This CVar saves the result of the games internal timing test. | This CVar saves the result of the games internal timing test. | ||
| Line 6: | Line 7: | ||
timingTest is kind of self explanatory; it's a timing test :)<br/> | timingTest is kind of self explanatory; it's a timing test :)<br/> | ||
It basically runs a code on all of your cores and see if they're synced up. If they are, it passes the timing test. If it fails, it gives you a timingTestError. When the game gets one of these, your game will fall back to a "safe" low-resolution timer so that these unsynced cores won't kill the game. You'll hit issues like your framerate being capped out at 64 (since the game refreshes 64 times a second on he low timer) but that's about it. If you force a high resolution timer on an unsynced processor, you'll get really odd timing issues like your cooldowns finish or never finish before they should be, your projectiles will move at really fast or slow rates, you won't turn right, and so on.}} | It basically runs a code on all of your cores and see if they're synced up. If they are, it passes the timing test. If it fails, it gives you a timingTestError. When the game gets one of these, your game will fall back to a "safe" low-resolution timer so that these unsynced cores won't kill the game. You'll hit issues like your framerate being capped out at 64 (since the game refreshes 64 times a second on he low timer) but that's about it. If you force a high resolution timer on an unsynced processor, you'll get really odd timing issues like your cooldowns finish or never finish before they should be, your projectiles will move at really fast or slow rates, you won't turn right, and so on.}} | ||
[[Category:Console variables|timingTestError]] | [[Category:Console variables|timingTestError]] | ||
Latest revision as of 04:48, 15 August 2023
← Console variables < timingTestError
This CVar saves the result of the games internal timing test.
Blizzard says:
timingTest is kind of self explanatory; it's a timing test :)
It basically runs a code on all of your cores and see if they're synced up. If they are, it passes the timing test. If it fails, it gives you a timingTestError. When the game gets one of these, your game will fall back to a "safe" low-resolution timer so that these unsynced cores won't kill the game. You'll hit issues like your framerate being capped out at 64 (since the game refreshes 64 times a second on he low timer) but that's about it. If you force a high resolution timer on an unsynced processor, you'll get really odd timing issues like your cooldowns finish or never finish before they should be, your projectiles will move at really fast or slow rates, you won't turn right, and so on.
It basically runs a code on all of your cores and see if they're synced up. If they are, it passes the timing test. If it fails, it gives you a timingTestError. When the game gets one of these, your game will fall back to a "safe" low-resolution timer so that these unsynced cores won't kill the game. You'll hit issues like your framerate being capped out at 64 (since the game refreshes 64 times a second on he low timer) but that's about it. If you force a high resolution timer on an unsynced processor, you'll get really odd timing issues like your cooldowns finish or never finish before they should be, your projectiles will move at really fast or slow rates, you won't turn right, and so on.