Transference softlock/hardlock

[Colies]

This bug has been existing for years, I'm sure many players have 
encountered the bug, I do not know why it hasn't been fixed yet.

I here provided everything I know so far related to this bug and hope this bug gets fixed sooner......or later

Operationally : 

Spoiler

Transfer to warframe from operator caused this bug to happen, that's sure thing.
From my personal experience, just rapid transference is unlikely to trigger this bug, 
I'm used to subconsciously going void mode as soon as I transfer to the operator to prevent kill, in most cases the bug will happen after that.
Revive by teammate or jump off cliff reset doesn't clear this bug, Only self revive reset can clear this bug.

A rare interesting case that I just encountered recently :
I use void mode in place(no void sling) before reviving by last gasp and the bug are gone. That makes me more convinced that void mode is the problem.

Network :

Spoiler

Playing solo or being the host doesn't trigger this bug. (So far I haven't)
Unstable connections are very likely to make you trigger this bug.
But whether high ping or low ping, the bug would still trigger, I have encountered this bug in both situations. (or it could be VPN)

So I assume that maybe the unstable connection will cause the void mode sync error, the host thinks you're still in the void mode but you aren't and you're not even in the operator form.

What this bug does to gameplay: 

Spoiler

Unable to shoot fire, use melee(but still able to do execution), transfer to the operator, use warframe ability. And furthermore severe in some cases such as unable to use text chat, jump, roll, interact action.

Strange thing : 

Spoiler

Warframe no longer faces the direction of your camera, unless you aiming manually.
The enemy would aim under the warframe instead of aiming at the warframe.

If that is unfixable please just give us something like /kill or /respawn.

Edited June 24, 2023 by Colies

[Megazawr]

Afaik it is due to desync issue with host thinking you are knocked down to the ground and client thinking otherwise, resulting in this bug.

[nghoomoine4]

so for those who has stable connection whether its wifi or broadband or ethernet they confirm wont have this issue with desyncing causing transference not usable?

[Colies]

On 2023-06-25 at 6:39 AM, Megazawr said:

Afaik it is due to desync issue with host thinking you are knocked down to the ground and client thinking otherwise, resulting in this bug.

Knockdown may be one of the ways to cause this bug, in my case, this could happen even without any enemy attacking me.

On 2023-09-06 at 3:13 AM, nghoomoine4 said:

so for those who has stable connection whether its wifi or broadband or ethernet they confirm wont have this issue with desyncing causing transference not usable?

I can only speak for myself, I really have not encountered this bug with a stable connection host, not even once.
And in case you are wondering, my definition of a stable connection is, that you don't experience any weird delay during active fights where a bunch of VFX blinds your eyes, bugs often happen in this situation because the host's hardware can't keep up with that many calculations, so you can't just simply look at the ping to judge is the host connection good or bad. not to mention if the host is using a VPN, you only see the ping of you and the VPN, not the host.