Feature: enable low-bandwidth mode from the settings screen #293
Conversation
Corrected and clarified the 'MISSING RENDER' error case.
When passed as inline parameters, memory is expressed as MB. However, when passed in a config file, memory was expressed as KB. This created confusion https://discordapp.com/channels/253355867938750485/301912419368697856/541719192252973066 https://discordapp.com/channels/253355867938750485/301912419368697856/541719244094701597 https://discordapp.com/channels/253355867938750485/301912419368697856/541719343684124696
Make config file loader take ram in MB for consistency
clarification of error message
Fix Ant Build
… allow by scheduler depending on the past error, current settings (ram, cpu, gpu,...)
Fix grammar and consistency of README
… anymore, it should be removed
…et#256) * Fix: -renderbucket-size option not applied if configuration file doesn't exist
* Include public key as password in help
* Fix failed MimeType detection * Fix failed MimeType detection * Fix formatting
…tain time (laurent-clouet#249) A new -shutdown <time> option has been created to specify the time when the client will stop asking for new jobs, will finish uploading the frames in the upload queue and will shutdown the computer. The time argument can have two different formats: an absolute date & time in the format yyyy-MM-ddThh:mm:ss (24h format) or a relative time in the format +m where m is the number of minutes from now. The user can also select the shutdown-mode, where "wait" will wait for all the processes (render + pending uploads) to finish and "hard" will cancel all the pending jobs and will initiate the computer shutdown.
…t#282) * restore missing time remaining time in UI with openCL
luguina
changed the title
|
I'm not sure it's the best way to do that feature because the scheduler option is only available on config request so only at the beginning of the session. |
|
I don't see the problem here, TBH. Many applications show this behaviour when you're changing an option that cannot be applied in runtime. Even in the current client, we have the same behaviour in the No Systray option. It requires a client restart to be applied. |
I think the logical place is the configuration call (the one you decided) because is quite unlikely that your configuration will change during a session (moving from low bandwidth to normal or vice-versa), but if restarting the client to apply the new configuration is a serious roadblock for you then we can move it to the request job call to make it dynamic. |
laurent-clouet
force-pushed
the
master
branch
2 times, most recently
from
90c3325 to
7f1949e
Compare
This feature allows the user to activate the low-bandwidth mode from the settings GUI screen.