0
0

I’m currently working with CryENGINE 3 SDK and I need to resolve all sound errors or warnings that our build logs.

So what I did is compiled a list of every sound event CryENGINE evokes and the list was huge.

Is there an easy way to have FMOD Designer print out the list of current events stored in a project file so I can systematically comapire those events to the ones CryENGINE is looking for?

for example
CryENGINE event: "sounds/vehicles:vehicle_accessories:light".
Actually FMOD Event: sounds/vehicles:lights/vehicle_accessories:light".

Thanks,

  • You must to post comments
0
0

I don’t think that FMOD Designer has this built-in, but it’s not difficult at all to write a little program to do that.

The basic idea is:
– Load the project using EventSystem::load(), and store off the project ID it returns
– Get the EventProject reference using EventSystem::getProjectByIndex()
– Store off the project name by calling EventProject::getInfo()
– Iterate recursively over every EventGroup using EventProject::getNumGroups() and EventGroup::getNumGroups() followed by EventProject::getGroupByIndex() and EventGroup::getGroupByIndex()
– Store off the EventGroup name at each level by calling EventGroup::getInfo()
– In the recursive call, print out all of the Events. You can get the Events using EventGroup::getNumEvent() and EventGroup::getEventByIndex() (make sure to pass in FMOD_EVENT_INFOONLY so it doesn’t try to load the audio data). When you have the Event, call Event::getInfo() to get its name.

If you’re not a programmer yourself, you can probably ask a programmer to do this for you – shouldn’t take them too long.

Hope that helps!

  • You must to post comments
0
0

You can output all the events in a project by building a programmer’s report from the build menu.

  • You must to post comments
0
0

Heh. Or that 😳

  • You must to post comments
0
0

Sorry for the late response,

Thanks for the support is was all very helpful. Using your sudo code I was able to write a quick program that list all the events that an .fev contains and print them to a .txt file. Now I’m able to do a quick look up on every sound event that Crysis maybe calling.

BTW: The programmers report does list all the events, but I needed the exact string format that Crysis was looking for.

for example :
/particles/explosions/generic_large
sounds/physics:particles/explosions:generic_large

Thanks for the support.

Shawn

  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.