Midnight Grove fatality bug

Basic Info:

Platform: Steam
Issue Type: Gameplay
Game Mode: Single Player
Server Type: PvE
Map: Exiled Lands
Server Name: None
Mods: None

Bug Description:

During the passage of the Midnight Grove and performing a finisher, the character stops moving. The mob I am finishing off is a humanoid, and it just stands still, waiting for the fatality. My character becomes stuck and cannot move. The weapon is sheathed, and to release the character from this state, I need to press the “Use” key. I tested this on multiple mobs, and the issue persists. No mods are being used; it is the base game. Additionally, my thrall runs around this humanoid mob and cannot deal any damage, just as other enemies cannot harm it. While I can move forward and backward, I cannot move in any other direction or perform any other actions. also gives error EMTOE: 0 NOT FOUND IN THE DATA TABLE - TARGET: BASEPLAYERCHAR_C_0

Bug Reproduction:

I deliberately brought the enemy’s HP to 1 when the fatality scene became possible, pressed the attack key, while forcing my companion not to fight so as not to interfere. And then repeated it with another mob already with an active satellite. And it works only on people, that is, on whom you can apply finishing

And one more thing, I noticed that this also happens in the wine cellar, maybe the fatality doesn’t work in dungeons or instances

I just found out that it does not work in any instance on people. the mistakes are the same

That’s right, fatalities do not work in any dungeons at this time.

I already sended bug report and was accepted for processing

Something similar is happening on console (playstation) in the Midnight Grove. When the fatality should occur, the player sheaths the weapon teleports a few feet and in a new direction while getting an error along the lines of ‘emote not possible in current state’.

I put this Q to you as you may be able to answer for me.
Since Funcom are monitoring player usage, do you know if they receive alerts to ‘emote not possible in current state’ error data from player game-play.
I have come across this message on a regular basis on my PC.

I wouldn’t be able to say for certain as I don’t know but I assume it is possible.

It could very well be that all they see was that a fatality was initiated and may not have put in the logic whether it is successful or not. With that said, their data on fatalities may be flawed altogether.