DaHai8

I'm unable to get this image out of my head... And now, you won't be able to either!

Wish Granted: How to Prevent Windows from Automatically Updating Specific Drivers Caveat: Only works on Windows 10 Pro or Enterprise

And a very good thought. Happens to me too, but I made sure the drivers were AMD/NVidia/Intel. Just doesn't make sense... I mean, what kind of video card does Cura need?? My laptop has a someone new and beefy card, and it struggles on that... and it's a Core i7!! If I'm going to spring for a more powerful video card, I may as well take that money and buy Simplify3D! I just can't deal with it anymore, and I don't know what else to try... and I haven't heard anything from Ultimaker... But newest is not always better. We've all seen M$ upgrades brick PCs. I downgrade my video drivers to get them to perform properly. And its not just Cura that runs slow with the newest (bad) video drivers: Sketchup, Slic3r, and others.

Every time M$ sends out an Update, like the one that came out last week (KB4041676/ KB4041691) , its screws up my video drivers and I have to re-install them with versions I downloaded from the manufacturer. Happened with Windows update last week, Cura slowed to a crawl, then I reinstalled the original video drivers and everything's back to normal speed....just saying that's what happens to me...

If 100% is working correctly and filling 100%, but any lower infill looks sparse or stringy, then you may have your print speed set too high. If its like S3D, then 100% infill speed is printed at Top/Bottom speed, whereas lower infill percentages are printed at full speed. And for TPU, that may be too fast. So try lowering the infill speed to your top/bottom speed. Just a WAG.

Will this be Cura 2 v3.0 or Cura 3.0 or Cura 3 v1.0? I remember back when Cura 2.0 came out the reason for the version reset was that it was 'Cura 2' whereas Cura 15.x was 'Cura 1' or Original Cura. So is Cura 3 a whole new rewrite, like Cura 2 was, or a progression of versions? What happens when you run into the same version numbers as with Original Cura (in 9 years)? Maybe call it something different so you don't confuse simple minds like mine with these new old version numbers: CurAtion, perhaps

Perhaps there is an open source STL validator that could be integrated into Cura?

Cura knows, without having to click on 'X-Ray' mode, that the model has issues. Cura also know that less than X% of the model actually touches the build plate - or that a majority of the model's 'base' is actually a fraction of a millimeter above the build plate. Because the skirt or brim actually passes under most of the model. I think Cura can also tell of a model contains many connected surfaces that can adversely effect the print. Give all this, and the regular flow of questions on this board relating to Odd Brim Placement, Supports for the Entire First Layer, Closing Holes, Infill Where There is Nothing, etc., would it be possible to pre-detect these issue and pop up a windows that says something like "Model is Possibly Crap, please check it for errors before slicing/printing" - Ok, maybe not exactly those words But it would sure help preemptively catch a lot of repeating posts here where the STL file is, well, shall we say "Not valid". Just a thought...

There's Experimental->Hollow Out Object, Experimental->Enable Conical Supports, Special->Drop Down Support Mesh. Not sure what exactly they all do, but they sound promissing!

Another option is to edit it with Meshmixer and have it actually hollow out the object, then when you bring it into Cura and Support->Everywhere, it will put internal supports in the pumpkin. Maker's Muse has a nice video on how to hollow out an object in MeshMixer:

Ok, the pumpkin stl file is not hollow. You set infill to zero (?) so Cura still sees it as a solid object and won't put support inside a solid. There are some Experimental settings in Cura that might help, as well as possibly placing a pillar stl file inside as a manual support - but I have no experience with either of those areas. Maybe someone else who's more familiar with those particular Cura settings can help.

That is odd, it should have generated internal supports. Maybe a bug in Cura or an issue with the stl file. Is the stl file available somewhere to download and examine? Like thingiverse...?

Did you try Support -> Support Placement -> Everywhere ? That will add support inside and outside your model, basically 'Everywhere' it is needed.

Not sure what program you used to create your object, but it may be that it's not a solid manifold. Have you looked at it in x-ray mode to see if there are any red areas? Those indicate problems with the model that the slider will choke on. There are some online apps, like MakePrintable, that can check your stl file for errors. That's all I got. Hope it helps.

Did you wait until both extruders were at room temperature before doing the PID tune on each one? They are both right next to each other, and share the same cooling block. Running a PID tune on one would probably transfer some heat over to the other if it was still warm/hot. So if you didn't wait until both hot-ends where are room temperature before doing the PID tune, you'd probably get different results due to heat carry-over from the other. Otherwise, maybe check with E3D - could be different heater cores or thermistors in each hot-end.

Did you try the Image Gallery button? Its the next to the last button on you edit window. Click on it, then click on "Upload Image". Drag-n-Drop your image into that window and then click on Add. Its pretty straight-forward and doesn't require the blood of your first born or anything like that. 'Cause otherwise, I'm at a loss as your what you're trying to describe. Sorry.

I still say is your video drivers

Video drivers. I had the same problem on my laptop. Windows kept 'updating' my video drivers to a version that just sucked for graphical updates. Slic3r, Sketchup, Cura, all slowed to a dead crawl. I have Intel HD 4000 graphics chip and downloaded the two most recent driver updates from the Intel web site. Whenever M$ mucks with my Video Drivers, I just run either one (or both) to reload the good drivers and my PC screen updates go back to normal.

I've been a developer for 30+ years, and rarely its the programmers who are pushing out new releases - especially at Cura's feverish pace. Perhaps upper management needs to made aware the damage being done to Ultimaker's reputation having so many releases back-to-back with continuous bugs. Its just not that feverish with other slicers: Slic3r - 2+ years Simplify3D - ~1 year between releases Crap(ft)ware - 2+ years... So, my 2c: Push back to management to slow down. 1-2 stable release per year. One team working on bug fixes for each release, and the other team working on enhancements for the next release while incorporating the bug fixes of the previous one. There is no way any Q&A team can sufficiently test Cura against all the current 3D Printers on the market. That's where the community comes in and bug-fixes for stable builds over time. There is just not enough time to do all that when new versions are pushed out every 2-3 months - or quicker.

Just a WAG here, but since the print origin is at the corner of the print bed (unless you're using a Delta printer), and the rotation matrix is rotating about the origin, then haven't you just rotated it off the print bed? Try changing your rotation matrix to rotate about the center point of your object.

My trick for printing with PETG is to print the first layer at the top-end of the temperature range listed for the filament. In my case, its 240c. This makes it flow like hot honey so its doesn't get pulled around on travel moves. It also sticks better to the build plate (PrintBite, in my case). After the first layer, I reduce the Nozzle Temp to my normal setting for PETG (220c)

Usually means you need another closing curly brace } somewhere in the json - either at the end or further up. I think its your "overrides" group that is not closed at the end.

Same as your previous post on Stepper Motor startups: Sounds like a bug in Marlin 1.1 - especially if it didn't happen with the older release. You could try upgrading again to the latest release: 1.1.4 Also check on the Marlin Firmware Forum if its been reported as an issue: http://forums.reprap.org/list.php?415

Sounds like a bug in Marlin 1.1 - especially if it didn't happen with the older release. You could try upgrading again to the latest release: 1.1.4 Also check on the Marlin Firmware Forum if its been reported as an issue: http://forums.reprap.org/list.php?415

Install the "Solid Inspector" plugin from the Sketchup Warehouse. It is very good (not perfect) at catching errors in your model that would keep it from printing properly.