Jump to content
Ultimaker Community of 3D Printing Experts


Team Ultimaker
  • Content Count

  • Joined

  • Last visited

  • Days Won


rburema last won the day on August 30 2020

rburema had the most liked content!

Community Reputation

17 Good

Personal Information

  • Country
  • Industry
    R&D / Exploration

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The fix that @burtoogle made for the OP has been deemed low risk enough that we'll try to get it in 4.7, a beta of which should be out relatively shortly.
  2. We have made the explanation a little more clear for 4.7 (not out yet), see this topic: https://github.com/Ultimaker/Cura/issues/7592 The new explanation is a little longer, and mentions the switched-to profile. The column names are also changed from 'Default'/'Customized' to the switched-to profile name and 'Current Changes'. If you want to save the changes (to a new profile), you can select 'Create Profile From Current Settings/Overrides ...' in the drop-down menu, before changing (there is another menu-item for updating one you made earlier).
  3. Not directly, but something like this can be done. It's a bit cumbersome though. You can get the face-id of the face under a screen-position with SelectionPass.getFaceIdAtPosition, then work out the intended object, then get the normal from the/that mesh. (For example as happens in SelectionTool._pixelSelection) As an alternative; if your plugin has it's own stage (like next to Prepare, Preview, Monitor) then I think it becomes an option to write your own RenderPass and shader to get the normal out that way.
  4. Sadly this is the stair-stepping again (somehow). I think we should look into rethinking that whole piece of code, given the amount of trouble it causes us and how hard it is to debug. It does, most of the time, give a nice workaround though: Just put 'support stair step height' to 0.0 mm and the missing support will appear.
  5. @Reverse_Engineer The 'action' button (the big blue one that says slice) changes to a print-over-network/save-to-USB/save-to-file button, this can be changed with the arrow next to it once sliced. Alternatively, after slicing, select 'Export...' and select '*.gcode' in the 'Save as type:' dropdown in the save-window. As a last resort/workaround (for most printers), unzip the .3mf and find the .gcode file within.
  6. Yes, you can download the 4.2-BETA here. Otherwise wait +- two weeks before 4.2 proper is released.
  7. Confirmed this behaviour in version 4.1 for the UM5 file at least. I also tried to slice it in the 4.2-BETA (I remember something we changed for a bugfix) which _does_ seem to have the first layer support 🙂 ... so, it seems unlikely the problem was on your end!
  8. If you want relatively easy to remove supports, you might want to try the (sadly still experimental) Tree-support: Disable normal support, and enable 'Tree Support' in the experimental tab (you might need 'show all settings' first). It'll take a longer time to slice (but not nescesarily print), but most of the time its worth it. Other than that, it's a bit of a trade-off between what'll actually print well and your particular model.
  9. @Astrofreak85 We did pull in something that was previously available as a mod by one of our community members (the 'Creawesome' mod) that could have changed the Ender definitions, but I'm not sure those are the intended changes.
  10. @andy3820 While it isn't under any active development any more, we do support USB connections for at least some printers. The USB detection may or may not work for certain models, but it is there.
  11. The only part that is really inconsistent is the Line Type - Color Scheme legend (also the Skin Overlap settings should be in the Shell catagory I guess.) Concerning the settings (not the Line Type as shown in Preview): - Shell is all outer parts / (near the) outside of the model. - Walls are the vertical (enough) parts of the shell, and thus part of the shell. (They're red and green in the preview.) - Skin is the horizontal parts of the shell, and also part of it. Not just the top, but also the bottom! Yes, this also means that the lowest layer of a bridge is ski
  12. Concerning the height: What happens there is that the height of the layer(s) doesn't change the model, it only changes where the layer intersects the model. The (1st) layer is still reduced in height, but the next layer will start sooner. Setting the number of top/bottom layers to 0 should have worked, and works if I try to reproduce it here. Also you expect there to be walls on the 0th/1st layer as wel, even if there is Could yout attach the saved project (Save As, not Export) so we can see what's going on? Ypu might need to zip it to attach it here. Alter
  13. Cura (as a whole) is open source, the component that does the slicing is called CuraEngine, the relevant portion of the docs that explains this can be found here. This is only a very short exaplanation, and valid for the normal support, but we also have the experimental tree-support. Other slicers have different methods of generating support.
  14. @ultradryan If it's this issue, the upcoming 4.2 release will fix this.
  • Create New...