[[Switch] Bugs while not host: Index Issues, Spontaneous Parazon Kill, Squadmate stuck in knockdown while maintaining non-knockdown play states, Waypoint and HUD issues]

On Friday March 27, 2020 around 8:50 PM CST, I was running as a non-host Limbo in an index run, and Bugframe being Bugframe, Banish and Stasis kept stopping automatically before the clock ran down and didn't give their finishing animations (which may be due to Jad Teran, but with the other issues I kept having, I have some doubts.)

Enemies (and specter allies) keep popping around the map without dying and without particle effects to tell me someone is TP-ing them.

There's something about spawning/being in the rift/not spawning/being in the rift that makes my enemies usually not appear on my minimap even with my massive enemy radar. Walking out of my Cataclysm allowed me to see the enemies on the minimap regardless of where they were rift-wise, and dashing while in my Cataclysm allowed me to see them on the minimap for a few frames and if I did it enough??? or popped in and out of operator enough??? or recast Cataclysm/Stasis at the right time??? the enemies would show up on the minimap both inside and outside the rift again while in my warframe until they died and the process started all over again. For example, I was looking right at an enemy that spawned in right next to me in the rift and it wasn't on my minimap.

I noticed this behavior continue through my second non-host index run that lasted until around 9:35 PM CST.

After working through this abnormal game performance, I chose a lich survival mission with the same host to see if the problem extended beyond what I already noticed. It did. As a client member of the squad, my warframe parazon killed a thrall without the associated button press, though shortly before - while I was not in range to get the prompt - I may have tried reloading my weapons. Also, after extraction became available and my host and I began rushing to the exit, I noticed their warframe was moving around the map stuck in a knockdown position from my game's point of view. They remained in that position until extraction occurred.

 

I don't know if this is just because everyone is home playing WF on Switch because of COVID-19 and aniversary events making the connection quality drop in weird ways or what, but internal game related data isn't moving around to the places where it should be at the times it needs to be there, and that makes it difficult for me to want to play - even as a host, considering that even though I might not witness this behavior that way, anyone who joins with me might.

 

More recently, I've also noticed that in many missions with multiple waypoints that can show up throughout the different stages of a mission, the waypoints from some earlier mission segments don't always go away from the HUD (though they do get cleaned up on the minimap) after their segment is completed, e.g., excavation waypoints after the excavation completes and the initial alarm panel after setting it off to begin a survival mission. The problem here is clutter on the screen distracting from the current mission objective and whatever enemies might be around if enough residual waypoints remain from endless missions. I haven't used needed to use life support since noticing this issue, so I haven't discovered if the lifesupport tower waypoints fall under the same buggy behavior, but I suspect they do.

Also, a more minor issue: the waypoints for all points of interest and HUD components related to enemy/ally health/shields/names still turns read and remains that way for the remainder of the Lich mission after the enemy Lich spawns in.

[Game freeze on chat window input open]

Username: Macbow333

Approximate bug time: 2019-7-20 2:36 AM CST

Playing: Equinox Prime, Hek, Pyrana Prime, Plague Star Polearm Zaw, Helios, Deconstructor

Mission: Lith Extractor, Grustrag Three assassin squad had spawned and were defeated, got a Brakk BP.

Completed first extractor pair and got a Fang Prime Handle.

Working on second W1 Radiant Relic in the mission and fourth & fifth extractor.

Opened pause menu to be able to open chat window.

Grove Guardian NW mission appeared and was the last NW mission to need completing in the current NW week at time of posting.

Opened chat window and pressed "Y" to open NS text input UI.

Game froze on that combined action. May have encountered some sort of race condition with another command the Switch was processing, or could be some peculiar unhandled exception.

[Frost Snowglobe UI Glitch]

There's a Frost ability HUD bug on Nintendo Switch that's been around for a few months.

I can cast Frost's Snowglobe ability normally.

Its startup behavior functions as expected.

Its status effect behaves as expected.

Its armor/health behaves as expected on the actual Snowglobe in the environment, but in the HUD for his skills in the corner of the screen, the percentage health drops incorrectly from whatever percentage health the bubble is at to 0 shortly after startup behavior is complete. This behavior does not track with the actual health of what the bubble has, as it last for a substantial amount of time after the HUD says it's at 0% health.

Are the Switch devs aware of this bug? Either way, will there be a fix in the works for this bug in the next few updates?

[Orb Vallis Crash and lost nightwave progress]

So... this is still an issue, but on top of all that, after I got back in after reloading the game at around 2:40AM CST, I tried fishing more, but then a host migration happened when they returned to Fortuna, but I wound up on Plains when I was on Vallis before the migration.

I'm not sure what all I should say here, or if I should create a new thread for this issue... It's my first post on these forums, too.