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
This would be a killer feature for me.
I know the speed limits and speed schedule are available via the web ui and mobile DS get app. But it requires so much clicks, inputs and switches, there's no "turtle" button like the vanilla transmission client has.
Sometimes I need to slow things down, so my remote game streaming won't be interrupted by lags, one button toggle would be really useful in such cases.
Looks like SDM can support this too with GetConfig/SetServerConfig API. If you can get the current config, save it as default one and save the modified config in the settings, it should be possible to toggle between the two (or mutliple) modes. I don't usually use the SDM schedule toggle, but it could be also added to the mode settings in the extension, as part of the modes, or as a separate toggle.
The text was updated successfully, but these errors were encountered:
I see the value in this, though I'm unsure if it's something I want to bring into scope of this project as it's a good chunk of work and I have limited time to keep this project in good working order.
This would be a killer feature for me.
I know the speed limits and speed schedule are available via the web ui and mobile DS get app. But it requires so much clicks, inputs and switches, there's no "turtle" button like the vanilla transmission client has.
Sometimes I need to slow things down, so my remote game streaming won't be interrupted by lags, one button toggle would be really useful in such cases.
Looks like SDM can support this too with GetConfig/SetServerConfig API. If you can get the current config, save it as default one and save the modified config in the settings, it should be possible to toggle between the two (or mutliple) modes. I don't usually use the SDM schedule toggle, but it could be also added to the mode settings in the extension, as part of the modes, or as a separate toggle.
The text was updated successfully, but these errors were encountered: