Jump to content
Ultimaker Community of 3D Printing Experts
Crow

Cura 3.1.0. Crashing

Recommended Posts

What kind of forum requires moderator review for every single post? Ridiculous.

Anyway, I guess it's a toss-up as to whether this reply or my actual post about the same problem shows up first, but...it doesn't work for me either. Splash screen shows up, gets to "loading interface", and then disappears and Cura doesn't run. Never happened to me with any other version.

Share this post


Link to post
Share on other sites

How about previous versions of Cura? Do they still work, or is it just Cura 3.1?

What do the logs (stderr.log and stdout.log) say in %LOCALAPPDATA%\cura ?

I contacted MS support. They told me to run as administrator. They said that some of the apps have not caught up with the updates yet.

Share this post


Link to post
Share on other sites

What kind of forum requires moderator review for every single post? Ridiculous.

It's only the first post. You are approved now so post away. We get a LOT of spammers. Some times 400 spams in one day.

Share this post


Link to post
Share on other sites

What kind of forum requires moderator review for every single post? Ridiculous.

It's only the first post.  You are approved now so post away.  We get a LOT of spammers.  Some times 400 spams in one day.

Apologies for the overreaction. I swear I'm here for/to help! ;)

(edit) I just tried to run 3.1.0 again. On my end of things, both stderr.log and stdout.log are blank, 0KB files. Running as admin had no effect. My existing install of 3.0.4 is running like a champ though, no problems at all.

Edited by Guest

Share this post


Link to post
Share on other sites

ok... 5 min ago installed and have the same issue - on my desktop pc as well on my office notebook.

It shows the splash screen and then disappears/crashes when writing setting up scene"

==EDIT:==

... SORRY, forget it...

@Crow,

There is a NOTE at the official release info (https://ultimaker.com/en/blog/52266-whats-new-in-ultimaker-cura-31) adressing this issue:

Upgrading from Ultimaker Cura 3.1 beta to Ultimaker Cura 3.1 stable may require manual removal of the user config file (located in the Ultimaker Cura 3.1 subdirectory). This fixes an issue with a wrong profile being generated and not being overwritten.

Edited by Guest

Share this post


Link to post
Share on other sites

ok... 5 min ago installed and have the same issue - on my desktop pc as well on my office notebook.

It shows the splash screen and then disappears/crashes when writing setting up scene"

==EDIT:==

... SORRY, forget it...

@Crow,

There is a NOTE at the official release info (https://ultimaker.com/en/blog/52266-whats-new-in-ultimaker-cura-31) adressing this issue:

Upgrading from Ultimaker Cura 3.1 beta to Ultimaker Cura 3.1 stable may require manual removal of the user config file (located in the Ultimaker Cura 3.1 subdirectory). This fixes an issue with a wrong profile being generated and not being overwritten.

 

Correct. Try right clicking on the app icon and running as admin.

Share this post


Link to post
Share on other sites

 

ok... 5 min ago installed and have the same issue - on my desktop pc as well on my office notebook.

It shows the splash screen and then disappears/crashes when writing setting up scene"

==EDIT:==

... SORRY, forget it...

@Crow,

There is a NOTE at the official release info (https://ultimaker.com/en/blog/52266-whats-new-in-ultimaker-cura-31) adressing this issue:

Upgrading from Ultimaker Cura 3.1 beta to Ultimaker Cura 3.1 stable may require manual removal of the user config file (located in the Ultimaker Cura 3.1 subdirectory). This fixes an issue with a wrong profile being generated and not being overwritten.

 

Correct. Try right clicking on the app icon and running as admin.

 

Sorry hit reply too soon..

I loaded 3.1 but did not remove config file.

Share this post


Link to post
Share on other sites

 

I doubt running as admin will fix anything, but let us know if it works for you.

 

It works.

 

It doesn't work for me, unfortunately. Also never had the beta installed, I generally only use the release versions, so no wayward profiles for me to delete. The program simply doesn't run, and doesn't leave anything in any of the log files to tell me what's going on.

Share this post


Link to post
Share on other sites

Same issue -- crash on splash screen upon reaching "Setting up scene" running both as user and administrator. Below is the freshest stderr.log I have with a new (re)install after manually clearing out every 3.1 folder/file/reg entry I could find. (FYI: never ran 3.1 beta; had the drive X crash/hang issue with 3.0 which was solved by remapping the device's drive letter from "X" ). Hope this helps.

 

2017-12-24 02:05:07,420 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin ConsoleLogger
2017-12-24 02:05:07,479 - INFO - CuraEngineBackend.CuraEngineBackend.__init__ [64]: Found CuraEngine at: C:\Program Files\Ultimaker Cura 3.1\CuraEngine.exe
2017-12-24 02:05:07,481 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin CuraEngineBackend
2017-12-24 02:05:07,491 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin CuraProfileReader
2017-12-24 02:05:07,506 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin CuraProfileWriter
2017-12-24 02:05:07,517 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin OBJReader
2017-12-24 02:05:07,531 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin OBJWriter
2017-12-24 02:05:07,555 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin STLReader
2017-12-24 02:05:07,582 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin STLWriter
2017-12-24 02:05:07,604 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin FileLogger
2017-12-24 02:05:07,666 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin FirmwareUpdateChecker
2017-12-24 02:05:07,679 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin GCodeProfileReader
2017-12-24 02:05:07,707 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin GCodeReader
2017-12-24 02:05:07,729 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin GCodeWriter
2017-12-24 02:05:07,754 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin ImageReader
2017-12-24 02:05:07,780 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin LegacyProfileReader
2017-12-24 02:05:07,814 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin LocalFileOutputDevice
2017-12-24 02:05:07,842 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin MachineSettingsAction
2017-12-24 02:05:07,942 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin OctoPrintPlugin
2017-12-24 02:05:07,972 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin PerObjectSettingsTool
2017-12-24 02:05:07,998 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin PluginBrowser
2017-12-24 02:05:08,012 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin PostProcessingPlugin
2017-12-24 02:05:08,046 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin RemovableDriveOutputDevice
2017-12-24 02:05:08,124 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin SimulationView
2017-12-24 02:05:08,145 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin SliceInfoPlugin
2017-12-24 02:05:08,192 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin SolidView
2017-12-24 02:05:08,210 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin CameraTool
2017-12-24 02:05:08,262 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin MirrorTool
2017-12-24 02:05:08,292 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin RotateTool
2017-12-24 02:05:08,332 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin ScaleTool
2017-12-24 02:05:08,347 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin SelectionTool
2017-12-24 02:05:08,409 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin TranslateTool
2017-12-24 02:05:08,452 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin UltimakerMachineActions
2017-12-24 02:05:08,553 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin UM3NetworkPrinting
2017-12-24 02:05:08,598 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin UpdateChecker
2017-12-24 02:05:08,663 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin USBPrinting
2017-12-24 02:05:08,678 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin UserAgreementPlugin
2017-12-24 02:05:08,738 - DEBUG - UM.PluginRegistry.loadPlugin [206]: Plugin VersionUpgrade21to22 was disabled
2017-12-24 02:05:08,777 - DEBUG - UM.PluginRegistry.loadPlugin [206]: Plugin VersionUpgrade22to24 was disabled
2017-12-24 02:05:08,807 - DEBUG - UM.PluginRegistry.loadPlugin [206]: Plugin VersionUpgrade25to26 was disabled
2017-12-24 02:05:08,842 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin VersionUpgrade26to27
2017-12-24 02:05:08,861 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin VersionUpgrade27to30
2017-12-24 02:05:08,883 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin VersionUpgrade30to31
2017-12-24 02:05:08,911 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin SimpleView
2017-12-24 02:05:08,961 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin X3DReader
2017-12-24 02:05:09,000 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin XmlMaterialProfile
2017-12-24 02:05:09,037 - INFO - UM.PluginRegistry.loadPlugin [238]: Loaded plugin XRayView
2017-12-24 02:05:09,051 - INFO - UM.VersionUpgradeManager.upgrade [112]: Looking for old configuration files to upgrade.
2017-12-24 02:05:12,949 - DEBUG - UM.Backend.Backend._onSocketError [200]: Socket was unable to bind to port, increasing port number to 49675
2017-12-24 02:05:12,950 - DEBUG - UM.Backend.Backend._createSocket [214]: Previous socket existed. Closing that first.
2017-12-24 02:05:12,961 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [232]: Attempting to kill the engine process
2017-12-24 02:05:12,962 - DEBUG - UM.Backend.Backend._createSocket [214]: Previous socket existed. Closing that first.
2017-12-24 02:05:13,082 - DEBUG - UM.Backend.Backend._logSocketState [174]: Socket state changed to Listening
2017-12-24 02:05:13,137 - INFO - UM.Backend.Backend.startEngine [75]: Started engine process: C:\Program Files\Ultimaker Cura 3.1\CuraEngine.exe
2017-12-24 02:05:13,139 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] Calling engine with: ['C:\\Program Files\\Ultimaker Cura 3.1\\CuraEngine.exe', 'connect', '127.0.0.1:49675', '-j', 'C:\\Program Files\\Ultimaker Cura 3.1\\resources\\definitions\\fdmprinter.def.json', '']
2017-12-24 02:05:13,191 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] 
2017-12-24 02:05:13,194 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] Cura_SteamEngine version DEV
2017-12-24 02:05:13,205 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] Copyright (C) 2017 Ultimaker
2017-12-24 02:05:13,211 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] 
2017-12-24 02:05:13,212 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] This program is free software: you can redistribute it and/or modify
2017-12-24 02:05:13,213 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] it under the terms of the GNU Affero General Public License as published by
2017-12-24 02:05:13,215 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] the Free Software Foundation, either version 3 of the License, or
2017-12-24 02:05:13,216 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] (at your option) any later version.
2017-12-24 02:05:13,217 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] 
2017-12-24 02:05:13,219 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] This program is distributed in the hope that it will be useful,
2017-12-24 02:05:13,223 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] but WITHOUT ANY WARRANTY; without even the implied warranty of
2017-12-24 02:05:13,224 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
2017-12-24 02:05:13,225 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] GNU Affero General Public License for more details.
2017-12-24 02:05:13,226 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] 
2017-12-24 02:05:13,228 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] You should have received a copy of the GNU Affero General Public License
2017-12-24 02:05:13,229 - DEBUG - UM.Backend.Backend._backendLog [93]: [Backend] along with this program.  If not, see <http://www.gnu.org/licenses/>.
2017-12-24 02:05:13,261 - DEBUG - UM.Backend.Backend._logSocketState [178]: Socket state changed to Connected
2017-12-24 02:05:13,263 - DEBUG - UM.Backend.Backend._onSocketStateChanged [168]: Backend connected on port 49675
2017-12-24 02:05:18,664 - WARNING - cura.Settings.CuraContainerRegistry.addContainer [57]: Instance container Select Mini_variant is outdated. Its setting version is 0 but it should be 4.
2017-12-24 02:05:22,425 - DEBUG - UM.Settings.ContainerRegistry.load [231]: Loading data into container registry took 9.164202690124512 seconds
2017-12-24 02:05:22,768 - DEBUG - UM.Controller.setActiveView [86]: Setting active view to SolidView
2017-12-24 02:05:22,949 - CRITICAL - cura.CrashHandler.__init__ [62]: An uncaught exception has occurred!
2017-12-24 02:05:22,951 - CRITICAL - cura.CrashHandler.__init__ [65]: Traceback (most recent call last):
2017-12-24 02:05:22,952 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "<frozen importlib._bootstrap>", line 969, in _find_and_load
2017-12-24 02:05:22,953 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
2017-12-24 02:05:22,955 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "<frozen importlib._bootstrap>", line 664, in _load_unlocked
2017-12-24 02:05:22,956 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "<frozen importlib._bootstrap>", line 634, in _load_backward_compatible
2017-12-24 02:05:22,957 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "__startup__.py", line 12, in <module>
2017-12-24 02:05:22,958 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "<frozen importlib._bootstrap>", line 969, in _find_and_load
2017-12-24 02:05:22,960 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
2017-12-24 02:05:22,961 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "<frozen importlib._bootstrap>", line 664, in _load_unlocked
2017-12-24 02:05:22,962 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "<frozen importlib._bootstrap>", line 634, in _load_backward_compatible
2017-12-24 02:05:22,963 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "Console.py", line 24, in <module>
2017-12-24 02:05:22,965 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\bin\cura_app.py", line 83, in <module>
2017-12-24 02:05:22,966 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\CuraApplication.py", line 681, in run
2017-12-24 02:05:22,967 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 107, in __init__
2017-12-24 02:05:22,969 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\CuraApplication.py", line 733, in getMachineManager
2017-12-24 02:05:22,970 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\Settings\MachineManager.py", line 1234, in createMachineManager
2017-12-24 02:05:22,971 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\Settings\MachineManager.py", line 109, in __init__
2017-12-24 02:05:22,972 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\Settings\MachineManager.py", line 357, in setActiveMachine
2017-12-24 02:05:22,974 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\UM\Application.py", line 156, in setGlobalContainerStack
2017-12-24 02:05:22,975 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\UM\Signal.py", line 212, in emit
2017-12-24 02:05:22,976 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\UM\Signal.py", line 315, in __performEmit
2017-12-24 02:05:22,977 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 500, in _onStackChanged
2017-12-24 02:05:22,979 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 597, in _updateDisallowedAreas
2017-12-24 02:05:22,980 - CRITICAL - cura.CrashHandler.__init__ [65]:   File "X:\3.1\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 956, in _getEdgeDisallowedSize
2017-12-24 02:05:22,981 - CRITICAL - cura.CrashHandler.__init__ [65]: ValueError: max() arg is an empty sequence
 

Share this post


Link to post
Share on other sites

Getting some crashes here too.  It will be mid way through slicing and drop out on my Windows 10 Home/64 laptops.

 

Another thing I had happen was my antivirus gave an alert to when trying to Save File to my local hard disk.  Cura still seems to have problems playing nice with antivirus software (TrendMicro in my case).

 

Share this post


Link to post
Share on other sites

Is there already a solution?
I am using Cura 3.1 for about two weeks and right now it refused to start. Cura stopped at "Loading Interface..." (Win 7 / updated from 3.04, no beta installed).
Tried to start as admin - no difference.

Tried to kill the Cura.exe process in the taskmanager - does not work.

 

This makes Cura very much useless!

Share this post


Link to post
Share on other sites
On 12/26/2017 at 1:04 PM, LePaul said:

Getting some crashes here too.  It will be mid way through slicing and drop out on my Windows 10 Home/64 laptops.

 

Another thing I had happen was my antivirus gave an alert to when trying to Save File to my local hard disk.  Cura still seems to have problems playing nice with antivirus software (TrendMicro in my case).

 

I am using Avast. It alerted, gave me the choice to install anyway and ran ok. Then reported back about 30 minutes later that it was a safe program by the Avast team and added to their list of ok programs.

Share this post


Link to post
Share on other sites

Sorry if this is covered elsewhere and I missed it, very new to all this. Is Cura 3.1 for windows 10 only? I was upgrading from 14.07 to get the fan on off at various stages. PC  is windows 7 home premium 64bit edition.

Share this post


Link to post
Share on other sites
On 12/5/2017 at 6:56 PM, Crow said:

Windows 10 updated yesterday and this morning my Cura keeps crashing at startup. I have uninstalled and reinstalled the update but it still crashes. Anybody else have this problem?

 

I also had this problem... but a windows update that I did today actually fixed it.

There was nothing suspicious in the logs and also my gfx card drivers were updated. Previously Cura also worked... so it was really the windows update.

Share this post


Link to post
Share on other sites
On 12/6/2017 at 5:54 PM, antisubae said:

It works.

 

It doesn't work for me, unfortunately. Also never had the beta installed, I generally only use the release versions, so no wayward profiles for me to delete. The program simply doesn't run, and doesn't leave anything in any of the log files to tell me what's going on.

 

I have this problem too. I have been using Cura 3.2 for awhile now on Windows 10 with no issues. Then out of the blue with no obvious changes on my part it stopped working-- just hung and I had to kill the process. For a while after that I could start it by giving it admin privileges and then that quit working also. It just hung and refused to continue and never started up again no matter what I did. Finally I installed Cura 3.3 and went through the whole setup and printer tuning process all over again. It worked fine for a while-- several days-- with no issues. Then today with no obvious explanation it just hung. Killing it and restarting it doesn't help. Giving it admin privileges doesn't help. There's nothing obvious in the event logs and nothing obvious in any of the Cura logs. I've tried rebooting my machine and that doesn't help. I've checked for errant drivers and yada yada-- all clean. But when it comes to Cura, no workie. I'm getting by at the moment using Simplify3D but I would much prefer to be able to go back to using Cura as I'm used to it and I kinda like it.

 

If it will help, I've attached the logs from the "..\AppData\Roaming\cura" folder and the "3.3" subfolder. If needed I can attach the logs from the "3.2" folder.

 

Can anybody help me with this issue??

 

John

cura.log

stderr.log

stdout.log

Share this post


Link to post
Share on other sites

Extra info regarding previous post-- I can't go back and edit that one for some reason...

 

I've never used any version on this system prior to version 3.2. But the 3.3 version is a Beta, if that matters, but it was installed after I had the problems with the 3.2 version. So presumably it has nothing to do with those 3.2 issues.

 

Also-- a previous poster mentioned a windows update having to do with graphics-- I don't know about updates. My system has been up and running for a week(-ish) since the last reboot and before the problems began. However, I do note that the last entries in the logs seem to have something to do with setting up for graphics of some kind. Perhaps there is a connection here?

Share this post


Link to post
Share on other sites

I am having the same issue. I have installed versions 3.1, 3.2 and 3.2.1. All do the same thing. I can open the program after it installs, but when i close the program and try and reopen. All i get is the splash screen and see it open the close right away.

  • I have tried to Run as Admin.
  • Delete the Cura folder under AppData

I have version 2.3.1 32 bit working on another system that i have but would like to have the 64 bit on my new system.

 

I have attached a DxDiag log of my system.

DxDiag.log

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

Announcements

  • Our picks

    • Architect Design Contest | Vehicles.
      We're open for entries! - Design and submit your 3D designs of architectural entourage - vehicles - for a chance to win a large filament pack. Presenting an idea, an architectural design or something as big as an urban project isn't easy. A scaled model can really help to get your idea across.
        • Like
      • 14 replies
    • What The DfAM?
      I'm Steve Cox, an experienced engineer familiar with 3D printing. I wanted to share some DfAM guidelines with this community to help and make stronger parts.
      I'm also an Autodesk Certified Instructor for Fusion 360, so many of the images in ...
        • Thanks
        • Like
      • 17 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!