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

Dynamic (calculated) line widths not treated correctly by other fields. #5431

Open
3 tasks done
tlhintoq opened this issue May 23, 2024 · 6 comments
Open
3 tasks done
Labels
enhancement New feature or request
Milestone

Comments

@tlhintoq
Copy link

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.1 nightly 22may2024

Operating System (OS)

Windows

OS Version

Win10x64pro

Additional system information

Core i9 11th gen
64gig ram
Nvidia

Printer

Any/all

How to reproduce

Set nozzle diameter - 0.6 in this case
Set a dynamic default line width so the same profile works on a .4 machine as well as a .6 machine. In this example 150%.
Set other lines widths to 0 so they automatically inherit the line width from Default line width. In this example that makes them all 0.8
Tree supports: Set tip diameter to 0.8mm

Actual results

All the math works out that everything is 0.8 in this example. Yet you can't slice this because of error
Organic support tree tip diameter must not be smaller than support material extrusion width.

NOTE: Calculated line widths are also broken if you paint the object with different materials/colors. Basically the calculated width feature which would be awesome is dramatically crippled to the point of not being usable by other elements/features of Orca.

Expected results

The flow of the math, the order of operations carried out, should calculate that all the inherited line widths are 0.8 and therefore this error should not arise.

Project file & Debug log uploads

No project file required as this is reproducable from the instructions above.

Checklist of files to include

  • Log file
  • Project file

Anything else?

2024-05-23_10-37-52

@tlhintoq tlhintoq added the bug Something isn't working label May 23, 2024
@tlhintoq
Copy link
Author

tlhintoq commented May 23, 2024

And just to confirm its a math problem...
Change the 150% to 0.8 and the error goes away - even though the result should be the same.

@tlhintoq
Copy link
Author

Latest 2.1 RC still doesn't address the use of % line widths. Its such a great option that I would love to be able to use it.
Its especially nice when you have machines with different nozzle sizes installed. Great to just set a profile with 150% for example.
But you can't use these dynamic values if you do anything beyond the ultra basics of Orca.
Paint the object - Breaks
Dynamic layer height - breaks

2024-06-19_16-04-01

2024-06-19_16-06-02

CC: @SoftFever

@SoftFever SoftFever added enhancement New feature or request and removed bug Something isn't working labels Jun 20, 2024
@SoftFever SoftFever added this to the 2.2 milestone Jun 20, 2024
@SoftFever
Copy link
Owner

@tlhintoq Can you attach a sample project?

@tlhintoq
Copy link
Author

image

image

DoubleBinV5.zip

@tlhintoq
Copy link
Author

Wait... It may not be the use of % but instead the computed value.
If I hard code the top layer line width to .24 I get the same error.
I can go as low as .28 and its acceptable and slices.

@tlhintoq
Copy link
Author

If you get a chance... Can you shed some light on Flow::with_spacing() ?
I'd like to have more of a true understanding of where this is coming in to play so I can be smarter about some of problems.
Is there some flow spacing or other spacing value this is interacting with and that's where the conflict arises? Or just a hard value that says: "Can't go smaller than 70% of the nozzle width"... something like that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

2 participants