Lazy Output Log

[kellven]

I've had problems with the F2 log in game being "lazy" since I picked up KSP, usually, but not always when something is screwy with someone's code.

After taking out my frustration on my Esc key, I just noticed that the log does eventually reach the end of it's inbox and display current messages if it's poked enough with new messages.

I'm wondering if anyone knows exactly why it gets backlogged, and if there's anything that can flush it to the bottom other than lots of new spam.

[Kreuzung]

I dunno why, but there's KSP_Data\output_log.txt or so, just open it in a text editor that reloads if the file is changed.

[sal_vager]

The output_log.txt will contain everything that KSP does from startup to shutdown (or crash) including all that you see on the F2 debug display

[erkle64]

I think it's caused by multiline messages.

[kellven]

I was thinking the same about the multiline stuff, of course that could be a wrap issue, or '\n' issue, or a bunch of others. output_log isn't the problem, it's just highly annoying to not have a reliable in-game output for debugging stuff, having to close/restart KSP after every single tiny detail test is just impractical.

[Kreuzung]

You don't have to quit KSP, the logfile is written to the hard drive each time a log message appears (that's probably the reason why logging a lot of things lags the game too).

[dikkjo]

I find the debug console not very usable so i use a little shareware called "baretail" to display the output.log on my other monitor. The advantage of baretail is that you can highlight text with different colors based on search strings, I highly recommend this to any log followers.