In the debug version (xenon is what i’m using) FMOD prints out a ton of sometimes useful information.
This is good for me however the other developers will kill me for spamming debug console.
Is there a runtime way to turn off FMOD’s debug output so that I can enable it when I need it but for those not working on sound it won’t disturb them?
- stephenmccaul asked 12 years ago
can that gDebugLevel be renamed to FMOD::gDebugLevel, or something prefixed. It’s just that Microsoft also has gVars, and it might become accidentaly an issue.
On the project I’m working, I’ve hacked our makefiles to link to the D library if the username or the computername (USERNAME, COMPUTERNAME) is my name.
ifeq ($(USERNAME),dstanev) /* my username */
LIBS += fmod…D.lib
LIBS += fmod…lib
That is not acceptable for us. If it is between a new build and not using the debug info I won’t be able use it. (not entirely my decision) At some points I might be forced to link it in for a one time build but that is error prone and time consuming.
A feature ubiquitous to logging systems is a verbosity control where by differing amounts of detail are printed (status, warning, error, fatal). Our engine has multiple messaging categories with configurable verbosities per category.
Another possibility is to allow us to set a callback for these messages so we can control their output.
Please login first to submit.