hehe didnt see that post.. same here
Thankfully Apple and MacOS are super helpful here (NOT!).
What can be happening, and I have no idea why, is that previous versions of Cura are still on your Mac system and those are causing problems. People have reported solving this issue by removing previous installs. I have NO clue why that works, and how Apple managed to make a OS so fucked up that different installations of an application mess each-other up.
(Between Windows, Linux and MacOS. MacOS is the most hostile enviroment I ever programmed on. It really feels like random shit goes wrong on random machines for random reasons)
I've build 13.06.4 the same way as all the previous 13.06.X versions, so why the new version would suddenly crash, I have no clue...
Interesting. I tried removing all of the last Cura including prefs and settings manually since there is no uninstaller but still didn't work.
I reverted to the previous version for now though.
Glad I'm not a programmer sounds very frustrating!
.5 is out and runs.. im testing right now.
As far as I know the .5 version fixes the "Cura error" problem.
It can be downloaded from http://software.ultimaker.com/
The root cause seems to be some conflict in a system update I applied from Apple and a library I used to package Cura, causing the final "Cura error" if you ran it on a different system.
I had the same problem on windows when I removed: G1 F{travel_speed}
from start.gcode. Put it back and everything works fine.
EDIT: Sorry, wrong thread, the right one had a problem with Cura not preparing files, threads were one on top of the other heh...
Recommended Posts
mostlyatomicbob 34
Yup same here. Using 10.8.4, Macbook air.
I get exactly the same error message
Bob
Link to post
Share on other sites