0
0

If the FMOD Designer is used to create let’s say for example the engine example in the api, is this less memory and cpu friendly than just programming the function regularly in FMOD Ex or is it the exact same and just a easier interface for users with less programming experience. Basically what are the disadvantages with using FMOD Designer instead of programming the code manually?

Thanks

Mac

  • You must to post comments
0
0

It’ll definitely be more runtime overhead to do the engine in Designer than just hand coding it.

With FMOD Designer, you’re basically shifting functionality from code into data, which buys you flexibility/expressiveness at the cost of additional runtime overhead. The main reason you’d want to make that tradeoff is to allow your sound designers to be much less dependent on programmers for creating and integrating audio. It’s potentially a process/production win. However, if you’re a one man show or have relatively little audio, your mileage may vary :)

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.