Summary (TL;DR):
A looping sound inside an Audio Gameplay Volume stops being affected by AGV after leaving attenuation and returning from virtualization when virtualization mode is set to Restart. The issue does not occur with Play When Silent and did not exist with the legacy Audio Volume system.
Hello,
I’d like to report a potential bug related to audio virtualization and its interaction with Audio Gameplay Volume (AGV) in Unreal Engine.
Setup:
- A looping sound with attenuation.
- The sound is placed inside an Audio Gameplay Volume.
- Virtualization mode set to Restart.
- The initial state of the sound does not matter — starting within attenuation or starting already virtualized leads to the same issue.
Scenario:
- The sound is actively playing while the listener is within the attenuation range.
- The listener leaves the attenuation range, causing the sound to become virtualized.
- The listener re-enters the attenuation range, and the sound exits virtualization and restarts (as expected with Restart mode).
Expected behavior:
After exiting virtualization, the sound:
- restarts,
- continues to correctly respond to Audio Gameplay Volume (Attenuation and Filter).
Actual behavior:
After exiting virtualization:
- the sound restarts,
- Audio Gameplay Volume no longer affects the sound (no Attenuation or Filter are applied), even though the sound is still within the AGV bounds.
Additional observations:
- This issue does not occur when virtualization is set to Play When Silent (i.e. the sound never enters a virtualized state).
- With the legacy Audio Volume system, sounds could freely enter and exit virtualization while still being correctly affected by the volume.
I’d like to ask whether:
- this behavior is intentional, despite the differences compared to Audio Volume,
- or if this is a known bug that is already being addressed and expected to be fixed in an upcoming patch.
Thank you for your time, and I appreciate any clarification or guidance on this matter.