You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.
keyword_mission_successful_audio_clip_ignores_volume_settings_skirmish_sliderresolution_fixedtype_bug | by heatwave
With all in game volume sliders completely to the left (off), the "Mission Successful" audio clip (that is played upon winning a skirmish) is played at your system volume setting.
Steps to Reproduce:
• Slide all warzone volume sliders to the left.
• Keep your global system volume at a point where you can hear it.
• Defeat all rival teams in a skirmish
• Before the game summary screen, you'll hear the usual WZ voice at your system volume say "Mission Successful," despite all volume sliders at zero.
Issue migrated from trac:526 at 2022-04-15 18:19:43 -0700
The text was updated successfully, but these errors were encountered:
#CommitTicketReference repository="" revision="af570f57f83e00e4b6ff73171b22610f0486e61d"
Randomize also map and player positions
Randomize also game map and player's starting positions for further
fun.
NET_numHumanPlayers() cherry-picked from PR #526.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
keyword_mission_successful_audio_clip_ignores_volume_settings_skirmish_slider
resolution_fixed
type_bug
| by heatwaveWith all in game volume sliders completely to the left (off), the "Mission Successful" audio clip (that is played upon winning a skirmish) is played at your system volume setting.
Steps to Reproduce:
• Slide all warzone volume sliders to the left.
• Keep your global system volume at a point where you can hear it.
• Defeat all rival teams in a skirmish
• Before the game summary screen, you'll hear the usual WZ voice at your system volume say "Mission Successful," despite all volume sliders at zero.
Issue migrated from trac:526 at 2022-04-15 18:19:43 -0700
The text was updated successfully, but these errors were encountered: