Pointless spam in output_log.txt

[Padishar]

Does everyone else's output_log.txt have the following written after every call to MonoBehaviour.print?

 
(Filename: C:/BuildAgent/work/ea95e74f6e5f192d/Runtime/ExportGenerated/StandalonePlayer/UnityEngineDebug.cpp Line: 54)

That's 1 line with just a space, 1 with the filename and linenumber stuff and 1 empty line. This greatly increases the size of the file and makes it a lot harder to find the output you are looking for. If it does happen for everybody and isn't just a strange quirk of my installation (I presume not) then we should ask Squad to get rid of it. Debugging plugins without a sensible debugger is hard enough without having to wade through megabytes of spam to find your info or regex replace it so you can fit more than 20 lines of your output on the screen...

There are also a couple of messages that come out as:

WheelCollider requires an attached Rigidbody to function.

(Filename:  Line: 167)

So, no filename and a different line number. Presumably that particular bit of code is using a different routine to write to the log than everything else does...

Edited March 12, 2014 by Padishar

[Faark]

Well, you can specify your own log callback and write/filter whatever you want, for example a KSP.log-like file that includes stack traces. Check out KSPLog.AddLogCallback(...) and/or Application.RegisterLogCallback(...). Though i'm afraid you cannot write into KSP.log that way.

"WheelCollider requires an attached Rigidbody to function." is most likely a warning generated by Unity itself.