Open Thomasims opened 7 months ago
@Thomasims hi,
Thank you for this bug report.
I have gathered all the information and forwarded it to the QA team. If they need any additional details, I will let you know.
Or we can have a shortcut to bring out the in-game log window anytime anywhere.
Currently it's not easily accessible (editor -> log or F3 profiler -> log; former need to be in editor (obviously) while latter not available in UI such as options menu for global mods)
Hi there!
Got some information regarding this issue.
After calling AllocConsole(), you need to add freopen("CONOUT$", "wt", stdout) on the next line to redirect the output stream. Like this:
AllocConsole(); freopen("CONOUT$", "wt", stdout);
I understand that's the "fix" for the DLL but I still wonder why it's necessary at all; why was this changed in the experimental branch? Does it break the new in-game log window?
Describe the bug
The game's stdout stream is no longer receiving any text (neither the usual game logs nor any
print()
call).Modders never "officially" had access to this but it was easy enough to open a console; Either using a DLL to simply call AllocConsole() on Windows or simply running the game from a shell on Linux.
For many modders, particularly scripters, being able to output text to a (copy-able!) console is invaluable and suffice to say not having access to it anymore is a major setback.
This is also where level load times were written, a very useful data point for map-makers looking to cut down loading screen time. (I do note that this info is still available in
log.txt
, but it remains more convenient to have it on stdout.)Steps to reproduce the behavior
print()
calls for debugging/iteration.Expected behavior
At the very least for
print()
calls to pass through to stdout, as well as level load times (the "Loaded in x seconds" messages).Environment
Additional context
No response