Hello — I recently upgraded FMOD from 4.04.28 to 4.04.31, and now I’m having problems with EventSystem::load(). At first it wouldn’t compile, so now I’m passing it an EventProject pointer:
[code:3gwtn8lq]FMOD::EventProject *project = NULL;
char *loadMe = "path/to/project.fev";
char *encryptionKey = ""; // or NULL?
FMOD_RESULT result = system->load(loadMe, encryptionKey, &project);[/code:3gwtn8lq]
The result comes back as FMOD_ERR_INVALID_PARAM, and I’m not sure why. This call worked fine in 4.04.28, and the values of the other two paramaters haven’t changed. The path in loadMe is valid. I’m not sure whether the encryption key should be NULL or an empty string, but I’ve tried both and neither works. Why else would the function return an invalid parameter error?
- cort asked 10 years ago
have you tried recompiling your sound data with the latest version of fmod designer as well? If so maybe i could see your project? I just tested a few projects and similar code to yours works ok.
The encryptionkey should be null, otherwise it thinks you’re trying to decrypt the data with that string.
I did recompile the project with the latest version of designer. No dice.
I’ve posted the project (extremely simple, you’ll see) at [url:wj3w5ety]http://www.club.cc.cmu.edu/~cort/sounds.zip[/url:wj3w5ety]. It includes both the source .fdp and all the files created during the build, in case the output is somehow incorrect. Let me know if anything looks suspicious!
Thanks for that we see what happened now.
Just recently, we’ve put a limit on instances of events to 63 maximum, because we released the bit-packed event handle was overflowing its bitfield if the user specified more than 63 max playbacks.
This means if you reduce any current events you have with 64 or more max playbacks, down to 63 or less, it will work.
We’ve changed it so that it doesnt error out like this any more by the way, it just clamps it internally without complaining, this will be in v33 which is this thursday.
Please login first to submit.