Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cura doesn't use the Support X/Y Distance set on individual custom support #9882

Open
5axes opened this issue May 21, 2021 · 8 comments
Open
Labels
Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes Type: Bug The code does not produce the intended behavior.

Comments

@5axes
Copy link
Contributor

5axes commented May 21, 2021

Application Version

Not related to release exist for a long time but still there in 4.9

Reproduction steps

Define a custom support
Set an individual Support X/Y Distance
Set an other value for this settings in the Global profil

Actual results

Cura will only use the global settings to create the support

Expected results

As it is possible to define an individual value for every support expecting to be able to modify localy the result.

Note : Certainly same type of limitation as this report : #8082 (CURA-7610 for other developers)

Additional information & file uploads

image

@5axes 5axes added the Type: Bug The code does not produce the intended behavior. label May 21, 2021
@fvrmr
Copy link
Contributor

fvrmr commented May 21, 2021

Hi @5axes thank you for your bug report.
I can reproduce this issue. I will discuss this with the team. Keep you posted!

@evtrados
Copy link
Contributor

Developers: See internal ticket CURA-8260

@Ghostkeeper
Copy link
Collaborator

The X/Y distance currently functions as a per-object setting like "how much distance should support keep from this model". Since support is not keeping distance from other support meshes, overriding the setting in a support mesh is useless.

@5axes
Copy link
Contributor Author

5axes commented Jun 4, 2021

Not sure to understand ... Yes the issue is how to define a customised support X/Y distance on a support mesh. As it is possible to define this distance individualy via a per-object settings it should be possible to use this value and not just the global settings ? We don't talk about distance between supports themselve but distance between the customized support and the model.
image

@Ghostkeeper
Copy link
Collaborator

Basically there are conflicting requirements here then. The Support X/Y Distance says "all support needs to keep this much distance from the model". The model still has a Support X/Y Distance set to 1.0mm (because the extruder's setting is not specialised for the model), so all support keeps 1.0mm distance from the model. Including that custom support.

What would you expect to happen if you set the Support X/Y Distance for the model to 2.0mm and the Support X/Y Distance for the support mesh to 0.16mm?

@5axes
Copy link
Contributor Author

5axes commented Jun 4, 2021

On my point of view if we can define a value on a customized support , this value should be the final distance between the Model and this particular support. If you can specify a value ( here it's the X/Y Distance) this value should be used to calculate the support according to your local modification and the other support will be calculated according to the general settings.

@Ghostkeeper
Copy link
Collaborator

Similarly, if we can define a value on a single model, this value should be the final distance between that model and all the support.

You have two distances here. Both can be specialised, for either of the models. Cura says that the value specialised in the individual meshes wins. You say that the value specialised in support meshes should win. In reality, they are conflicting constraints.

The conflict is currently resolved in the way that I would expect, but not in the way that you would expect. There is a ticket for it now though, so another developer should eventually look at it to see whom they agree with.

@GregValiant GregValiant added Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes labels Nov 19, 2024
@GregValiant
Copy link
Collaborator

Is this still an issue in current Cura versions (5.8.0 and up)? Can this be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

5 participants