UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
I just had the same issue. Because you mentioned about Cura 2.6.2, I was able to find a workaround for my problem. Hope this helps you as well, if you haven't already figured it out.
This happens only for the 'custom printer' profile. If you select any of the existing machines included in the software, you won't get this error. I tried changing the 'machine settings' of my new custom machine, but no luck.
But the custom machines which I had added a long time ago in the previous versions of Cura (which then were automatically migrated to the newer version when I installed one) were still working fine. I was using Cura 3.0, I tried Cura 2.7 but got same error.
Then I downloaded Cura 2.6.2 and it worked fine!
So the workaround is, create your custom machine profile in Cura 2.6.2 and then install the latest version. The new version will automatically import the profiles from 2.6.2 and they work perfectly fine with all the latest features!
But this is just a workaround and I hope the Cura team fixes this issue. Can't keep uninstalling newer version simply to add a machine profile and then install the new version again.
Sid.
1
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!
🚀 Help Shape the Future of Cura and Digital Factory – Join Our Power User Research Program!
We’re looking for active users of Cura and Digital Factory — across professional and educational use cases — to help us improve the next generation of our tools.
Our Power User Research Program kicks off with a quick 15-minute interview to learn about your setup and workflows. If selected, you’ll be invited into a small group of users who get early access to features and help us shape the future of 3D printing software.
🧪 What to Expect:
A short 15-minute kickoff interview to help us get to know you If selected, bi-monthly research sessions (15–30 minutes) where we’ll test features, review workflows, or gather feedback Occasional invites to try out early prototypes or vote on upcoming improvements
🎁 What You’ll Get:
Selected participants receive a free 1-year Studio or Classroom license Early access to new features and tools A direct voice in what we build next
👉 Interested? Please fill out this quick form
Your feedback helps us make Cura Cloud more powerful, more intuitive, and more aligned with how you actually print and manage your workflow.
Thanks for being part of the community,
The full stable release of Cura 5.10 has arrived, and it brings support for the new Ultimaker S8, as well as new materials and profiles for previously supported UltiMaker printers. Additionally, you can now control your models in Cura using a 3D SpaceMouse and more!
Recommended Posts
sidnaique 2
I just had the same issue. Because you mentioned about Cura 2.6.2, I was able to find a workaround for my problem. Hope this helps you as well, if you haven't already figured it out.
This happens only for the 'custom printer' profile. If you select any of the existing machines included in the software, you won't get this error. I tried changing the 'machine settings' of my new custom machine, but no luck.
But the custom machines which I had added a long time ago in the previous versions of Cura (which then were automatically migrated to the newer version when I installed one) were still working fine. I was using Cura 3.0, I tried Cura 2.7 but got same error.
Then I downloaded Cura 2.6.2 and it worked fine!
So the workaround is, create your custom machine profile in Cura 2.6.2 and then install the latest version. The new version will automatically import the profiles from 2.6.2 and they work perfectly fine with all the latest features!
But this is just a workaround and I hope the Cura team fixes this issue. Can't keep uninstalling newer version simply to add a machine profile and then install the new version again.
Sid.
Link to post
Share on other sites