-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Last update (#12) causes streams to be too quiet & range does not work #13
Comments
I was hoping this wouldn't be the case but I couldn't find any documentation as to why Set3DFadeDistance is so weird or how to use it properly. It was working fine for me, maybe I'll have to make a modular |
I noticed that in the code, the values seem to be very strange for the set3DFadeDistance function |
Yes, doing the opposite (which would seem correct) yielded the same results as you are having for me. I heard the sound across the map |
Looks like you're right; the values are reversed: if I set the minimum to 1 and maximum to 2000, the sound fades in after I get a (very) far distance away from the E2 chip. |
Very weird so yeah we'll just manually set the volume like streamcore does. Either way we needed to do this in order to add #11 |
Fixes #13, also made the maximum radius and volume settings much more relaxed at 3x volume and 10,000 source units distance radius. If you want it lower, just set your server or client's convars.
Volume is now manually set depending on the distance to the stream & the radius of the stream. It is no longer using Set3DFadeDistance. Fixes #13
The last update (#12) causes streams to have very a low volume (the volume does change when webaudio:volume() is used, but the stream is very quiet), and the audio can be heard regardless of distance from E2 to player. Setting the range seems to make no difference to this.
The text was updated successfully, but these errors were encountered: