Do not hide support speed settings when supports are disabled #2031

New Issue

MrUnknownDE · 2026-04-05T22:43:57+02:00

MrUnknownDE commented

2026-04-05 22:43:57 +02:00

Originally created by @PrimeGoat on 10/1/2025

Is there an existing issue for this feature request?

I have searched the existing issues

Support speed settings disappear when supports are off. At first this seems logical — why show them if supports aren’t enabled? But this creates a real problem for profile creation.

Many printers can run at very high speeds without issues until supports are drawn. That is often the point where split lines and instability occur. To avoid this, supports usually need to be slowed down in profiles. But since support speed options vanish when supports are off, profiles cannot be prepared with tuned support speeds without having to mess around with additional settings.

Even if those values are still saved invisibly in the profile, the fact that they cannot be seen or edited is a UX problem. Profiles should be transparent and complete: tuned support parameters should be confirmed and editable even if supports are disabled at the moment.

Supports are job-dependent (on/off changes depending on the model being printed). But the parameters of supports (like their speed) are profile-dependent. It makes no sense to create duplicate profiles (“supports on” and “supports off”) just to preserve a speed value. A proper profile should always be prepared for the possibility of supports, whether or not they’re active for the current job.

Which printers will be beneficial to this feature?

All

Describe the solution you'd like

Keep support speed sliders visible and editable at all times, so they can be saved in profiles even when supports are disabled.
If clutter is a concern, then at least keep them visible in Developer Mode — after all, that’s the point of dev mode: everything is visible.
There is a potential slippery-slope concern (if one support option is unhidden, why not all of them?). The difference is that most support settings are customization. Speed, however, is different: it simply remains as-is when supports are enabled, so if it wasn’t set correctly, that mistake carries straight into the print. Unlike cosmetic settings (tree vs. grid) that would naturally be reviewed when enabling supports, support speed is stability-critical — the wrong value can literally destroy a job by knocking supports loose or ripping lines, and something that critical should not be hidden.

Describe alternatives you've considered

No response

Additional context

Currently, when supports are disabled, support speed sliders vanish from the Speed panel.
This means profiles cannot be prepared with tuned support speeds without having to mess around with additional settings (like temporarily enabling supports just to edit speeds).
Even if values persist invisibly in the JSON, the lack of visibility/editability makes profiles less trustworthy and harder to manage.
Many printers can run extremely high global speeds, but supports often require slower speeds to prevent failures.
Supports being job toggles rather than profile toggles means every profile should already contain properly tuned support parameters, even if supports default to off.

*Originally created by @PrimeGoat on 10/1/2025* ### Is there an existing issue for this feature request? - [x] I have searched the existing issues ### Is your feature request related to a problem? Support speed settings disappear when supports are off. At first this seems logical — why show them if supports aren’t enabled? But this creates a real problem for profile creation. Many printers can run at very high speeds without issues until supports are drawn. That is often the point where split lines and instability occur. To avoid this, supports usually need to be slowed down in profiles. But since support speed options vanish when supports are off, profiles cannot be prepared with tuned support speeds without having to mess around with additional settings. Even if those values are still saved invisibly in the profile, the fact that they cannot be seen or edited is a UX problem. Profiles should be transparent and complete: tuned support parameters should be confirmed and editable even if supports are disabled at the moment. Supports are job-dependent (on/off changes depending on the model being printed). But the parameters of supports (like their speed) are profile-dependent. It makes no sense to create duplicate profiles (“supports on” and “supports off”) just to preserve a speed value. A proper profile should always be prepared for the possibility of supports, whether or not they’re active for the current job. ### Which printers will be beneficial to this feature? All ### Describe the solution you'd like - Keep support speed sliders visible and editable at all times, so they can be saved in profiles even when supports are disabled. - If clutter is a concern, then at least keep them visible in Developer Mode — after all, that’s the point of dev mode: everything is visible. - There is a potential slippery-slope concern (if one support option is unhidden, why not all of them?). The difference is that most support settings are customization. Speed, however, is different: it simply remains as-is when supports are enabled, so if it wasn’t set correctly, that mistake carries straight into the print. Unlike cosmetic settings (tree vs. grid) that would naturally be reviewed when enabling supports, support speed is stability-critical — the wrong value can literally destroy a job by knocking supports loose or ripping lines, and something that critical should not be hidden. ### Describe alternatives you've considered _No response_ ### Additional context - Currently, when supports are disabled, support speed sliders vanish from the Speed panel. - This means profiles cannot be prepared with tuned support speeds without having to mess around with additional settings (like temporarily enabling supports just to edit speeds). - Even if values persist invisibly in the JSON, the lack of visibility/editability makes profiles less trustworthy and harder to manage. - Many printers can run extremely high global speeds, but supports often require slower speeds to prevent failures. - Supports being job toggles rather than profile toggles means every profile should already contain properly tuned support parameters, even if supports default to off.

MrUnknownDE closed this issue

2026-04-05 22:43:57 +02:00

Sign in to join this conversation.

No Label enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#2031