0
0

I would to use the "L" version of FMOD. I linked to the xxxL.lib. And run with the xxxL.dll. But the log didn’t write to the file, but output to the Visual Studio’s "Output" window, if I run the debug version from VS. If I run the release version drectily, there is no log info and log file. Event though, I exactly set the debugLogFilename to "fmod_internal.log" by calling the function setAdvancedSettings, and it returns FMOD_OK. It still doesn’t work. How can I do to output the log into the file, rather than output to the "Output" window.

  • You must to post comments
0
0

It looks like that functionality has been disabled for a while, what should happen is by default on Windows, Linux and Mac all logs go to a log file when using the ‘L’ version of FMOD (no logging when using the non ‘L’ version). I’ll get that fixed up for our next release, currently all logging is going to the TTY.

For now if you want to redirect it you can do hook a hidden exported API function:

[code:1r7waebq]
FMOD_RESULT F_API FMOD_Debug_SetMode(unsigned int mode, unsigned int buffersize);
[/code:1r7waebq]
Set ‘mode’ to 0 = stdout, 1 = file
Set ‘buffersize’ to 0

  • You must to post comments
0
0

[quote="mathew":3qd1imei]It looks like that functionality has been disabled for a while, what should happen is by default on Windows, Linux and Mac all logs go to a log file when using the ‘L’ version of FMOD (no logging when using the non ‘L’ version). I’ll get that fixed up for our next release, currently all logging is going to the TTY.

For now if you want to redirect it you can do hook a hidden exported API function:

[code:3qd1imei]
FMOD_RESULT F_API FMOD_Debug_SetMode(unsigned int mode, unsigned int buffersize);
[/code:3qd1imei]
Set ‘mode’ to 0 = stdout, 1 = file
Set ‘buffersize’ to 0[/quote:3qd1imei]
This function doesn’t exist. I explicitly declared it, then I got link error. I used the latest stable version (4.40.09).

  • You must to post comments
0
0

Actually the function has existed forever, one thing I missed saying, you need to extern C it.

Regardless, you shouldn’t need that function now, the logging version should correctly output to file with 4.40.09.

  • You must to post comments
0
0

[quote="mathew":3975g6hw]Actually the function has existed forever, one thing I missed saying, you need to extern C it.

Regardless, you shouldn’t need that function now, the logging version should correctly output to file with 4.40.09.[/quote:3975g6hw]
Thanks for your help. It works properly, now.

  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.