Jump to content
maht

Cura 4.6 beta period begins today

Recommended Posts

Posted · Cura 4.6 beta period begins today

UMS3_Highspeed-vehicle-heatcam-mount-transparent-support-layer.thumb.jpg.24092f7b76e8b4358a61b588bae2a75a.jpg

Transparent support in Cura 4.6

 

THANK YOU to all Ultimaker Cura users helping in the fight against COVID-19 – with 3D printing, volunteering, or just by staying home.

Want to get involved? Find out more.

 

Get an early preview of Ultimaker Cura 4.6. The stable release is slated for late April. We've released on a Friday this time around because we noticed usage seems to spike over the weekend. 

 

As usual, a special mention goes out to smartavionics and fieldofview for their significant contributions. Last week we hit a milestone of 3 million slices per day. Jobs sent to Ultimaker printers are up 27%, and cloud prints coming from Cura are up 26.5%. We also closed 19 pull requests in last 7 days. 

 

Here are some noteworthy features and fixes in this release: 

 

New Intent profiles. In version 4.4 we introduced Intent profiles for the Ultimaker S3 and Ultimaker S5 which allow you to start prints at the click of a button without a lot of configuration steps. Due to popular demand, version 4.6 expands the range of Engineering Intent profiles to include more of the Ultimaker material portfolio: PC, Nylon, CPE, and CPE+. These work with 0.4 print cores. 

 

Various crashes captured by Sentry. We recently adopted Sentry as our new crash logging system, and this has enabled us to catch and resolve various crashes for a more stable product.  

 

Infill mesh ordering. When you have three objects overlapping each other and you set two of them to "Modify settings for infill of other models", then the setting "Infill Mesh Order" determines which of the two infill meshes gets priority where they overlap. This was broken for cutting meshes, so BagelOrb contributed a fix. 

 

Print monitor preheat fields. When connected via serial or using Octoprint, values in the print monitor preheat fields were broken in previous versions. They have now been fixed by fieldOfview

 

Stepper motor disarming during pause at height. Some printers automatically disable their steppers after a pause (after a certain time). This script makes it possible to set that in the pause script (instead of relying on default behaviour of the firmware). 

 

Updated installer. Small fixes have been made to the installer. To keep up with the times, we’ve also updated the images to display an Ultimaker S3 instead of an Ultimaker 3. 

 

Third party printers merged in this release:

 

Flying Bear printers. oducceu has contributed a machine definition for the Flying Bear Ghost 4S Printer. 

 

Magicfirm printers. jeffkyjin has contributed machine definitions for MBot Grid II+, MBot Grid II+ (dual), MBot Grid IV+ and MBot Grid IV+ (dual). 

 

HMS434. Updates to the HMS434 machine definition have been contributed by maukcc

 

FabX Pro. hussainsail2002 has contributed machine definitions for FabX Pro and print profiles for REDD materials. 

 

Want to add a third-party machine definition to Ultimaker Cura? Here’s how.  

Disclaimer: Third-party machine definitions are accepted as contributed, and will not be tested or maintained in any way by the Cura development team. Make sure anything submitted to us is thoroughly tested.

 

See the full release notes for more info. This time we’ve included links to relevant issue reports and pull requests that created each new feature, so you can dive right in and see each individual commit if you're into that kind of thing.

 

...or just download now.

 

Some notable new additions to the Marketplace:

 

ThingiBrowser 2.0.0 by Chris ter Beke allows you to download objects from Thingiverse directly into Cura. It now also supports MyMiniFactory. 

Material Cost Tools by fieldOfview allows you to export and import material cost and weight data into a CSV format, for easy sharing. 

 

More plugin updates will filter through as we approach the stable release. Any issues you experience with a plugin in Cura should be reported to the plugin author. 

 
As always, any issues you experience with Cura itself should be reported on GitHub, being very careful to follow the issue template that we have set up that gives us all the info we need to help you. 

 

Take care everyone, and stay safe. 

  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...