Jump to content
Ultimaker Community of 3D Printing Experts
melbo

Cura 2.4 and Cura 2.5 Beta slow?

Recommended Posts

Hi community,

Not sure if someone else experience the same but Cura 2.4 and Cura 2.5 Beta are super slow on my MacBook Pro 2.2 GHz, 16GB. CPU almost 100% all the time. Any thoughts about it? Would really appreciate it. I used other slicing software before and none of them where so CPU intense like this one.

Best,

Mel

5a3333fbd552d_ScreenShot2017-04-05at2_10_03PM.png.dff666d24e60e6470dec16d8b15a4281.png

Share this post


Link to post
Share on other sites

Slicing is multi threaded these days. This means that it will use more resources if there are any.

If you don't want Cura to use that much resources, disable auto slicing. If more people feel this way, we could also add a force single threaded option, but that would significantly increase slicing time (~ 2x as slow)

Share this post


Link to post
Share on other sites

Ive found Cura to work really really slow on desktop imac (16GB ram, latest os), it works a bit better on my macbook pro (also 16GB ram)....

turning off auto slice does help, but really on the imac its pretty much unusable.

S3D is a good alternative slicing software if your on the look-out, it costs $150, but if your going to be doing alot of printing I think it's worth investing in.

Share this post


Link to post
Share on other sites

Slicing is multi threaded these days. This means that it will use more resources if there are any.

If you don't want Cura to use that much resources, disable auto slicing. If more people feel this way, we could also add a force single threaded option, but that would significantly increase slicing time (~ 2x as slow)

Perhaps the "force single threaded option" as you have suggested, isn't a bad idea. It appears that multi threading has introduced other anomalies into the slicing process, such as not knowing where Cura knows where it left off on the previous layer

From a previous post in April by bagel-orb:

Cura 2.5 definitely handles positioning differently from 2.4. Since Cura 2.5, CuraEngine is using multi-threading to speed up the process. The engine generates multiple layers at the same time. The major disadvantage of this is that the engine doesn't know where the previous layer ended in order to get the point on the inner walls closest to the previous print head location. Instead the engine starts each layer closest to the Layer Start Location.

In addition, I've also experience some strange behavior with support placement in 2.5. Placing support where it is not needed. That's why I continue to use 2.4 for daily production work on my UM3 machines.

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

  • Our picks

    • Taking Advantage of DfAM
      This is a statement that’s often made about AM/3DP. I'll focus on the way DfAM can take advantage of some of the unique capabilities that AM and 3DP have to offer. I personally think that the use of AM/3DP for light-weighting is one of it’s most exciting possibilities and one that could play a key part in the sustainability of design and manufacturing in the future.
        • Like
      • 3 replies
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!