Jump to content
Ultimaker Community of 3D Printing Experts


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

Recent Profile Visitors

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

  1. Having had my issue with Cura not supporting really small items fixed by burtoogle pointing me to a setting I never knew existed before, I wonder if another long standing issue can similarly be fixed here. I've always had far more stringing from supports than from the actual model, with blobbing & stringing on the model surfaces nearest. It gets really annoying when a print would be perfectly printed if it wasn't for the support. I know about 'Limit Support Retractions' and turned that off long ago, and avoiding printed parts & supports when travelling, but does any other setting spec
  2. Excellent! Thank you, a setting I never knew existed, it certainly looks good in preview. I'll test it tomorrow.
  3. I realise I'm probably the only one here who even tries to print really tiny tanks (1:600, under 1cm long), but it worked fine up until Cura 4.0.0. After that, there was a strange failure in the slicer trying to use supports. The support went so far, then just stopped, often at a demarcation line, like the bottom of the turret.. Now, this only seems to happen on really small models, but it did not happen on 4.0.0 and before slices. Is there some setting I'm not using that affects this? Has anyone else seen the effect? It will work if I use tree Supports, but Tree Supports just don't support s
  4. OK, seems like it needs: Compatibility Mode for Windows 8 DO NOT Run as Admin Double click on an STL, DO NOT attempt to open the program itself Ensure minimal disk activity in Task Manager before starting.
  5. I have found it will only start if my computer is displaying minimal activity in Task Manager, specifically minimal disk activity. That may be specific to my machine.
  6. I fixed one of my own issues at least - it didn't allow me to drag & drop files into 4.0.0 after reinstalling because somehow it had been set to Compatibility mode. Also UAC no longer asks for confirmation every time I open it. Still can't run 4.3.0 though.
  7. I had the same issue installing 4.3.0. Previously I had 4.0.0 and 4.2.1 installed, with 4.0.0 as default. It worked fine, 4.2.1 had issues with support. After installing 4.3.0, not only would that not start (Task Manager shows it sitting dormant in memory), but 4.0.0 won't start either. After scouring my PC clean of everything to do with Cura of any version, I have reinstalled 4.0.0 and now that works - except I can't drag and drop files into it! Cura seems to be the default for the relevant files, 4.0.0 is the only Cura installed, and drag & drop works for all other programs,
  8. I've been looking at the Preview window, and I see one interesting thing - there's no gap between the outer & first inner wall, but if there's a second inner wall (I usually have 3 walls) then the profile shows a visible line. This is a different turret, by the way...
  9. On examining Cura's Preview, \I believe the issue arises when Inner Wall layers are visible on the outer surface.
  10. For as long as I've been printing on my Ender 3 Pro, I've used some version of Cura, & I've had a problem with visible gaps between lines, either where the top edge of the wall is visible, or on small details on a surface.I can see the layers of the walls or details against one another, and, occasionally, thin gaps. These aren't just visible, they have depth - albeit tiny gaps with tiny depth, they're visible through coats of paint & I have to fill them with putty. Bear in mind I primarily print wargaming miniatures, like tanks, and my prints, regardless of my own worries, have been co
  11. Thanks, but I have discovered I can have both 4.0 and 4.1 on my PC at the same time - if I click on a file to open it it'll always open in 4.1, but if I need 4.0 I can open that first. That'll do nicely until 4.2 appears.
  12. Thanks, I'll just stick with 4.0 until then.
  13. Is it worth going back to 4.0 or is 4.2 imminent? EDIT - it does indeed work in 4.0...
  • Create New...