Split screen co-op: reactions covering the entire screen

[hallo moin]

Hello!

the local coop split screen is known to have some problems. However, I have not yet read anywhere about a major problem that I have with it, which is why I wanted to ask whether a) others have the same problem and b) whether there is perhaps a solution for it.

The problem: Every time a reaction is offered (oportunity attack, counterspell, smite, etc.) BOTH sides of the screen go completely black with the offer of the reaction. There is no way (that I know of) to somehow (temporarily) make this screen disappear again. One can only say: yes, perform reaction, or no, do not react.

This is extremely unsatisfying.

In the smite example: I perform a melee attack and the screen goes black IMMEDIATELY (so that the smite is offered), you see nothing of the attack animation and also not how much life the opponent still has. It even happens that the attacked opponent has died and you don't notice that.

How can I decide properly whether I want to smite or perform another reaction or not? There is not even the possibility to look at the screen of the second player.

So in terms of gameplay and immersion, this is a very unpleasant bug / game design (i dont think that its intended by the devs).

Any tips or fellow sufferers?

[Archetype]

I don't know why it pauses and covers the screen for both players, but it's definitely annoyed us as well. I wish there was a way to have it only cover the side that is currently affected (for things like portent dice, both sides freezing would be fine). Things like Divine Smite pausing the game every attack for the second player as well gets annoying really quickly, and prevents them from effectively taking their turn simultaneously.

[Nordil(Hun)]

Visit Larian and report the bug to them. They do not monitor or check this forum, or steam at all. Sticky post number 1.

[hallo moin]

i have just submitted a bug report

[hallo moin]

In the patch notes for patch 2, it says under "Controller" - "Combat":
- "Tweaked the Reactions UI"
Unfortunately, absolutely nothing has changed and the problem described above still exists...