ZDaemon

[cockad]

Hi!

I don't know how to tell this but sometimes (actually more often than not), when I join a server and play and let's say I'd like to keep my keys and stats for some minutes (in order to continue the game later), so I just press alt+tab to switch to another program and after a while zdaemon just closes itself. No runtime error messages, nothing, no crash reports etc..

Why does it happen? Does it happen because of CPU overload?

When I want to connect back then it says: "Nick in use"

Once I have managed to test it on my own server and the remote console log only said: "<My player> timed out."

So I presume that my CPU is overloaded and zdaemon cannot "keep pace" with this overload and that's why my ping increases so high that zdaemon disconnects me. Though I don't really know why it closes itself at the same time. Why doesn't it just disconnect the user?

Even if you run the zdaemon but you neither play on any server, nor play offline, it still heavily uses CPU. Question is: why? It just shows the console, there is no game running at all.

[Flambeau]

I had this too.
Often, well always, when out of focus.
On request I tried the "no idle" paramater and ever since this has not happened to me anymore.

Have reported this back, so hopefully it will be solved soon for you too Cockad

[TETSUO]

Really sure you don't have another zdaemon.exe process still running? Check Task Manager - Details.

[cockad]

No. This happens sometimes, but nowadays a bit less frequently.

Recently, it has just disappeared for a short while then it appears again. As far as I know this problem has something to do with the heavily used CPU.

It mainly happens when the focus is not on the ZDaemon itself. (you are using another program meanwhile)

[TETSUO]

Do you use some app which captures your screen? I also recall having similar issue when configuring OBS Studio or Discord to capture zdaemon.exe while it was fullscreen and then switching back to zdaemon

[cockad]

No, I don't. But CPU is only dualcore.

In case of ZDaemon, screen capture can be done after the demo has been recorded.

But I am aware that the ZDaemon heavily depends on CPU usage, so it wouldn't be a wise idea to capture the screen for whatever reason when the ZDaemon is running and morover is out of focus.

[Krawa]

Let's see if it still happens with 1.10.15 or if it's fixed now.

[Flambeau]

2 months in now, did not happen to me anymore.

[cockad]

Nice, it appeared again:

https://i.imgur.com/nc7TLsp.png

[AF-Domains.net]

You never mentioned that previously.

Your original report states "no runtime errors".

This diverges from that.

Submit a new report and provide the proper context regarding what was occurring up until that point.

If you can replicate it, provide those steps.

Otherwise this topic is now locked.