WoW:CVar timingMethod: Difference between revisions
Jump to navigation
Jump to search
m (fix category) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{Stub/API}} | {{Stub/API}} | ||
{{cvar}} | |||
Blizzard says[http://forums.wow-europe.com/thread.html;jsessionid=FD0CB4D5DBDA0BC734B5D9C509F45AAB.app09_01?topicId=36613802&sid=1]: | Blizzard says[http://forums.wow-europe.com/thread.html;jsessionid=FD0CB4D5DBDA0BC734B5D9C509F45AAB.app09_01?topicId=36613802&sid=1]: | ||
| Line 22: | Line 23: | ||
''timingmethod 2 is a higher resolution timing method and you won't hit the cap with that.'' | ''timingmethod 2 is a higher resolution timing method and you won't hit the cap with that.'' | ||
[[Category:Console variables|timingMethod]] | [[Category:Console variables|timingMethod]] | ||
Revision as of 23:40, 19 September 2013
← Console variables < timingMethod
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.