11 minutes ago, ahoeben said:(that is what the beta is for, right?)
It sure is! Thank you for adding these notes. If you don't mind I'll also add it my initial post, in case not everyone reads all comments.
11 minutes ago, ahoeben said:(that is what the beta is for, right?)
It sure is! Thank you for adding these notes. If you don't mind I'll also add it my initial post, in case not everyone reads all comments.
I am unable to launch 3.2 beta at all.
this is what i am getting
@megablue, can you zip up the folder %APPDATA%\cura\3.2 and post it somewhere so we can download it and have a peek at what is going wrong? In all likeliness something unexpected is happening upgrading your configuration. If you want to run 3.2 anyway, you can empty the %APPDATA%\cura\3.2 folder but leave the 3.2 folder in place. Then you get a fresh start for 3.2. But before you do that, please zip up the contents so the actual issue can be fixed.
Edited by ahoeben48 minutes ago, Skippy7 said:
Noticed the same thing, it also only effects the dark theme
I can confirm this on my system too.
Is there anything in the Adaptive Layers and a model that would prevent it from slicing? Well, it slices, but creates no layers with a Zero print time.
Here the model slices well:
Please not this file has been 'sliced' and ready to send to print over network.
Here I have introduced a model to try to create a void for weights. Adaptive on, and it will not slice:
Please not this file has been 'sliced' and ready to send to print over network with no information.
Same model setup with adaptive off and it slices just fine. Please note that the cylindrical model that is selected has no special features applied to it.
Please not this file has been 'sliced' and ready to send to print over network.
Here is a model that is made of parts and each part only has horizontal expansions applied and it has no slice information.
Please not this file has been 'sliced' and ready to send to print over network with no information.
As soon as I turn off Adaptive, it works just fine.
Please not this file has been 'sliced' and ready to send to print over network.
Also, I used to use the 'infill mesh' with no infill to create a void. What method has replaced it as everything I have tried does not allow the model to slice. Again, it slices, but creates no layers with a Zero print time.
I have not been able to replicate the above. The above image was from 3.1. All others above that one is from 3.2 beta.
The crane model is something I cannot post publicly, but here is the Mandelbrot project file with all parts. The cylindrical object was going to be a void space as above. The Mandlebrot is made of two versions of the same file, one smoothed, one not. Both stacked to create sharp and smooth layers. The cylindrical part going inside the main cardiod to create a void to put weights into as it prints.
UM3E_MandelBrotRaisedExample_PLA-PVA-04mmNoz_02Lay.curaproject.3mf
Edited by kmanstudios6 hours ago, ahoeben said:@megablue, can you zip up the folder %APPDATA%\cura\3.2 and post it somewhere so we can download it and have a peek at what is going wrong? In all likeliness something unexpected is happening upgrading your configuration. If you want to run 3.2 anyway, you can empty the %APPDATA%\cura\3.2 folder but leave the 3.2 folder in place. Then you get a fresh start for 3.2. But before you do that, please zip up the contents so the actual issue can be fixed.
there you go, the 3.2 config files
https://mega.nz/#!0g9HwDZJ!LlNGNr6WQu31OWwU5AiWoHEfQpRSExrUIprVhdRi2es
Solved earlier query, re: Voids for weights.
Here you can see that the walls of each object are respected and 'trimmed to a unified object.'
Here you can see that the interior walls are trimmed to a unified surface, but the interior object's walls do not bend around the borders of the unified surface.
In both cases, the interior of the cylindrical object has no infill and can be used to put weights or other things into the void during printing.
How about ditching the perspective view and switching to an axonometric projection, or at least allowing the users to select one or the other? Engineering CAD is rarely, if ever, done in a perspective view, and such a view is not really appropriate for many situations in a slicer application. The distortion that occurs in the viewport because of the perspective is a hindrance to accurate positioning and nesting of parts on the build plate.
Additionally, allow the 6 (not just 4) primary side views to be viewed without any perspective. Sometimes it's helpful to see the back and bottom views of a build area.
I understood that some fixing was done for the 'pause at height' setting?
Would expect to see a travel movement to the 190,190 position, but still nothing to see...
How do you check where the pause takes place? Also because the height is specified in millimeters and must be recalculated in amount layers..
I find the newly setup selection of everything clicked when you first click on an input field annoying. Most people are already trained to double click to select all values and it makes it a pain to select one digit out of several.
With the tendency to click and drag that has been instilled since day one of the mouse for selection of all things and single clicks and click/drags make this an oddball feature.
If you want something that can be functional is when you make an input and hit enter to set the property, you can have it reselected to help with the fat finger type of typos. 2 instead of 5, etc.
But, the new way is counter to every other program I can think of and requires a lot of retraining just for one function in just one program and presents a lot of agida just to input.
Edit: Oh...and I just saw that its implementation is not uniform across the interface.
Edited by kmanstudiosminor detail: the arrow of the mesh fixes is pointing the wrong way.
Edited by peggybI tested today and have to say, Cura 3.2 is a very big step forward in speed on my Mac.
It started very fast and changes in the Settings going very fast also. I like it a much
The explanation of the threshold for adaptive layers is a bit unclear."This number is compared to the tan of the steepest slope in a layer". Does "tan" mean the trigonometric function "TAN()" or? Is "the number" a slope value or? The steepest slope in a layer? Isn't a "low" slope what usually needs higher resolution? Could be a nice feature, but unclear how it works
Tree support, seems to have a bug when you choose "Touching build plate". Then they stop in mid air:
22 minutes ago, hoegge said:The explanation of the threshold for adaptive layers is a bit unclear."This number is compared to the tan of the steepest slope in a layer". Does "tan" mean the trigonometric function "TAN()" or? Is "the number" a slope value or? The steepest slope in a layer? Isn't a "low" slope what usually needs higher resolution? Could be a nice feature, but unclear how it works
Explanation and implementation can be difficult. See this thread to see if it helps. The last messages are about playing with the numbers. Sometimes, ya just gotta fiddle around a bit.
Does not help much, since there is no explanation there
53 minutes ago, kmanstudios said:Explanation and implementation can be difficult. See this thread to see if it helps. The last messages are about playing with the numbers. Sometimes, ya just gotta fiddle around a bit.
Recommended Posts
ahoeben 1,991
I was not complaining about your copying of the blog post here, but about the blog post ;-)
I have edited my post above to include a preview of what I think is a fairly nifty feature, that would have deserved attention in the blog post.
Something else that is in the beta and deserves a mention is multiextruder replacement patterns in start/end gcode snippets. I understand that is not very sexy for a blog post, but it is important that it is mentioned so that it actually gets tested during the beta period (that is what the beta is for, right?)
You can now use eg {material_print_temperature, 1} to refer explicitly to the print temperature set for the second extruder. You can also refer to an extruder more implicitly by its function, eg {material_standby_temperature, support_extruder}.
Link to post
Share on other sites