You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.
Would you consider adding a command to resume the renderer?
I know there's already a pause command that handles both pausing and resuming, but sometimes that is not enough, and it's also a bit confusing.
Here is the scenario I'm in (TL;DR below):
I'm running a small private server with a Raspberry Pi 4, using the Pl3xmap plugin for its webmap feature. However, the map has grown to 6GB, and if I keep Pl3xmap running continuously, it can crash the server while updating. To avoid this, I manually pause and resume it, which works well but is a hassle. I want to create a (scheduled bash) script that automatically resumes it at night and pauses it again after a set time. Using the current two-in-one command would be unreliable as it can sometimes accidentally resume it instead of pausing, or vice-versa. So, separate commands would be preferable in this scenario.
TL;DR: The two-in-one command we currently have is unpredictable and unintuitive, and cannot be reliably used in automation. Separate commands would solve those issues.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
Would you consider adding a command to resume the renderer?
I know there's already a
pause
command that handles both pausing and resuming, but sometimes that is not enough, and it's also a bit confusing.Here is the scenario I'm in (TL;DR below):
I'm running a small private server with a Raspberry Pi 4, using the Pl3xmap plugin for its webmap feature. However, the map has grown to 6GB, and if I keep Pl3xmap running continuously, it can crash the server while updating. To avoid this, I manually pause and resume it, which works well but is a hassle. I want to create a (scheduled bash) script that automatically resumes it at night and pauses it again after a set time. Using the current two-in-one command would be unreliable as it can sometimes accidentally resume it instead of pausing, or vice-versa. So, separate commands would be preferable in this scenario.
TL;DR: The two-in-one command we currently have is unpredictable and unintuitive, and cannot be reliably used in automation. Separate commands would solve those issues.
The text was updated successfully, but these errors were encountered: