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

Brim distance on multiple object #14862

Open
Pentecost95 opened this issue Mar 12, 2023 · 5 comments
Open

Brim distance on multiple object #14862

Pentecost95 opened this issue Mar 12, 2023 · 5 comments
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: Bug The code does not produce the intended behavior.

Comments

@Pentecost95
Copy link

Pentecost95 commented Mar 12, 2023

Application Version

5.3.0

Platform

Windows 11

Printer

Custom

Reproduction steps

  1. general brim distance 0
  2. adding brim distance 0.5 feature on different object using built in feature "Mesh type : Normal model" and adding istruction to single object that i want

Actual results

every object has 0 brim distance

Expected results

object that i selected and adding 0.5 should have that instead remaining 0

Additional information & file uploads

no need additional... just adding feature on single ibject doesn t take effect

@Pentecost95 Pentecost95 added Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Mar 12, 2023
@MariMakes
Copy link
Contributor

Hey @Pentecost95,

Welcome to the UltiMaker Cura Github 🚀
Sorry, it took us a while to get back to you 😞

I took a look and I can reproduce your bug.
image

We introduced some changes to the brim in Cura 5.3, this bug must have snuck in during development.

I'll bring it up to the team to see what they can do to improve it.
It's a feature I use myself as well, so fingers crossed that it can be resolved 🤞.

Thanks for the report! 👍

@MariMakes MariMakes added Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. and removed Status: Triage This ticket requires input from someone of the Cura team labels Apr 3, 2023
@MariMakes MariMakes added Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. and removed Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. labels Apr 6, 2023
@MariMakes
Copy link
Contributor

Hey @Pentecost95,

I brought your issue up with the team, they agree it's worth fixing.
We've added a ticket to the backlog with the intent to improve this.
For internal reference CURA-10503

Thanks for the report! 👍

@Pentecost95
Copy link
Author

Pentecost95 commented Apr 8, 2023

Hey @Pentecost95,

I brought your issue up with the team, they agree it's worth fixing. We've added a ticket to the backlog with the intent to improve this. For internal reference CURA-10503

Thanks for the report! 👍

Thank you for considering this! Hope will fix soon bye ;)

@MariMakes MariMakes reopened this May 4, 2023
@MariMakes
Copy link
Contributor

I'll open this issue again since it's not resolved yet ant this is still something we want to improve.

@Pentecost95
Copy link
Author

I'll open this issue again since it's not resolved yet ant this is still something we want to improve.

sorry i' ve closed by mistake! should be fixed soon yes, it s an important feature bug, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

2 participants