0
0

I have a problem where a value seems to be set "slowly" and after it’s set several times, the update is "appropriate". Let me define this statement. A sound is created (a vehicle engine defined in FMOD Designer with the typical load/rpm parameters) and after it starts (it can idle for a long time) the first few setValue(); calls the pitch (RPM) does not change. Then, it seems to start working (like after half a second) and the pitch changes just fine. Could this be a buffer set too large and FMOD finally catches up? After it "catches up" then all seems fine. You can drive the engine with RPM afterwards and it responds as you would think it should.

any pointers appreciated!

brad

  • You must to post comments
0
0

Ok, no ideas from anyone?
Let me ask this, is there a buffer that I can change in FMOD? Just to see if it’s a buffer issue?

  • You must to post comments
0
0

Hi brad,

Your description of the problem is a bit vague which makes it difficult to work out exactly what is going on. I would recommend making sure you’re checking the FMOD_RESULT for every function call you make to confirm that they are succeeding. I suspect the cause of the issue could be related to invalid handles or virtualization.

  • You must to post comments
0
0

ok, thanks

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.