- Status New
- Percent Complete
- Task Type Feature Request
- Category Engine → Crashes
- Assigned To No-one
- Operating System
- Severity High
- Priority
- Reported Version 0.6.1
- Due in Version Undecided
-
Due Date
Undecided
-
Votes
5
- Leon (21.05.2012)
- Mario Rohkrämer (17.05.2012)
- Elvi (17.05.2012)
- Minks (17.05.2012)
- Aiwendil (17.05.2012)
- Private
Opened by Mario Rohkrämer - 17.05.2012
Last edited by Mario Rohkrämer - 02.08.2014
FS#5638 - Overhaul errorlog.txt usage, make it contain useful content
There are numerous (at least dozens) complaints in the forum that (especially under Windows) the errorlog.txt contains only uninteresting default errors which are not at all critical, but misses really useful and critical entries instead.
The whole “error console” concept is nonsense for Windows users. Windows builds don’t output anything useful in the console they are started from, and this would be the only console where output could be redirected to files.
If you call the client with the parameter “–console”, a new console is opened, but this one can’t be redirected with “>” or “2>”, you would have to mouse-select as much as you can keep in its history. Most PC users will not know enough about Windows to tweak this console window, maybe not even know how to select and copy from it. On Windows 7 it is even worse, when the client crashed, the new console is nearly disabled, so you almost cannot select and copy text from it after a crash.
2 years later: Severity "High", but state "Unconfirmed"… I'll have to confirm it by myself.