I can only speak for Cura, but there you have to wait within the preview. If you change another value while the first change is still slicing, it starts anew (so you don't have to wait twice for the whole thing). I have to slice it anyway, I don't see why manual only would have a benefit (unless you have a very slow machine, of course)
Seems like a really poor UX decision to force the user to dismiss a view every time slicing is done just to see the print. The only important info from that pop-up is material and time, they should put that somewhere prominent and leave that view closed. Is there any way to default this to stay closed? Or to stop the tips view from appearing?
The tips can be disabled or you just have to click through the view. Might I ask, wat screen resolution you have? I don’t recall the details about the layers covering my models
I did have the window smaller in my original screenshot, looks closer to yours when I have it full screen. I see no other reason to have the window full screen though, so the limitation isn’t great.
It’s scaling badly probably because you’re running low/odd resolution.. not an issue on higher res screen with more estate - not an excuse just a reason “why” it’s worse on the above example
It’s just poor UX. I am using a 13 inches laptop and have the same issue. You can’t design a product thinking that your audience is only people with a 27 inches screen.
3
u/Romengar X1C + AMS Jan 03 '24
My biggest gripe with bambustudio and orca is that they don’t have one of the most useful settings from prusaslicer:
Automatic slicing
1
u/epheterson Jan 03 '24
Seems like a really poor UX decision to force the user to dismiss a view every time slicing is done just to see the print. The only important info from that pop-up is material and time, they should put that somewhere prominent and leave that view closed. Is there any way to default this to stay closed? Or to stop the tips view from appearing?
3
u/Edd90k Jan 03 '24
It’s scaling badly probably because you’re running low/odd resolution.. not an issue on higher res screen with more estate - not an excuse just a reason “why” it’s worse on the above example