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 overhaul: New features and bug fixes #11678

Merged
merged 16 commits into from
Oct 30, 2022
Merged

Conversation

BagelOrb
Copy link
Contributor

Frontend component of Ultimaker/CuraEngine#1613

With the new implementation we don't need that much clearance.
With the new brim algorithms the brim will never be generated outside of the volume.
It's nice to be able to input 9999 if you want the brim to cover the whole build plate...
... for testing purposes ;)
The prime tower should no longer be displaced by the brim width
it allows for removing the brim inside holes completely if set to a high value,
or just keep it a small distance away from internal holes
it is handled by CuraEngine now.
@MariMakes
Copy link
Contributor

Thanks! For internal reference CURA-9066

@github-actions
Copy link
Contributor

github-actions bot commented Oct 28, 2022

Unit Test Results

15 651 tests   - 1   15 649 ✔️  - 1   48s ⏱️ +5s
         1 suites ±0            2 💤 ±0 
         1 files   ±0            0 ±0 

Results for commit 45fb71e. ± Comparison against base commit a9f4b2d.

♻️ This comment has been updated with latest results.

Some brim settings seemed to behave as if they where linked, when in fact for any extruder set to -1 the 'default extruder' was set by some hacky code that supposedly fixes a 'dissallowed area' issue, very likely also related to the skirt/brim settings. Since dissalowed area for skirt/brim will not be a thing anymore, at least in the front-end, due to CURA-9066 (the 'parent' jira ticket that was blocked by this bug); it was sinplest just to remove the hack altogether. (Otherwise we'd have to make an artificial distinction between -1 and None as it relates to 'Not Set/Used' versus 'Not Overridden', only to then force it back to -1 in situations that call for it -- like communicating to the engine.)

CURA-9553
@rburema rburema merged commit f75cb7a into main Oct 30, 2022
@rburema rburema deleted the brim_per_material_optimized_order branch October 30, 2022 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants