Closed ghost closed 3 years ago
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 think
hook system for the receiver which will be annoying.. but worth it for future editions and so we don't have constant timers running that do nothing like most addons do
I noticed that in the code, the values seem to be very strange for the set3DFadeDistance function
bass:Set3DFadeDistance(self.radius, 1000000000)
The radius seems to be set to the wrong value? This would modify the minimum radius, not the maximum radius, surely?
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
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.