Msuurmond

Can you share you log files so we can investigate?

Strange, I have the same setup (MacOS Sierra 10.12.4) and experience no problems. Maybe you could try to remove your config folder (back it up first) it is in ~/Library/Application Support/cura

Do you have custom profiles? If not you could try to clean your config (remove ~/Library/Application Support/cura) and see if that helps.

Running Cura 2.5.0 on Sierra without any problems.

Hi Per, I don't know what happened to your .gcode, but we are currently building different config folders for Cura versions. So from the next Beta (which will be public in a few weeks) you can run different versions beside each other and they won't have interacting configurations.

You just made my Monday a lot better, thank you!!

Could you try with 2.5 final?

Aha, thanks for the link. Maybe you can ask your IT department to whitelist Cura.exe?

We know the Baidu virusscanner gives a false positive on Cura 2.5, but Webroot seems to not find anything: https://www.virustotal.com/en/file/b64ede0e1dd24aaa17cf444ed18d5027cad3db69dd286e65c3a585e96659d749/analysis/1492763796/

1. Try to disable your virusscanner (temporarily!) while installing Cura. 2. Could you try to (re)install Microsofts Visual C++ 2015 ? https://www.microsoft.com/en-us/download/details.aspx?id=53840

Can you post/do you have some log files? On windows you can find them here: \AppData\Local\cura\ and then the file cura.log

This morning we released the 2.5 final version. (download here) I would like to thank you all for testing the 2.5-beta and giving feedback on what you liked and what you would like to see in upcoming versions. I have aggregated all input and some requests will certainly make it to the new version. The Cura team did an amazing job on building new features, squashing all bugs and working together with me We are already building the new 2.6 version and hope to start that beta in some weeks. Keep watching these forums to see when that happens!

Hi, I also had this with the first beta and it was because when printing through WiFi not all the gcode was correctly send to the printer. After we fixed this (in beta-2) it worked ok. Could you try our latest beta?

Looks like you found a bug, thx! We are going to fix it before releasing 2.5 final.

Could you try with the latest beta (2.5.0-BETA-2) ?

Thanks for your effort to try our BETA, I'll ask the team to look into this tomorrow.

We are currently working on a 'Pause auto slice' button for the next release.