I too have the same problem.
Has been working perfectly fine, up until installing the newest Radeon Drivers V20.8.3 this morning.
Now it crashes as soon as I open an STL file.
I too have the same problem.
Has been working perfectly fine, up until installing the newest Radeon Drivers V20.8.3 this morning.
Now it crashes as soon as I open an STL file.
Does 4.6.2 work for you on the new drivers?
In my case i’m using standard intel integrated graphics and whatever driver Windows 10 installed for it.
Problems here as well, on a 4.7 clean install, worked ok for a few prints, then started crashing importing any stl I have, after changing a few small profile material settings and the theme.
Using NVidia drivers here, on x86 Win.
4.6.2 is fine and never had such an issue.
https://github.com/Ultimaker/Cura/issues/8230
https://github.com/Ultimaker/Cura/issues/8249
Check these bug reports for a work around.
Reading to the end of the comments in issue 8230, it says it's the same issue as 8249, which is that the config parser has been replaced and obviously not tested very well! I found this the moment I tried 4.7beta so how come no one else testing the beta version picked it up?
In my case, I used OctoLapse which requires having comments in the startup GCode like "; layer_height = {layer_height}" and Cura 4.7 crashes because there's an equals sign in the GCode (even though it's a comment!). So I currently have a choice of using Cura 4.7 or OctoLapse!
From reading the comments about the change, I gather it was done to speed up startup from 2.5 seconds to 1.2 seconds. My vote would be that this isn't important. I'm about to do a 3D print which is going to take hours and you think I care about an extra second or two to start the slicer? I'd be more impressed if the speed of the slicing could be improved.
So for a simple fix, can we have a version 4.7.1 with the old config parser or setting to switch between the two until someone can mend the new one?
Edited by StarNamerThanks all - this fix worked for me: https://github.com/Ultimaker/Cura/issues/8235#issuecomment-682036305
Easy enough to do and it works for me on Win and worked for a mate on Apple (there is no python35.zip
on Mac, but the FastConfigParser.py(c)
is in the install directory somewhere.)
On 8/28/2020 at 11:21 AM, StarNamer said:I found this the moment I tried 4.7beta so how come no one else testing the beta version picked it up?
No idea 😞 It's also why i'm so frustrated with this issue.
On 8/28/2020 at 11:21 AM, StarNamer said:From reading the comments about the change, I gather it was done to speed up startup from 2.5 seconds to 1.2 seconds. My vote would be that this isn't important. I'm about to do a 3D print which is going to take hours and you think I care about an extra second or two to start the slicer? I'd be more impressed if the speed of the slicing could be improved.
That's your opinion. Unfortunately, it's not something that a lot of people agree with. The startup time is one of the things in Cura that most people complain about. Also note that the improvement was on my machine, which isn't a good indication for everyone (my boot times are already much shorter than what a lot of people report).
On 8/28/2020 at 11:21 AM, StarNamer said:So for a simple fix, can we have a version 4.7.1 with the old config parser or setting to switch between the two until someone can mend the new one?
A patch version is on the way.
I also have been having this issue for the past two weeks. I did delete my profiles and it started working. Today when I opened it up, I'm not sure why it suddenly started again, but it is back.
Startup time is important, but not as important as it being able to open at all.
Thanks for doing what you do, but this WAS reported in the beta, and understandably people are frustrated that it made it to a standard release.
Keep up the good work. Waiting for a patch.
Just har this problem and googles this. even after removing the octolapse script from my printer machine settings I can’t load any stl files without crashing... which is strange 4.7 worked for a while before this crap started. and now I can’t fix the one file I need to fix.
Creating a new printer profile worked. which si weird, I copied the start script from a new profile into my old... so these two ar basically identical but one crashes.
I wish they warned people about this KNOWN bug so thatan Octolapse user would just wait.
Edited by sr13299 hours ago, sr1329 said:I wish they warned people about this KNOWN bug so thatan Octolapse user would just wait.
I wish we'd known this when releasing 4.7... Unfortunately we didn't, since apparantly no-one with octolapse tested the beta.
But no worries, a patch is underway.
So did 4.7.1 fix this?
On 9/7/2020 at 7:22 PM, nallath said:I wish we'd known this when releasing 4.7... Unfortunately we didn't, since apparantly no-one with octolapse tested the beta.
But no worries, a patch is underway.
I signed up just to say thank you so much. 4.7.1 fixed this for me. Much appreciated!
5 hours ago, vdhdesign said:I signed up just to say thank you so much. 4.7.1 fixed this for me. Much appreciated!
Glad to hear 🙂
I just want to say Thank you. My problem of stl opening crash got fixed by Cura 4.7.1.
Thank you.
I have a Creality Ender 3 Pro and usually use the Creality slicer. Two days ago, I wanted to print in PETG so loaded up Cura 4.6.x to make use of the PETG profile built in. I was promped to upgrade to 4.7.1, which I did.
I loaded a file and printed it twice. I later went to load the STL file again and Cura Crashed. I did a little research and discovered this was a problem with 4.7, so I installed 4.6 again, which also wouldn't work. I then decided to use Creality slicer, and it also wouldn't work.
I monkeyed around for 2 days without any kind of success. I then ACCIDENTALLY discovered that Cura would load STL files which were located in other folders. It just wouldn't work from the downloads folder, which is where files from Thingiverse go by default.
I now have Cura 4.7 installed again, and working well, as long as I don't try to load an STL from the downloads folder.
Hopefully, somebody else will benefit from this discovery.
Edited by prescove
--SOLVED--
I had the 4.7 installed and had been working fine.
As of lately, Cura popped up a dialog to upgrade to 4.9 and I took the bait ..LOL
Installation went through smoothly, but once the UI is loaded and I try loading an object it crashes by sending multiple instances of dialog box with some errors in it.I clicked Send Report, then the error disappear, along with the UI, as if I had quit Cura.
Here's how I got it to work again -- an older version 4.8
https://brewinstall.org/install-ultimaker-cura-mac-osx/
Before you do that, go to Applications folder (Mac OS Catalina) and rename Ultimaker Cura to a different name, just in case you need to revert.
Install Cura by following the link above. It is done through the Terminal. Just copy paste the commands. There are only two commands to run. If one of them seems like several lines, they're actually a single command.
First command:
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" < /dev/null 2> /dev/null ; brew install caskroom/cask/brew-cask 2> /dev/null
Wait till it finishes downloading. At times it seems like not doing anything be patient and wait for the terminal prompt comes back, at which time there will be some text saying "...successful".
Then run the next command:
brew install --cask ultimaker-cura
Again wait for a success text.
Hopefully this works as a quick fix for those experiencing the same problem as mine.
Voila! Cura is working again, although it's not version 4.9. It's 4.8. I'll take it.
Recommended Posts
sr1329 3
Seriously same problem. I was stupid enough to delete all my “userdata” files to see if that was the problem.
I ended up recreating my profiles from scratch and it doesn’t work. So I had to go back to 4.6.2 and recreate my profiles there again.
I have both installed on the system as installing 4.6.2 doesn’t ask to remove a higher numbered version. I may as well remove 4.7 and keep using 4.6.2.
It crashes only upon opening an STL file. Windows is latest release version of 10. I believe version 2003 or whatever the May update was.
It happens with all files I’ve tried so it’s not the file. I can open and slice in 4.6.2. There is some output for the error it seemed to reference profiles. And someone mentioned deleting the Cura folder under your userdata worked in this situation on some other version of Cura.
Edited by sr1329Link to post
Share on other sites