For several reasons we update FMOD quite often and every now and then when we do this some people end up with dlls or spu-elf/selfs that are out of sync with the libraries. Almost always this will result in a crash and they will scream for my assistance and I will tell them to sync with the latest dlls/selfs/libs/whatever to get things working. To avoid this it would be nice if FMOD could output some kind of error when dlls/selfs are out of sync with libs instead of just crashing. As I see it this is out of my control so I would be really happy if you could add the feature internally in FMOD. Would this be possible?
- Frohagen asked 10 years ago
as for the event library u can make a code check
ver = 0;
pEventSystem->getVersion( &ver );
if( ver != FMOD_EVENT_VERSION )
to see if the runtime libs are teh same version as the ones used at compile time.
other than that, just scream back "Get latest!"
works for me 😉
That was an easy one But I guess it will do the trick at least on win32 since the eventsystem is running from the dll, or? I wonder what will happen on ps3 though since the entire eventsystem is running on the ppu (as I have understood it anyways) that is getVersion will be using the standard libs and not the spu-programs.
I think I was invloved in that one, that is the thread discussing how to link the spu-program to the main executable on the ps3. I think it is posted somewhere in the console forum. Anyways, that still can be a problem since it might happen that someone links the wrong spu-programs and even though that is a stupid thing to do it would be nice to have a safety check. It’s not that it would kill performance or anything as I see it since it will only be done at startup. What do you think ?
Please login first to submit.