WoW:CVar timingMethod: Difference between revisions
Jump to navigation
Jump to search
m (formatting) |
m (fix category) |
||
| Line 13: | Line 13: | ||
''If this does not help try setting the value to 0.'' | ''If this does not help try setting the value to 0.'' | ||
[[Category:Console variables]] | |||
Blizzard says[http://forums.worldofwarcraft.com/thread.html?topicId=3168405043&pageNo=1&sid=1#5]: | |||
''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.'' | |||
[[Category:Console variables|timingMethod]] | |||
Revision as of 22:20, 20 August 2009
Blizzard says[1]:
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.
Blizzard says[2]:
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.