Descriptive Problem Summary: The logging feature of ss13 stops working if you reuse the dream daemon client without fully terminating it
Numbered Steps to Reproduce Problem: Compile & boot up ss13(I use yogscode), get current logs and see theres like ~15, reboot by using sotp on DD and then start with the start button, notice that only 4 logs show up.
Expected Results: Logging to keep working through restarts
Actual Results: Logging ceases working
Does the problem occur:
Every start after reusing DD
Booting up the server for the first time using a fresh DD client
Workarounds: Keep Terminating/Opening DD
I can't really tell if it's on ss13 side as no runtimes are made, and it's happening with specifically on starts that are not the first in DD
ID:2617730
 Sep 19 2020, 9:22 am
|
|||||||||||||
Resolved
| |||||||||||||
|
Sep 19 2020, 10:28 pm
|
|
Lummox JR
  |
There's not enough information for me to investigate this. If you can reproduce it in a relatively simple test project then that's something I can look into, but I'd be really surprised if SS13's own logging stuff is largely the reason.
|
we have a dll that logging code goes through, i assume it's similar on yog and it could account for issues.
| |
Lummox JR resolved issue
| |