![]() ![]() ![]() They fixed an exploit (that i'm not aware of) by making the spell queue system that has always been there only take the first spell it is told to use where it used to take the last one it was told - meaning that you could overwrite the queued spell if a proc happened (etc.). this is true for any DPS class (and tank) that is GCD-capped - this means basically anyone but rogues who are lmited by energy and rarely by GCD. Spamming keys as a DPSer has always been important to achieve your highest potential. Hmm, this isn't an accurate assessment of what is going on in wow. posted by Tobold 11:45 AM Permanent Link There is really no reason why a game should respond better if you hammer your keys instead of pressing them once. WoW now actively punishes button mashing, and that is good. ![]() Only of course that with the new ability queue if you button mash, you will launch abilities twice which you only wanted once. They are the button mashers, if they want some ability to go off, they hammer the key until it does. If you play it right that is going to improve your ability output, because it gets around the problem of lag making you think you are still on cooldown, while in reality you are not.īut some people complain about the new ability queue, because they are apparently unable to hit a key just once. In the new ability queue system, if you are on global cooldown or in the middle of an action, and press another hotkey, the game remembers that, and queues the ability, performing it after the first one is finished. I do not mash buttons, but press them when appropriate. But if you have too much spell Q like the default 400ms it can delay things like counterspell or POM sheep.įrom what I understand the Spell Q is harmful in too high a value and too low a value so some tuning on your end will be required based on your play style and class.Due to the way I play World of Warcraft, I barely noticed the new ability queue system. The other place spell Q works out great is when you’re chain casting frost bolts for example, and you want them to stack up perfectly with the spell Q its possible to do this flawlessly without any real skill. You can turn it off entirely by replacing 100 with zero or whatever value you like. This will change your spell Q latency to 100ms, but say for example you have a 100ms connection latency then maybe its a good idea to stay above your latency because in some ways the spell Q thing helps with that a little bit in theory at least how I understand it. dump GetCVar("SpellQueueWindow")Ĥ00 ms latency default… =/ this is poop if expect your spells to go off when intended in some cases.įor example if your latency to the server is 100 ms you can reduce the spell Q latency to whatever you like by the following command line. This will help I think, but everything said in this thread is on the money basically. Note: none of the commands on the article were working for me, I had to use the AdvancedInterfaceOptions addon to adjust the CVar. What does this additional time value represent? Is it a constant (from server processes), a measure of reaction time, or keyboard latency? Something else? Where does the 150 come from and has that changed at all with the removal of batching?Īs the 50 from my latency is in ms, presumably the additional 150 is also ms and the CVar is milliseconds. If this is an actual improvement, what number should I actually aim for? Referring to this ubanster article: fix-wow-key-input-lag-latency/ it says to add 150 to your latency, but it is from early 2018. Is this the pseudo improvement mentioned in the previous posts regarding this subject? or with the changes to client and batching is this an actual improvement? In my experience from changing the SpellQueueWindow variable from 400 to 200 (my latency plus 150 - ubanster) my experience as a hunter feels significantly smoother with far less glitchiness in the swing timer I use and the latency (input lag) at which I perceive my button presses to respond with actions. Is this still the case?Īt the start of TBC, the Classic client as far as I am aware was updated to the Legion client, and spell batching was removed. Those posts state that changing this variable does nothing due to it being a variable for the Legion client, and it may only appear to be an improvement. Looking at previous posts on this subject, they were all from Classic WoW, pre-TBC, pre-Legion Client and pre-batching removal. Primarily, I encountered the CVar SpellQueueWindow which is by default set to 400. I’ve been doing some research into how I can reduce input lag when playing TBC Classic and I’ve run into a few curiosities. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |