Jump to content
Update 39: Isleweaver: Share Bug Reports and Feedback Here! ×

This bug has been in the game for AGES and has yet to be fixed (chances are you have experienced it atleast once in this week)


-Moctezuma-

Recommended Posts

Posted

That's rigth, I am talking about the bug in which for whatever reason, your Warframe and operator decide to become pacifists and won't allow players to shoot, melee, use abilities, etc

on top of that you moon walk and cannot unbug yourself for the rest of the mission,  usually this isn't a problem in open worlds because i believe k drives allow you to get unbugged, but in every other mission it is very annoying and can make you lose the game

ever since I started playing warframe in 2018, i've encountered this bug probably like 350 times (i am not kidding)

 

Posted
12 minutes ago, -Moctezuma- said:

(chances are you have experienced it atleast once in this week)

Me who never had this bug: 👁️👄👁️

Does going in and out of operator mode fix this? Usually, it's what I do when things bugged out in railjack and that usually fixes the problem.

Posted
2 minutes ago, Aadi880 said:

Does going in and out of operator mode fix this? Usually, it's what I do when things bugged out in railjack and that usually fixes the problem.

nope sadly

Posted

The only thing that can fix this, at least in my experience, is allowing your frame to die completely. Like, to the point where you need to revive yourself. That basically performs a hard reset for your operator and frame. Easier said than done on a tank frame in lower level content though, I will say that. It's annoying to deal with, and I really wish it would get fixed.

Posted

Only noticed it lately with Kahl, and managed to fix it by toggling my weapons. Though I am not surprised the bug still hasn't been fixed.

Posted
20 minutes ago, Lionsheart89 said:

, is allowing your frame to die completely. Like, to the point where you need to revive yourself.

Sadly teammates will try and revive you, and most of the times i get this bug, it wont even allow me to use chat to tell them not to revive me lol

Posted
21 minutes ago, -Moctezuma- said:

Sadly teammates will try and revive you, and most of the times i get this bug, it wont even allow me to use chat to tell them not to revive me lol

lol Yeah. I'm sure they mean well, but that doesn't fix the bug. 

Posted

Amen OP, and it's only been getting worse. I think it's something to do with performing actions while quickly using the Tenno, but honestly there's so much crap happening on screen at once that it's hard to tell. It all started with AotZ/the Sling rework.

Posted
5 часов назад, -Moctezuma- сказал:

Sadly teammates will try and revive you, and most of the times i get this bug, it wont even allow me to use chat to tell them not to revive me lol

You can still use chat while in "esc" menu.

Posted

i've been getting this alot since veilbreaker and it seems to be caused by transference

it was funny at first when i was an ice skating t-pose but it happened during an archon hunt defense, rapidly became very unfunny lol

Posted

I don't think it's a simple bug to fix. It's some kind of state transition problem. It seems to happen when you're switching states and get cc'd in some fashion. There are multiple variants of it: Yareli with her kdrive, Mesa with her ult, operator with frame. That suggests it's more fundamental than a simple bug in player controller code/scripts.

The logic for those scripts or bits of code may be totally fine.  It's probably in the interaction between whatever maintains player state and some other system. It could be some race condition in synchronising state over the network, for example, in which case it'll be difficult for DE to reproduce and track down.

Posted

Most likely nothing they can do about it since it is uhm quite clearly a latency issue causing massive lag.

You can notice it at the start of the clip where you are affected by magnetic distortion several upon several seconds after the magnetic debuff is gone. You are running around with it for 3-4 seconds which means you are in reality having a 3000-4000ms delay. Which is just several times beyond acceptable ms for anything to work properly. Might be caused by cross-play if that was active. Anyways, it is an issue between you and the host, and that is not something DE can fix, atleast not to cater to that massive gap.

Fairly sure this will never ever happen solo unless you have a rig that has extreme issues running the game to begin with.

Posted

I can confirm that I've never had this bug as host and plenty times as client, especially on super laggy hosts (400ms+). Very common in zariman due to operator juggling I guess?

Posted
9 hours ago, -Moctezuma- said:

am talking about the bug in which for whatever reason, your Warframe and operator decide to become pacifists and won't allow players to shoot, melee, use abilities, etc

This is a thing? I've never experienced this.

Closest I've had to it is a reload bug where you can manually reload. It's caused by: 

1. Falling/being knocked off a K-Drive while firing your secondary.

2. 30% chance that when exiting a K-Drive really fast and immediately opening fire. 

9 hours ago, Aadi880 said:

Me who never had this bug: 👁️👄👁️

That's literally my expression.

Surprised it's still around.

Posted
50 minutes ago, SneakyErvin said:

Might be caused by cross-play if that was active. Anyways, it is an issue between you and the host, and that is not something DE can fix, atleast not to cater to that massive gap.

Fairly sure this will never ever happen solo unless you have a rig that has extreme issues running the game to begin with.

This existed before cross play at least with my experiences, I can't say it's entirely common but common enough to be a nuisance. 

Posted
Il y a 1 heure, schilds a dit :

I don't think it's a simple bug to fix. It's some kind of state transition problem. It seems to happen when you're switching states and get cc'd in some fashion. There are multiple variants of it: Yareli with her kdrive, Mesa with her ult, operator with frame. That suggests it's more fundamental than a simple bug in player controller code/scripts.

The logic for those scripts or bits of code may be totally fine.  It's probably in the interaction between whatever maintains player state and some other system. It could be some race condition in synchronising state over the network, for example, in which case it'll be difficult for DE to reproduce and track down.

I player k-drives and yareli a lot so I encounter this bug a few times. It's difficult to reproduce and hard to see exactly what happen exactly but I think it happens when you change state while colliding with either slippery surfaces or some terrain asperity. 

It got fairly much common since Veilbreaker and happens in new situations ( like falling into water with a k-drive ) That increase might be linked to the ragdoll being removed from junction specters (since they did that there is no more ragdolls with direct hits on k-drives, so not impossible it affects other things, but I might be wrong)

 

Il y a 1 heure, SneakyErvin a dit :

Fairly sure this will never ever happen solo

It can happens solo, but latency issues increase the risk. 

 

Il y a 4 heures, Numerikuu a dit :

It all started with AotZ/the Sling rework.

No it was there before and after. It got more common  fairly recently. Like I said, since Veilbreaker.

Posted

I've had that happen to me, one way I can fix it is by bringing up the menu which usually fixes it but not always. I really hope that it get's fixed because it makes it a pain to use the operator if every time I use it I have a chance of my frame not working.

 

Posted

Almost a years old bug but recently found some similar others. No matter how much they update the game they introduce or reintroduce some bugs too. For me this happend when I tried to enter into the plains or fortuna or just did some random mission. As far as I saw this it is not always connected to operators because it happend with me multiple times when I did not used operator at all. Sometimes you cannot cast any ability, use the chat and once I needed abort the missions because the objective bugged too and not accepted I enter the extraction.

Posted

It's some kind of state change thing? I have seen it on Yareli when getting off of Merulina or falling into a reset zone, when playing Operator and using transference back and forth and things like that.

It really does seem more common than it used to be?

Posted
12 hours ago, Aadi880 said:

Me who never had this bug: 👁️👄👁️

Do you only ever play solo / as a host? I've only ever encountered this bug when playing as a client, usually with high ping hosts.

If that's not your case, you have no idea how lucky you are.

Posted
17 minutes ago, p_silveira said:

Do you only ever play solo / as a host? I've only ever encountered this bug when playing as a client, usually with high ping hosts.

If that's not your case, you have no idea how lucky you are.

I've been playing since 2018, since fortuna dropped, I think. I've been playing as a host, solo and as a client.

I've encountered a lot of bugs, but I've never encountered this specific bug, not even in the buggy-ass railjack update.

I have had weird S#&$ happen when on high ping, such as T posing when transference in. Usually though, going in and out of operator fixes the problem eventually.

Posted

I don't recall ever having had this bug, and I play with Vazarin, so I'm popping in and out of operator all the time (and yes, I do play solo most of the time, but not always.... and I'm on fairly crappy internet).

Posted
21 hours ago, -Moctezuma- said:

That's rigth, I am talking about the bug in which for whatever reason, your Warframe and operator decide to become pacifists and won't allow players to shoot, melee, use abilities, etc

on top of that you moon walk and cannot unbug yourself for the rest of the mission,  usually this isn't a problem in open worlds because i believe k drives allow you to get unbugged, but in every other mission it is very annoying and can make you lose the game

ever since I started playing warframe in 2018, i've encountered this bug probably like 350 times (i am not kidding)

 

The only way I know to get unbugged is to die, which is a MASSIVE L if you happen to main Nidus or Wukong, or any tanky frame in a lower level mission.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...