Audiokinetic's Community Q&A is the forum where users can ask and answer questions within the Wwise and Strata communities. If you would like to get an answer from Audiokinetic's Technical support team, make sure you use the Support Tickets page.

+2 votes
Hi, it seems like these two functions got broken between 2017.2.3.6575 and 2018.1.1.6727 Both did nothing and leave object at (0,0,0).

I did a A-B test between these two versions above with UE4's FirstPerson project template.

1. For Ak::SoundEgnine::SetPosition, I changed

AkAudioDevice->SetPosition(this, soundpos);

to

AkAudioDevice->SetPosition(GetAkGameObjectID(), soundpos);

 in UAkComponent::UpdateGameObjectPosition() which switch calling Ak::SpatialAudio::SetPosition to Ak::SoundEngine::SetPosition

 

2. For Ak::SoundEgnine::SetMultiplePositions, it works in 2017.2.3, but in 2018.1.1, the object just stays at where its placed in the level.

 And I made sure I revert one change while testing the other one so they dont coexist.

Is this something that wwise is aware of?
in General Discussion by Lei S. (140 points)
I'm also seeing this after updating to 2018.1.1 yesterday. Did you find a solution?
Sorry for the necro, but I'm experiencing similiar issues on UE 4.21.  I am providing a single AK Component with multiple positions , however the audio appears to play only from the single position of the AKComponent.    Is this a known bug?
nm, I'm just a dum dum.  

In case anyone else is experiencing this issue, make sure you turn off 'bUseSpatialAudio' on any AKComponent you are trying to call SetMultiplePositions() on.  

It will fail if this boolean is enabled!

Please sign-in or register to answer this question.

...