0
0

Hi!

How can this be possible?
Sometimes update() fails, returning FMOD_ERR_INVALID_PARAM though it takes no arguments. If I ignore this error, the listener position becomes incorrect and some looped sounds produce noise.
It turns out that about 50 +/- 30 sequential update calls fail and next 50 +/- 30 calls succeed, then fail again and then succeed. Probably this depends on frame rate.
What could be the reason of such behavior?

  • You must to post comments
0
0

This error doesn’t happen if I omit set3DListenerAttributes() call, but in when it is called both cases (when update succeeds or fails) it parameters are nearly equal, direction vectors are normalized and perpendicular.

  • You must to post comments
0
0

Problem seems to be solved by totally removing own sound library from project.

  • You must to post comments
0
0

[quote="brett":38wy2zv1]sometimes due to errors from data fed internally from other places which are eventually processed in system::update, internal functions called by System::update itself can return FMOD_ERR_INVALID_PARAM which feeds all the way back down to the caller.
If i could catch those errors through a reproducable case, i could change it from invalid param to some other error code.[/quote:38wy2zv1]

Why does it only occur for me on the PC then? I am passing the same data on the PC as I am on the Xbox 360 (except for the platform specific fev and fsb files). I am getting this on v49 and have been since ~v30.
Thanks.

  • You must to post comments
0
0

If you are using hardware voices on pc then that is a totally diffferent branch of code to xbox 360 which is all software, and you encounter driver errors etc on windows. That being said recent versions are not getting reports of this error, due to a few fixes, and also invalid param has been changed to other more informative errors.

  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.