Exfils '10-second countdown' muted when final active
Buddies and I just completed compiler and instantly hit the exfil.
Final started about 30-seconds into it, our exfil eventually hits the 10-second countdown, but while the notice is at the top of the screen the final 10-second loud beeps don't go off (as final exfil overrides them). So while people are looting it activated early. I managed to slide in, but my other friends with the ganglion and such weren't so lucky and died before getting to the airlock exfil.
Not necessarily a bug, more of a sound-priority issue (the compiler exfil should last longer anyways). My one friend was very mad about it and has been rather verbose in his steam review - admittedly we now know not to hit the exfil until we are about ready to leave - but since it was one of our first few times getting there and final was about to activate - we didn't want to risk it working like a normal exfil. Maybe just a QOL patch to make it last infinitely until final activates (besides player in circle 10-sec activation)? Or make your personal exfil timer take priority over the final for beeping unless final finishes sooner.
Comments
Hello there,
Thank you for your report.
Once a player enters the exfil volume, a 10-second countdown begins, and players inside when that countdown finishes should extract successfully. So if the on-screen notice was there but the usual final 10-second warning beeps did not play, that is a pretty reasonable thing to call out.
Special exfils have higher music/audio priority than regular ones. Final exfil and Compiler exfil are both treated as higher-priority states than a standard exfil, so it is plausible that the final-exfil state is stomping or masking the normal countdown cue here.
Separately, Bungie has already been tracking player confusion around non-final exfils overlapping with the final-exfil timer, including reports where players thought they were safe because the exfil sequence was underway but still died when the match timer hit 0. So even if this specific case is “sound priority” rather than the exact same timer bug, it is clearly in the same family of exfil readability problems.
If the UI says the 10-second countdown has started, the audio warning probably should not be getting buried just because final exfil is active too.
Please sign in to leave a comment.