About: CVar timingTestError   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

Blizzard says:

AttributesValues
rdfs:label
  • CVar timingTestError
rdfs:comment
  • Blizzard says:
dcterms:subject
dbkwik:wowwiki/pro...iPageUsesTemplate
Poster
  • Datth
Date
  • 3(xsd:integer)
Link
  • 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 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.
  • 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 :)(en)
Title
  • 3(xsd:integer)
abstract
  • Blizzard says:
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software