Maziani Posted March 5, 2017 Share Posted March 5, 2017 All of these only happen in Jordas Verdict. They do not happen in normal Archwing missions or Neptune missions (mixed Warfarme/Archwing). This is why these are posted under Mission instead of under UI. #1 Bug: Death during The Jordas Verdict [Trial] frequently causes loss of Revive UI element. Happens in both Warframe & Archwing mode. If you die in Warframe mode during Stage 3, you are ejected back to Archwing mode and the Revive UI remains inaccessible. Replication steps: Cannot replicate on demand Frequency: Recently occurring with increased frequency but only recently. Reportedly happening to others that I have been doing trials with. Attempted workarounds: Die in Warframe, wait until Purge, After purge to Archwing, Revive UI does not return Die in Archwing, Revive UI is not accessible Alt-F4, re-log in, reconnect to raid, Revive UI is not accessible (attempted up to 3 times in each raid in which this issue occurred.) #2 Bug: After transition from Archwing to Warframe (during stage 3), Warframe is rendered carrying the Archwing weapon that was active prior to transition, regardless of Warframe weapon equipped. (Weapon behaves like it should for the active Warframe weapon, but graphically, it is rendered as the Warframe weapon.) Replication steps: Cannot replicate on demand Frequency: Rare (Sorry, no photos, looks like I accidentally deleted them thinking the issues weren't frequently enough to comment on.) Notes: This usually is accompanied by other UI elements not working properly (squad HP tiles not updating, weapon stats and focus stats not updating, etc.) Have not attempted any workarounds to clear, since it does not obstruct game play (and Alt-F4ing in the middle of a raid to try to troubleshoot this bug isn't very respectful to the other players I'm squadding with.) #3 Bug: After transitioning from Warframe to Archwing or Archwing to Warframe, the weapon UI element will not update to reflect the actual active weapon (appropriate to the current mode) but will remain on the previous mode's display. Replication steps: Cannot replicate on demand Frequency: Recently occurring with increased frequency but only recently. Reportedly happening to others that I have been doing trials with. Notes: This usually is accompanied by other UI elements not working properly (squad HP tiles not updating, weapon stats and focus stats not updating, etc.) When this bug occurred I was also experiencing both bug #1 and bug #2. After dying, being purged and Alt-F4ing to try to restore Revive UI, the weapon status UI did not update after restart of game. Issue persists across multiple client launches so long as player remains in the same game session. Visual proof 19.12.1 - Bug #1 192.12.1.1 - Bug #3 NOTE: UI thinks that I'm still in Warframe mode, even though I'm showing as being in Archwing mode (and completely able to interact with the game in Archwing mode.) 19.12.1.1 - Bug #1, #3 19.12.1.1 - Bug #1 Link to comment Share on other sites More sharing options...
Maziani Posted March 6, 2017 Author Share Posted March 6, 2017 (edited) 19.12.1.1 - Bug #2 - Trinity in background is wielding the Velocitus and Veritux (Archwing weapons) in Warframe mode. Velocitus is overlapping with a Prisma Quanta. BUG 19.12.1.1 - Bug #3 - Weapon, Squad and Armor Integrity UI elements stop updating Edited March 6, 2017 by Maziani Added another picture to this post rather than posting a new reply to the thread Link to comment Share on other sites More sharing options...
tarfeef101 Posted March 7, 2017 Share Posted March 7, 2017 #1 and #3 happen in conjunction with me all the time. Only done this raid once where this didn't happen to me. One thing I did differently on that raid was ensure to pop antiserum before escaping during the purge. Not sure if this is the cause, but it's something that should be looked into. Link to comment Share on other sites More sharing options...
Maziani Posted March 7, 2017 Author Share Posted March 7, 2017 I was raiding with a group yesterday that commented that these problems are tied directly to anyone in the raid skipping any of the cutscenes or beginning any mission (leaving the spawning area) before everyone in the missions finishes loading. While I did have #2 and #3 during stage 3.1 on the previous Sun-Mon trial cycle (on Monday, prior to 7 PM Eastern resets)-- I did not have any problems during the JV trial where everyone avoided skipping cutscenes or leaving spawning areas before everyone loaded. Bug #2 & #3 (Sun-Mon trial interval) No bugs during Mon-Tue trial interval (where all members of the squad did not skip cutscenes and did not leave spawn area until all players finished loading.) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now