0
0

After a bit of experimentation I’ve determined FSOUND_3D_SetDistanceFactor only affects the software 3D processing. Is this the correct behavior? This was the cause of 3D sounds not working reliably on different machines in our office; some had 3D hardware sound, others didn’t and the 3D hardware sounds were too low in volume since I use centimeters (set SetDistanceFactor(100.0f)).

Removing this and scaling all positions and velocities by 0.01f gives the expected results on all our systems so I’m just going to ignore SetDistanceFactor, but I thought I’d ask in case this was a bug.

I’m still looking for the cause of sound problems with debug builds; I still have this issue with 3.71.

  • You must to post comments
0
0

Ok, so I read the documentation wrong and thought the value should be number of my units equals a meter (100.0f cm = 1m), not how many meters in one of my units (0.01f m = 1 unit cm)? ‘how many units per meter’ is what the documentation says, not scale factor (I assumed you divided by this value, not multiply) 😉 Your example of using 3.28 to convert feet to meters seems to match my interpretation.

Setting it to 100.0f worked fine for software 3D so I’m a bit confused by your test. On our systems using 0.01f on software makes the sound very low volume (ie. reduced min range and farther from listener) with no effect on hardware.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.