WoW:CVar timingTestError - Revision history

Move page script: Move page script moved page CVar timingTestError to WoW:CVar timingTestError without leaving a redirect

2023-08-15T04:48:05Z

Move page script moved page CVar timingTestError to CVar timingTestError without leaving a redirect

← Older revision

Revision as of 04:48, 15 August 2023

Bear at 23:44, 19 September 2013

2013-09-19T23:44:47Z

← Older revision		Revision as of 23:44, 19 September 2013
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]]

WoWWiki>Gourra at 21:57, 29 September 2010

2010-09-29T21:57:37Z

← Older revision		Revision as of 21:57, 29 September 2010
Line 1:		Line 1:
			{{Stub/API}}
	This CVar saves the result of the games internal timing test.		This CVar saves the result of the games internal timing test.

	Blizzard says[http://forums.worldofwarcraft.com/thread.html?topicId=20566356645]:		Blizzard says:
			{{Bluepost\|poster=Datth\|title=3. Re: Meaning of "timingTestError" in Config.wtf\|date= 03/03/2010 12:18:59 PM PST\|link=http://forums.worldofwarcraft.com/thread.html?topicId=20566356645&pageNo=1&sid=1#3\|body=
			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.}}

	~~''timingTest is kind of self explanatory; it's a timing test~~ :~~)''~~		[[Category:Console variables\|timingTestError]]

	~~''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.''~~

WoWWiki>DaBear78: Created page with "{{Stub/API}} This CVar saves the result of the games internal timing test. Blizzard says[http://forums.worldofwarcraft.com/thread.html?topicId=20566356645]: ''timingTest is ki…"

2010-09-29T21:46:28Z

Created page with "{{Stub/API}} This CVar saves the result of the games internal timing test. Blizzard says[http://forums.worldofwarcraft.com/thread.html?topicId=20566356645]: ''timingTest is ki…"

New page

This CVar saves the result of the games internal timing test.

Blizzard says[http://forums.worldofwarcraft.com/thread.html?topicId=20566356645]:

''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.''