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.

Panning volumes jump from 0 to -infinity instead of interpolating smoothly [closed]

0 votes

Hi, I have a bizarre problem and can't figure out why 3D panning would ever work like this.  I checked everything that I could think of that could have been broken, and have run out of ideas.

What happens, is as you pass a 3D object, the panning volumes jump quickly from (-infinity, 0) to (0, -infinity).  All objects are hard panned

It's a 2D game, so first thought was that the listener was at the same z level and so the angle measured between the listener's orientation and the object was causing it, but after checking the game object profiler it seemed like everything was in the right place. listeners and objects where they should be

I made sure the listener orientation was hard-coded pointing forwards towards the objects.  I also made sure the pan rule was set to "Headphones" by default.

Also, attenuation works fine and the listener moves with the camera, so I can only assume Wwise has everything it should need to calculate panning volumes for each object, but it's not.  I am very confused and would appreciate any ideas as to where else 3D positioning might be broken.

closed with the note: Solved
in General Discussion by Miles F. (250 points)
closed by Miles F.
This is my own personal shame.  When I hard-coded the listener position/orientation, I swapped the y/z values and didn't realize for actual months.  It was pointing straight down instead of forward, and I couldn't tell via the object explorer.
by Miles F. (250 points)
Powered by Question2Answer
...