Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0b1
Issue ID
1075453
Regression
No
[Audio] "Assertion failed on expression: 'IsFinite(gain)'" thrown when Audio Listener is enabled
How to reproduce:
1. Open the attached project and "Main" scene
Expected result: No assertion appears
Actual result: "Assertion failed on expression: 'IsFinite(gain)'" assertion appears
Reproducible with - 2018.3.0b1 (ab7c83e1efc4), 2018.2.6f1, 2018.2.0a1
-
ReprWasTaken
Sep 03, 2023 16:47
Also getting this issue in 2022.3.4f1
-
sniper02311
Oct 28, 2020 21:26
As a matter of fact, I do believe it might be a negative float that is trying to occur. Try to add in your script, if ("valueyouareusing" < 1) { "valueyouareusing" = 1; }. and then it might fix the error. You can probably use less than one if it is a float also[if needed]. Does that help?
-
sniper02311
Oct 28, 2020 21:22
I am just now seeing this as well. I am using FFT analyzers and referencing script floats, and it didnt not start until I started using those. Yet, the error it likely refers to (something that was "Infinity" as a value before), now works after proper referencing. So, my guess is it might be a reference issue. :/ Any luck on your end?
-
Develax
Apr 09, 2020 14:05
Alex, what was in your scene?
-
alex_roboto
Jan 24, 2020 00:30
That's it? Won't Fix? There's no workaround or explanation why this assert fires? I hate seeing errors when I'm testing my code, and my project has suddenly started throwing this assert every time I start my game.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Resolution Note (2019.2.X):
due to the low priority of the issue, we decided not to fix it.