Tuning it to 0, made it feel instantly better everywhere. Although they hid the entire thing from UI settings, it's still there and the defaults are truly somewhere around what I posted earlier. Found it out today, and boy has it made a difference alright. So don't be alarmed when you search the file and the entries are gone. They are not lost in the sense.īut it works. However after testing it seems to still be saved somewhere else. Rebooting the game overwrites the file and deletes the entries. console SET MaxSpellStartRecoveryoffset "0"īear in mind, once in the config.wtf file. Because even though you'd be timely in the network world, that queue would still not be processed in time and would do the old element before the new one that got initiated in a timely fashion but failed to be processed timely by the server.Ĭonsequentially you can do a /console SET reducedLagTolerance "1" You can imagine if a queue of around 100-200 can actually do more harm than good. Idk which cvar it is though, google is the place to go.ĮDIT: My connection is fibre(dorm net, has bandwitdh performance problems once in 2 months but is all around superb) 26ms. It worked horribly when it was at default because the default is set around 200ms or so I believe which screws you up if you queue a spell in that window and reconsider during combat but you're too late because the queue already fires the old spell that you found to be a mistake that you wanted to correct but no longer could because of that. So that there'd be no queueing of any spells. The way I worked it was I set it enabled by ticking it and setting the latency factor to 0. I'm guessing it's just a hidden cvar that I'll have to dig up some time as well. I have no clue where it went but that setting on default fucked a lot up. There was a setting that allowed setting the queueing latency before the UI settings revamp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |