Jump to content

unrealityCatalyst

Hunter
  • Posts

    111
  • Joined

  • Last visited

Reputation

158

About unrealityCatalyst

Recent Profile Visitors

576 profile views
  1. Friend just told me the same thing, came to check if anybody else had the same issue, and here we are.
  2. Yup, experiencing it as well, as is a friend. Completed two nodes successfully, and yet they aren't counting as being finished.
  3. 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.
×
×
  • Create New...