Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

All AkAmbientSound instance of an Audio Event share the same attenuation start point

0 votes 
We are spawning multiple AkAmbientSound which have the same AkAudioEvent plugged into them. We setup their spread & specialization info, but it seems that if we spawn one (it plays perfectly), then move just out of range of it, and spawn another, it keeps the initial events attenuation start point, so we cant hear the second one play.

I am not sure what we are doing wrong here...is there some issue w/ using the same AkAudioEvent source for multiple AkAmbientSounds? If I don't spawn the first one, then move to the same spot I couldn't hear the 2nd one before, then spawn one, it works fine there. Each ambient sound is heard where it should be, unless its outside of the first ambient sounds attenuation distance.
 
Thanks for any insight!
in General Discussion by Evan B. (170 points)

Please sign-in or register to answer this question.

Powered by Question2Answer
...