Yeah, this patch didn’t fix it, it’s in the “working on” section. I’ve only had it on my FG and haven’t really played it much since. My Paladin isn’t high enough level but haven’t played him in a while either so I’ll wait a bit.
Yeah that’s the existing bug with all movement abilities. I experienced that with Lunge yesterday.
What I think that is, is that there is a hidden value during a movement ability that tells the game to ignore your movement clicks until the movement ability ends, and if you get out of sync with the server due to latency, that hidden value stays active on your client because the server hasn’t told the client to release it, which would happen when the client says “Hey I got to the end of the movement ability.” It could also be that the packet with that message gets lost and needs to be resent but can’t be allowed to without also allowing some form of cheating. Since the server missed it, this will never happen. And it only gets overwritten when you use another movement ability, because the client assumes you might have more than one movement ability or a movement ability with more than one charge, so you can trust the client over the server when you recast, as long as your client and the server agree that was possible.
This is an issue with rollback netcode in general, is that as soon as the client and the server disagree, everything breaks. Also, any instantaneous movement ability is going to cause your new position and the position you were moments ago to vary wildlly, meaning if you lag and trigger a rollback during that, you’re going to jerk back and forth between those two positions.
This is probably solvable with AI (probably how they fix this in games like Overwatch is to pre-generate possible future game states and predict when one of them is going to happen) but indie developers don’t have resources to do stuff like that.
The issue being reffered to is a specific one with FG’s and ring of shields being active when entering timeline quest echoes. There was a thread about it a few patches ago…as long as you dont have RoS active on entry, should be fine.
anyone had this issue? I died without being hurt (still max life) while entering the safe zoom between the Lightless floor 1 and 2 (Titan’s hollow) happened many times.
Death message: slain by a screech from a gloom screecher.
I felt so bad today, I did 6 times lightless in the past 20mins, happened 3 times I couldnt pass to floor 2, and only 2 times I killed the boss, 1 time I could not even progress the boss fight with no “door”!
This was discussed in another thread from March or early April (if I recall). The devs know about the issues with aim assist and have some plans for it. An on/off toggle was also discussed and confirmed to be not outside the realm of possibility.
unfortunately, no eta on either better aim assist or toggle yet.