0
0

While integrating a basic 3D sound update loop (a set3DListenerAttributes() followed by an update() ) into our game, we always got a FMOD_ERR_OUTPUT_DRIVERCALL error immediatly following the first update on the first frame.

After some investigation, we realised that due to a bug in our camera, we passed a forward vector which was the same as the up vector. Correcting this fixed the whole thing. Now sound works perfectly.

The thing is: we passed invalid parameters to set3DListenerAttributes() BUT this method always returned FMOD_OK, leading us to believe that the bug was elsewhere!

This is extremely misleading and it would be great if you could either update the documentation (by saying that passing invalid parameters causes errors down the road) or, better yet, update the code so that set3DListenerAttributes() would return something like FMOD_ERR_INVALID_VECTOR when that situation arises.

Thanks in advance!
(This is using FmodEX 4.06.11)

  • You must to post comments
0
0

I think you get invalid vector errors when it’s not a normal.

  • You must to post comments
0
0

fmod DOES return FMOD_ERR_INVALID_VECTOR but for performance reasons you have to use fmodL version of the library to get the error.

  • You must to post comments
0
0

Oh!

Ok, thanks for the reply.

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.