Not moving when clicking (or using skill)
From what I saw on the video, It's your LMB Attack that causes your death
I slowed down your footage and I saw that you've been default attacking for at least 5 times when the last piety beam hits you (5 weapon swings include your dual wield swings). I believe you are spamming left click and frostblink at that time. What really happened is you perform the attack right when you try to spam the blink, this of course cancels it because of your animation lock on default attack. So from my view to fix your issue : use move only on your LMB and see the results. I cast remi - a very beginner friendly guide : https://www.pathofexile.com/forum/view-thread/2866127 Support me if you want to! ttv/remicaster1 Dernière édition par Remicaster1#7723, le 23 août 2020 à 06:07:55
|
![]() |
" so you have been playing for as long as me (approximately, due to same year but i don't know the date you started) so saying you know more than me, well, in some aspects you may, but not in all aspects. Please, get over yourself. |
![]() |
" It's my LMB attack that caused my death, yes, that is correct. But why? Because the Field Attack of Pieties stopped me from moving due to it not performing MOVE when I was clicking on the ground, and NOT her. But before her beam attack, it was fine. So you tell me that it only happenning after she started her beam attack is not a bug? Even though you are correct, that is not the reason of things. the whole issue is that there is a targeting bug. So you saying what happenned is correct, and that is what happenned, but why did it happen that way? Because of a movement/targeting bug. Move only means that I have to then have another slot used to basic attack. Meaning that on start, left click should be set to move only and right click set to attack, but it isn't like that, it's set as left click is attack. Anyhow, stopping an attack animation is easy to do, I have done it many times to then move. So the issue is still the targeting bug. I don't think anyone can actually push it away from being a targeting bug. the fact that it has happenned enough times means that it's not a one off thing, there are conditions that exist for the error to take place. And it keeps happenning. So while LMB set to MOVE ONLY is a WORKAROUND, it is NOT A FIX. I appreciate the input and your analysis is accurate. |
![]() |
" " With that attack that does one long attack, that means that that attack is mid way and one attack to complete. Which it does have to do. I used fast attack skills, and double does 2 swings with weapons, meaning that it does 2 attacks fast, but that is one skill, but can be cancelled half way through because it does 2 attacks, not one. So the skill is cancelled.Yours is one attack, and during the attack preparation you can move because the attack has not actually begun. But the skill is only one attack. " The issue, while you are accurate, is not about the speed of a skill or anything like that. It's about targeting. Also, near the end there, you were not clicking far enough away from your char to be able to make flame dash take place. So the animation lock you speak of, yes it exists. but it would have had no effect on the situation I was in. as I have explained up above. :) This is why I don't use long attack skills, because that's how my build worked. Fast attacks, easy movement. but this targeting bug caused me to die. And it's happened a few times since, just by chance. Even on the first unique in the game... lol (I was so embarrassed when that happened. But it was the bug so I survived the shame). " Yes, normal players doing troubleshooting and bug testing is not good, but as a bug tester myself I have performed tests time and time again and spent many hours attempting to get different results, and it's just a bug, doesn't always happen with AoE attacks, unless there are given conditions. I can't get EXACT conditions without access to the debug console, I need permission from the devs to use that. And yes, I am glad you said that it is a workaround, not a fix, because that is exactly what it is. And it removes the ability to use a standard attack unless I consume another keybind with a basic attack. Which in itself poses another issue because I have to then get rid of another skill because there would be another I can't use. |
![]() |
" I was testing this with double strike just now (it does have an animation cancel window btw--the window is just tiny on Double Strike and it partially ends after the first strike) and found that while the skill could be animation canceled after the first strike with a move-only command it couldn't be canceled by any other skill (including flame dash, including default attack when targeting an enemy). In other words: you can't flame dash (or move with default attack with mobs under your cursor) out of a Double Strike animation after you're locked into it. Video: https://www.youtube.com/watch?v=M0mZ-c2PH4I Again, not entirely relevant to your original report here but may explain why you couldn't flame dash while you were double striking in your second vid. Also, there's no minimum cast distance for flame dash. You can cast it at your feet and your character will dash the minimum travel distance in the direction of the cursor. Though at the end of my vid I was using move only anyway. |
![]() |
" Yes, the cancelation window is tiny, but I have done it so many times it's not funny. And yes, that is why I click away from the enemy as well as then activating a skill. Because clicking off them causes the cancel and the activation of skill just happens. But theissue still remains about the targeting issue. Which seems to be going off target still, even though I keep trying to bring it back. the skill cancellation/animation.etc isn't the issue here. " " It would explain some things about that incident, but not everything. Because I was not target locked. " I appreciate the tests for the attacks and details and all, it at least validates and removes anything in regards to those skills and all from being a factor and issue in regards to it. Since you have tested as well, I have no doubt that the only issue is the layer bug. :) |
![]() |
This is not a bug.....
Dernière édition par Ryssenryss#0344, le 30 août 2020 à 10:41:21
|
![]() |
is correct, great jobs friend
|
![]() |