[Feature Request] Per-Object Process Preset Binding with Inheritance #811

New Issue

MrUnknownDE · 2026-04-05T16:31:52+02:00

MrUnknownDE commented

2026-04-05 16:31:52 +02:00

Originally created by @ReverendRhyme on 2/11/2026

Is there an existing issue for this feature request?

I have searched the existing issues

Yes.

OrcaSlicer currently allows per-object overrides, but not persistent per-object Process preset binding. In practical workflows, this forces users to manually tune many fields one by one and maintain those values manually.

This is especially painful for multipart jobs (for example, model + custom supports as separate STLs) where objects must stay aligned on one plate but use different process intents.

Which printers will be beneficial to this feature?

All

Describe the solution you'd like

Add per-object Process preset binding with inheritance.

Core behavior (MVP)

Each object can select a Process preset from available presets
Object inherits values from that preset by default
Per-object overrides remain supported
Overridden values are clearly indicated
Overridden values can be reset to inherited preset values
Objects remain aligned on one plate while using different object-level Process presets

Why this is distinct from copy/paste requests

Copy/paste settings is a one-time transfer. This request is about a persistent relationship:

object -> bound preset -> inherited defaults
local overrides on top
predictable reset-back-to-preset behavior

So copy/paste can be complementary, but it does not replace object-level preset binding/inheritance.

Example workflow

miniature STL -> high-detail preset (e.g. 0.05mm)
supports STL -> faster/lower-detail preset (e.g. 0.10mm, fewer walls, lower infill)
Both stay aligned on one plate

Describe alternatives you've considered

Per-object manual overrides
- Works, but requires touching many fields and is error-prone to maintain
Separate plates
- Allows different presets, but breaks same-plate alignment/workflow
Manual value copying
- Tedious and not persistent; does not provide inheritance semantics

Additional context

Non-goals for MVP

No redesign of global preset architecture
No mandatory object-linking/transform system changes

Backward compatibility

Existing projects keep current behavior unless an object has explicit process preset binding
No migration breakage expected

Suggested phased rollout

Per-object preset binding + inheritance resolution
Override indicators + reset-to-preset UX
Optional helper actions (apply/copy settings)

*Originally created by @ReverendRhyme on 2/11/2026* ### Is there an existing issue for this feature request? - [x] I have searched the existing issues ### Is your feature request related to a problem? Yes. OrcaSlicer currently allows per-object overrides, but not persistent **per-object Process preset binding**. In practical workflows, this forces users to manually tune many fields one by one and maintain those values manually. This is especially painful for multipart jobs (for example, model + custom supports as separate STLs) where objects must stay aligned on one plate but use different process intents. ### Which printers will be beneficial to this feature? All ### Describe the solution you'd like Add **per-object Process preset binding with inheritance**. #### Core behavior (MVP) - Each object can select a Process preset from available presets - Object inherits values from that preset by default - Per-object overrides remain supported - Overridden values are clearly indicated - Overridden values can be reset to inherited preset values - Objects remain aligned on one plate while using different object-level Process presets #### Why this is distinct from copy/paste requests Copy/paste settings is a one-time transfer. This request is about a persistent relationship: - object -> bound preset -> inherited defaults - local overrides on top - predictable reset-back-to-preset behavior So copy/paste can be complementary, but it does not replace object-level preset binding/inheritance. #### Example workflow - miniature STL -> high-detail preset (e.g. 0.05mm) - supports STL -> faster/lower-detail preset (e.g. 0.10mm, fewer walls, lower infill) - Both stay aligned on one plate ### Describe alternatives you've considered 1. Per-object manual overrides - Works, but requires touching many fields and is error-prone to maintain 2. Separate plates - Allows different presets, but breaks same-plate alignment/workflow 3. Manual value copying - Tedious and not persistent; does not provide inheritance semantics ### Additional context #### Non-goals for MVP - No redesign of global preset architecture - No mandatory object-linking/transform system changes #### Backward compatibility - Existing projects keep current behavior unless an object has explicit process preset binding - No migration breakage expected #### Suggested phased rollout 1. Per-object preset binding + inheritance resolution 2. Override indicators + reset-to-preset UX 3. Optional helper actions (apply/copy settings) <img width="493" height="921" alt="Image" src="https://github.com/user-attachments/assets/6e437ce8-e086-419b-b78e-095aa8edc33d" /> <img width="441" height="329" alt="Image" src="https://github.com/user-attachments/assets/2b5feec0-5686-4f14-9613-89ef50b0b718" /> <img width="454" height="334" alt="Image" src="https://github.com/user-attachments/assets/095a27b1-a3b2-4b0d-9e1a-3fe8cdf32c00" />

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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#811