Since the last Arma update [v2.04.147540] the fadeSound command appears not to be working properly. It reduces the sound (as intended) but only temporarily and after a second it jumps back to the starting volume.
Description
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Operating System Version
- 20H2
- Category
- Scripting
Use fadeSound command.
Event Timeline
Hello.
This seems similar to T158124 and might be related, however fadeSound does not reset for me right away as you are describing and is shown in your video. Are you sure you are not forgetting something in the repro steps? Or are you running any mods? Also when you are testing something on a server mention it in the description.
Try the profiling branch as mentioned in the ticket I linked above if it happens there as well.
No, as far as I know I am not missing anything. I am also not running any mods whatsoever nor have ever done so (the same is true for the server). If you want I can try to reproduce the problem in the 3Ditor to see whether the server is the cause but considering that the command did work on the server before and only stopped working after the update I am quite sure that the server is not the cause.
I would try to verify integrity via steam and if that does not help try the profiling branch as I mentioned before.
Cannot reproduce this either. I played with fadeSound scripts last weekend and noticed no issues
I wasn't able to reproduce the error in the 3Ditor either so maybe it only occurs in multiplayer.
I have checked it again and the fadeSound-command still doesn't work on my server but e.g. the fadeEnvironment-command does work just fine and I still don't have any explanation for it.
Can you reproduce without mods? Are you sure there are no mods present? Does this happen in a empty mission in editor preview too?
I don't know exactly why but now that the server runs version [2.04.147719] the fadeSound-command seems to work as usual again.
I will notify you in case anything changes but I think for now this task can be closed although I don't know how to close it.