On 24.03.2012 00:29, syd adams wrote: > I,ve noticed for awhile that sounds seem to cut off at the > reference-distance rather than max-dist. > Is there a new way to do the sound files that Ive missed or is this a bug ? > It is nice that sounds actually stop now , but I must be doing > something wrong .I've been attempting to fix all my sound files but > things aren't working as expected.
Erik should be able to give "authoritative" answers on sound, but AFAIK we're using the "inverse distance clamped" model for attenuation of all sounds. There's a graph showing how "gain" vs "distance" works in this mode - see this OpenAL spec (section 3.4.2): http://connect.creativelabs.com/openal/Documentation/OpenAL%201.1%20Specification.pdf Additionally, FG 2.6 introduced a new range check to free sound resources completely above "maximum distance". That's a check that FG is doing itself - not done by openAL (so not shown in the openAL spec). So, how it should work altogether for FG is: Volume is clamped to a maximum below "reference distance". Volume is attenuated above "reference distance". Sounds are completely cut off above "maximum distance" (since 2.6). If you think it's not behaving as described, it's probably best if you gave an example. cheers, Thorsten ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
