Extremely wild display bug during combat -- anyone seen this?

[xzar_monty]

So, after finishing PoE1, I continued to Deadfire, but it seems to me that some bugs have definitely got worse along the way. I just got into a fight, and there's a line in the combat log saying "Leyla abandoned casting Stunning Blow". That's all well and good -- except that I'm getting this message like twenty times per second. Really. It absolutely overwhelms everything else in the combat log, and the display keeps sort of flashing long after I press Pause. This is crazy! This was in the game earlier, but now it's totally, totally wild.

 

What has happened?

 

If anyone still remember the C64 era of the 1980s, the display is almost identical to this basic program:

 

10 Print: "Leyla abandoned casting Stunning Blow"

20 Goto 10

[anishar]

i've also experienced characters going into a loop where they attempt to use a spell or attack and it never goes off, i think it's a known issue and will hopefully get fixed in the next patch coming soonish

[xzar_monty]

Right, so it's not specific to monk or Stunning Blow? That should sort of guarantee that it's going to be fixed, then. Thanks for the reply!

 

Sheesh, the game's been out for almost a year and we're still at this.

[MaxQuest]

Do you use an AoE weapon by any chance?

 

Also what AI behaviour do you use for that character, and have you used others?

[xzar_monty]

I don't use any weapon, a monk with fists. AI completely off.

[xzar_monty]

(Btw, I re-loaded, tried again, it didn't repeat. Also, as I'm at the very beginning of the game I don't even have any AoE weapons.)

[MaxQuest]

That's weird. I remember this bug mentioned on reddit last year. But never encountered this myself.

 

I've encountered another similar bug through: use a full-attack ability with AoE weapon and there is a chance that the character will forget about recovery and will enter into a loop. Swinging like an enraged lumberjack. Although iirc this was already fixed.

 

Btw:

- did your character get interrupted during his first Stunning Blow attempt?

- was mortification consumed?

- did the damage of main hand go through?

[Boeroer]

I guess it's this:

 

https://forums.obsidian.net/topic/105732-bug-v21-commanded-ability-not-executed-flickering-action-icon/

Edited March 31, 2019 by Boeroer

[xzar_monty]

Boeroer: Could well be.

 

MaxQuest: Good questions. I am not certain about the answers, but I think they are: Yes. No. Can't say -- it would have taken an awful lot of scrolling to find that information.

[anishar]

the bug i experience is exactly the one boeroer linked, happens quite a lot...

[AeonsLegend]

I have the same issue. I have to give a movement command for it to go away. Sometimes have to accept a disengagement attack as a result.

[Boeroer]

You can simply cancel the action ("X" button). This will also reset your char and you don't have to move/disengage.

[AeonsLegend]

Good to know

[MaxQuest]

MaxQuest: Good questions. I am not certain about the answers, but I think they are: Yes. No. Can't say -- it would have taken an awful lot of scrolling to find that information.

Understood)

I was basically looking for a cause that could interrupt the current action.

And it seems that dunehunter has posted a plausible one back in september: link. And there have been no answer from the devs since that.

 

It's also unlikely that they will fix it, if they fail to replicate it \

So, for now the workaround is: if the character was running, press X before issuing a new command.