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

Misc. glitches & feature requests. #6442

Closed
amar-s opened this issue Apr 26, 2021 · 2 comments
Closed

Misc. glitches & feature requests. #6442

amar-s opened this issue Apr 26, 2021 · 2 comments

Comments

@amar-s
Copy link

amar-s commented Apr 26, 2021

Version 2.3.0+

Use About->About PrusaSlicer for release versions
^^^
**First Quirk: On Mac OS, the "About Box" should be the first item in the Application ("PrusaSlicer") menu. Having it under the "Help" menu is not according to Mac UI guidelines.

Similarly, "Check for Updates" should go under the application menu, NOT the "Configuration" menu.**

Mac OS 10.14.6

What 3D printer brand / version are you printing on, is it a stock model or did you modify the printer, what firmware is running on your printer, version of the firmware #s

Original Prusa i3 Mk 3.

Behavior

One glitch: I have the skirt turned off (by setting skirt layers to 0). I noticed that the slicing report states 2 minutes print time for the non-existent skirt. This, of course, is incorrect. I believe that what is reported is actually for the skirt AND BRIM. If so, the labeling should be changed to reflect this.

Is this a new feature request?

**Yes, partly.

  1. When I specify a raft, PrusaSlicer makes it fill the entire outer outline of the part. In other slicers I have used, it only makes the raft to a certain perimeter around where the part contacts the build plate (similar to how the brim works). I would like the ability to do this in PrusaSlicer, but don't think there is currently a way to do this.

  2. Also, when I specify support material be used, PrusaSlicer lays down greatly-expanded first layer(s) for the support material. I don't understand why they are so large. I would like a way to control this, so not so much material is wasted under the supports (and this material seems to interact with the brim in strange ways).

  3. With other slicers and printers, I was used to using rafts, since they provided good bed adhesion, and simply peeled away to produce a very clean part bottom. I have had trouble getting such results with PrusaSlicer & i3. I may need to play with settings more to see if I can achieve this.

  4. It seems an odd choice to have support material turned off by default. I think it should be turned on by default. Or at least you should get a warning if it is needed, but not turned on.

  5. It seems that Prusa's preferred method of achieving better bed adhesion is to use a brim rather than a raft. This works well for adhesion, but I find it difficult to easily and cleanly remove the brims from printed parts. I would like a way to increase the spacing between the part and the brim so that it may be more easily and cleanly peeled away from the part. I don't find a way to currently do this. (Separation can only be specified for support/raft material in the vertical direction.) I've played with the elephant foot setting to see if I could make things work better, but it doesn't help much and makes bed adhesion worse, defeating the whole purpose of the brim.**

@rtyr
Copy link
Collaborator

rtyr commented Apr 27, 2021

One glitch: I have the skirt turned off (by setting skirt layers to 0). I noticed that the slicing report states 2 minutes print time for the non-existent skirt. This, of course, is incorrect. I believe that what is reported is actually for the skirt AND BRIM. If so, the labeling should be changed to reflect this.

We will likely rename it.

When I specify a raft, PrusaSlicer makes it fill the entire outer outline of the part. In other slicers I have used, it only makes the raft to a certain perimeter around where the part contacts the build plate (similar to how the brim works). I would like the ability to do this in PrusaSlicer, but don't think there is currently a way to do this.

Raft improvements are already implemented on master. It will be included in PS2.4.0.

raft12

Also, when I specify support material be used, PrusaSlicer lays down greatly-expanded first layer(s) for the support material. I don't understand why they are so large. I would like a way to control this, so not so much material is wasted under the supports (and this material seems to interact with the brim in strange ways).

Also implemented on master. It will be possible to control this in PS2.4.0.

With other slicers and printers, I was used to using rafts, since they provided good bed adhesion, and simply peeled away to produce a very clean part bottom. I have had trouble getting such results with PrusaSlicer & i3. I may need to play with settings more to see if I can achieve this.

It was reworked for PS2.4.0, bridge flow will be no longer used for the first layer on the raft, see #6003 (comment).

It seems an odd choice to have support material turned off by default. I think it should be turned on by default. Or at least you should get a warning if it is needed, but not turned on.

I don't agree. Some warning would be nice though (I believe there is already opened issue for that).

I would like a way to increase the spacing between the part and the brim

That is what elephant foot compensation currently does. Brim offset will be added to PS2.4.0 though.

Please don't combine different topics in one issue, it is difficult to track.

@rtyr
Copy link
Collaborator

rtyr commented Apr 27, 2021

One glitch: I have the skirt turned off (by setting skirt layers to 0). I noticed that the slicing report states......

Label renamed to Skirt/Brim.

**First Quirk: On Mac OS, the "About Box" should be the first item in the Application ("PrusaSlicer") menu. Having it under the "Help" menu is not according to Mac UI guidelines.

Same as #3932.

Similarly, "Check for Updates" should go under the application menu, NOT the "Configuration" menu.

It checks for configuration updates, not application updates.

Closing.

@rtyr rtyr closed this as completed Apr 27, 2021
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

No branches or pull requests

2 participants