Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
WoW
Talk
English
Views
Read
Edit
History
More
Search
Navigation
Home
Random page
Help using wiki
Editions
for WoW
for WildStar
for Solar2D
Documentation
for WoW
for WildStar
Reference
WoW
⦁ FrameXML
⦁ AddOns
⦁ API
⦁ WoW Lua
WildStar
⦁ AddOns
⦁ API
⦁ WildStar Lua
Engine
Tools
What links here
Related changes
Special pages
Page information
Site
Recent Changes
Editing
WoW:CVar timingMethod
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{cvar}} Sets internal timing mechanism for the game engine, 0, 1 or 2. * 0 - Default value (highly recommended) * 1 - Low resolution timer for single core CPUs and multicore CPUs that can't sync up. Updates ~64 times a second. * 2 - High resolution timer for multicore CPUs that can sync up. Theoretically updates somewhere above 1000 times a second. Default: SET timingMethod "0" == Details == When the game starts up without this variable or if timingMethod is set to 0, it checks to see if your processor cores can all work at the same speed. If it passes, it gets a 2. If it fails, it gets a 1. It's best to not edit this cvar due to the following: If you force the game to use 1 but you have a multicore system and the cores sync up, you'll be using a lower resolution timer of around 64 times a second. The game won't run as well if you're capable of more. If you force the game to use 2 but your multicore system do not have cores that can sync up, you will experience significant timing issues like your cooldown timers and the actual spell cooldown being way off, or spell/projectile speed issues. == Older Details == Blizzard says[http://forums.wow-europe.com/thread.html;jsessionid=FD0CB4D5DBDA0BC734B5D9C509F45AAB.app09_01?topicId=36613802&sid=1]: <blockquote> There were some improvements made to better support Dual-Core CPUs. This will require adding the following CVAR to the '''Config.wtf''' file located within the '''WTF''' folder inside the World of Warcraft install folder: : set timingMethod "1" You can also type this command in-game, but will require a restart to save the changes: : /console timingmethod 1 If this does not help try setting the value to 0. </blockquote> Blizzard says[http://forums.worldofwarcraft.com/thread.html?topicId=3168405043&pageNo=1&sid=1#5]: <blockquote> timingmethod 1 is generally for systems where the cores do not synchronize. You might run into issues like your framerate caps at 64 instead of your vsync value. timingmethod 2 is a higher resolution timing method and you won't hit the cap with that. </blockquote> [[Category:Console variables|timingMethod]]
Summary:
Please note that all contributions to AddOn Studio are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see
AddOn Studio Wiki:Copyrights
for details).
Submissions must be written by you, or copied from a public domain or similar free resource (see
AddOn Studio Wiki:Copyrights
for details).
Cancel
Editing help
(opens in new window)
Templates used on this page:
Template:Apinav
(
edit
)
Template:Cvar
(
edit
)
Template:Editlink
(
edit
)