If you execute playSound3D globally (so local = false) on a client, where the position of the sound is about 330 m away, the client will hear the sound delayed by about 1 second. This is expected and wanted.
However, all other clients will hear the sound immediately, regardless of their position.
Description
Description
Details
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 11 x64
- Operating System Version
- 22H2, Build 22621.2428
- Category
- Sound
Steps To Reproduce
- Make a mission, connect two clients.
- Give one Zeus access and move the camera further away.
- Run playSound3D ["A3\Sounds_F\weapons\Grenades\handgrenade_drops\handg_drop_Metal_1.wss", objNull, false, getPosASL player, 5, 1, 1000, 0, false].
Maximum distance does not make a difference.
Additional Information
There is a workaround:
[["A3\Sounds_F\weapons\Grenades\handgrenade_drops\handg_drop_Metal_1.wss", objNull, false, getPosASL player, 5, 1, 1000, 0, true]] remoteExecCall ["playSound3D", 0]
It does the job, but it would be nice to have the command work properly.
Event Timeline
Comment Actions
I can confirm this has been fixed in profiling branch 2.14.151142.
Thank you very much!