unrealityCatalyst
-
Posts
111 -
Joined
-
Last visited
Posts posted by unrealityCatalyst
-
-
Yup, experiencing it as well, as is a friend. Completed two nodes successfully, and yet they aren't counting as being finished.
-
Has just happened to me as well.
-
Was about to find this to bump it up once again, seeing as I had taken a break and started playing again only to run face first into this bug again.
5 hours ago, UnS3eN said:Nothing to do with knockdown in my case. I was literally just pressing 5 in quick succession to trigger Poise at the start right after spawning.
Hmm, now that's interesting. So it may be a mixture of either Tenno-targeted CC desyncing or something to do with operators getting desynced in and of itself. While each case is different, it's good to get the different kinds of instances of the bug occurring to narrow down what exactly is going on. In this case, what sort of things were you unable to do, outside unable to turn, shoot/attack, or use 1-5? Cause the stagger version of the bug was somewhat different than the knockdown variant, I want to see if this one has any variance.
-
2
-
-
Welp, another update, another long period of the issue going unaddressed. Can't we get at least acknowledgement of the problem?
At the very least, I think I figured out what causes the other instance of ability and attack lockout, where you're still able to visibly turn, but unable to jump/slide/parkour. It's most likely due to desync making the game think you're stuck in a state of stagger, since the behavior of it and knockdown are somewhat different.
Though, given the evidence of it also happening to both specters and now Acolytes in missions where you're alone (which, were those in Solo, or a lobby where nobody had joined yet?), I'm starting to think there may be more issues with both knockdown and stagger than I thought than just simple desyncs at times. There may be some kind of problem somewhere within the more unique movesets and animations used by Warframes, but I have no idea when they could've popped up outside of when I first experienced the no-turn ability/attack lockout way back around 2018-2019. It could've started to occur probably even before then, but I have no way to be sure outside hearing more experiences or anything folks might've recorded back then.
-
1
-
-
I'm... Not 100% sure if that's related or not due to being a specter? Not to mention there's nobody else in the mission, so no idea what's going on there.
-
Yuuuuuup. Juuuuust waiting for dev response. Aaaaany day now.
-
Actually, if anything, the fact that this bug happened on the stream displaying Angels of the Zariman gameplay and yet devs aren't saying anything in here is honestly just depressing. What the heck does somebody have to do to get DE eyes in here?
-
1
-
-
Given the fact that there's so many sources of knockdown in the game, I don't know why this is still not fixed. Best I've been able to avoid it is my friend calling out whenever I'm stuck in knockdown whenever they host and avoiding using 5 after that, but again, that doesn't fix the issue, that just locks you out of vital gameplay mechanics.
-
46 minutes ago, Hectoncheir said:
Oh cool so there's numerous variations of the bug. Wicked.
Has anybody tried using emotes, pulling out a shawzin, or called their archgun to free their characters?
If worse comes to worse, can also do Alt+F4, restart the Warframe client then reconnect to the previous session.I've tried emotes plenty of times, though I don't think I've tried arch gun yet, since that forces a whole, long animation to play. Still, we shouldn't have to be resorting to workarounds for a years old bug.
-
On 2022-10-16 at 1:48 AM, Orion299 said:
That's messed up. Why is DE like this?
No clue. Brought up another bug at one point in regards to multishot and enemy awareness that I pinpointed to starting in 19.6.3 (almost 6 years ago), yet that went completely ignored. That's for another bug report though.
-
3
-
-
Well, the fact that they fixed an issue with animations and abilities when it comes to framerate in 32.0.13 had me somewhat hopeful, but nah, they might not know about the knockdown desync issue still. I've experienced the lockup multiple times even after the hotfix.
Guess I'll just have to keep this years old bug on page 1 until somebody actually looks at it.
-
2
-
-
On 2022-10-12 at 1:03 AM, Hectoncheir said:
Not only is the bug easy to reproduce, it is also just as easy to remove the bug; enter Operator mode, then enter Void mode, and the bug is gone.
What you're describing in the second example might be a somewhat different bug, as the bug I'm describing is completely inescapable outside letting yourself die; Straight up because after returning from operator mode, all abilities are completely locked up, including using 5 to re-enter operator mode.
-
1
-
-
Just going to bump this up once more as I've encountered the operator version of this bug twice since posting and the non-operator version just yesterday during sortie. The frequency this can happen at this point is pretty alarming, especially given just how many sources of knockdown there are in the game at this point. Multiple variants of eximus, multiple enemy types from all the factions, it's hard not to run into this bug, and it's, once again, gone unfixed for years.
-
On 2022-10-01 at 6:37 PM, XHADgaming said:
God yes! Trigger this so many times over the years. Not only do I want to see this fixed but there also needs to be a fail-safe so that it doesn't happen no matter what rather than having to constantly go and fix all of the ways of triggering it.
Well, give it seems to have something to do with knockdown, I feel like whatever issue with that is resolved will keep it from happening again. I say that because I encountered another similar-but-not-the-same issue just last night; After getting knocked down and very quickly getting back up with timing, I once again lost the ability to attack or use abilities, but I also lost the ability to bullet jump. My Warframe was able to turn like normal, however. Of course, friend verified that I was sliding around on the ground stuck in knockdown on their end, so it's still a similar issue and has to do with knockdown in multiplayer lobbies.
-
So, exactly as the title says. I bet most of you have probably experienced this bug at least once or twice. That or way too many times to count. But, after observing things carefully, I figured out what might be happening.
From what I can tell, this is actually stage two of what would otherwise look to be a completely different, otherwise harmless bug.
If you've ever been playing as host in a mission, and have noticed that one of your teammates has been sliding around while laying on the ground in a knocked down position, this is stage one of the bug. I've had a friend that I've constantly been playing with tell me in Discord VC that, whenever they host, they see me suddenly sliding around on the ground prone after getting knocked down, when I clearly got up on my end. If you swap to your Operator and go back to your Warframe after this point, you will advance to stage two of the bug; Unable to shoot, melee, roll dodge, or use abilities (including 5 for going into Operator again). Your Warframe's rotation will also be locked to facing a single direction unless you aim.
My best guess is that there is some form of desync between host and client in the process of sending info about the client player's input to get them standing again. And when you come back from Operator mode, it tries to update this, though only registers the fact that you're still knocked down for the host, therefore thinking that you shouldn't be able to do most actions. Again, this is only a guess though.
As of right now, there's only two ways to escape this bug at stage two, and that is to either enter Archwing mode or to die and lose a life in the mission. Unfortunately, Archwing mode is only available in open world missions, and this bug could very well occur enough times that you could end up unable to respawn after dying enough times (not to mention being entirely nonviable if you're in an Archon Hunt). If you want to avoid this, then when you're still at stage one, you need to wait until either another knockdown occurs and your host confirms that you're standing upright again, or possibly throw yourself into a point that will reset your position. These used to work on stage two, but unfortunately at some point, they ended up not working anymore. And clearly if you're in a public lobby, your host is most likely to not tell you of your knockdown problem, and you end up going Operator and locking up your Warframe.
I've been experiencing this bug for years at this point. There have been other threads that went unanswered and were subsequently auto-archived, though that's probably because there was no clear reproduction to go off of. Then again, the last thread that I had pointed this out in went unanswered as well, and the last post is from November of last year.
Workarounds are not a fix. This is actually a serious, years old bug. Please, somebody get this to a dev's eyes. I can easily state the reproduction here (Which also serves as a TL;DR)
1. Be a client in a multiplayer mission
2. Get knocked down by an enemy and confirm with the host if they see you remain in a prone position after you get up on your end
3. Enter Operator (Optional: possibly also Void Sling), and then go back to your Warframe
4. Your Warframe will lose the ability to perform most vital actions
If anybody else has video of this, that may also help, as I don't have a method of recording.-
23
-
-
Well, this is all find and dandy - If it weren't for the fact I'm having trouble relinking after getting the accounts delinked. 401 - invalid csrf token. Can I get some help over here?
-
Yup, I can confirm this one as well. Not only that, but you continue to hold it while walking around the orbiter and in dojos.
-
Type: In-game
Description: Sometimes, clients participating in Murex raids will not get any form of rewards. I've lost out on possibly thousands of Scarlet Credits at this point. This is also accompanied by the Murex driven away count not updating on the client's end.
Reproduction: It's random whenever this happens, but it seems to become guaranteed if your squad finishes a raid, and then initiates another one from the same flotilla instance.
Expected Results: Rewards from mission
Observed Results: No rewards from mission
Reproduction Rate: It's happened to me way more times than is comfortable, I just want to be rewarded for my efforts.
-
1
-
-
Yeah, confirming the bug, since every instance of the Railjack half I've participated in has not given me any Scarlet Credits. Very disheartening that my efforts are not being rewarded.
-
Yeah, given how low of a count you can receive, sometimes a quick run ends up not being worth it. I've gotten way more 6 count drops of void traces than I'm comfortable with.
Possibly the only reason I want keys back at this point.
-
8 minutes ago, Azure.M said:
Uh, they are disallowed from exilus yes because of that.
Huh. Could've sworn I saw the symbol on those. Still, fairly bs.
-
I honestly feel the argument that reload mods are ineligible because "it affects dps so lol no" is rather invalid. It's far more a QoL for a weapon than it is dps, because it's not like you're actually getting larger numbers out of being able to start shooting the exact same bullets at the exact same rate of fire just a bit sooner.
If we follow that logic further, then clip increasing mods should be disallowed as well because you don't have to reload as often, therefore giving you more dps over those who don't use ammo clip extension.
-
3
-
-
Yup, I've experienced this very same bug a couple of times myself
-
Guh, I saw this after I bought the skin myself... It really feels weird having it not line up properly. Maybe it'll get a fix after DE gets back from their holiday break? I certainly hope so, even if it is something minor.
Incarnon Adapter Weekly Reset Failed; Options were from Week 6 again
in Mission Specific
Posted
Friend just told me the same thing, came to check if anybody else had the same issue, and here we are.