OK, I can see that now. Unfortunately, that doesn't work when testing in UDB; it doesn't show you the CLI output window when there's an error messagebox, only the widget screen. I'll have to think about how to work around that.I'm with dpJudas here. The old log window wasn't that great anyway because you couldn't copy text out of it. Reimplementing it wouldn't bring back much of value. If you relly need the startup log for testing, use '-stdout' on the command line. What we might do is adding a CVAR that makes this setting persistent.
In the meantime, what does "-stdout" actually do? The engine seems to write the console output to the CLI window (when I start the engine) anyway
Statistics: Posted by MartinHowe — Mon May 13, 2024 11:08 am