-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3.4.1] Cura back to windows and crash when add printer #3784
Comments
Can you provide the 3.2 data folder so we can investigate? |
Also provide the configuration files for the printer (is they are not included in the 3.2 data folder) |
I ve zipped the file of configuration for EXP3d |
Up i always search error in config files with no succes |
This page will tell you where to look |
I loaded up those profiles and got the same error. The mistake comes from the definition file. It names a I've made a fix so that Cura no longer crashes on this for the next release but instead swaps to an arbitrary quality type that does exist. You'll need to update the version of those configuration files anyway though. Good luck. |
I ve done your advice but not resolve problem for cura 3.4.1 |
@Ghostkeeper. I redid the procedure described to try to solve the problem but it was unsuccessful. |
Could you try again with Cura 3.5? The fix I made should be included with that release. |
I have a custom printer settings work on cura 3.2.1 but with upgrade to 3.3.1.
The printer is an EXP3D, the builder provided configuration files for version 3.2.1 but I think with the changes in the machine manager a variable must be wrong and crash cura.
Cura.log said :
2018-05-07 11:07:15,390 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend.slice [210]: Starting to slice...
2018-05-07 11:07:15,390 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend.slice [227]: Going to slice build plate [0]!
2018-05-07 11:07:15,390 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend.slice [235]: Build plate 0 has no objects to be sliced, skipping
2018-05-07 11:07:23,937 - DEBUG - [MainThread] AutoSave.AutoSave._onTimeout [71]: Autosaving preferences, instances and profiles
2018-05-07 11:07:35,758 - DEBUG - [MainThread] LocalContainerProvider.LocalContainerProvider.loadContainer [53]: Loading container exp3d
2018-05-07 11:07:36,080 - DEBUG - [MainThread] UM.Settings.ContainerRegistry.addContainer [355]: Container [exp3d] added.
2018-05-07 11:07:36,099 - DEBUG - [MainThread] UM.Settings.ContainerRegistry.addContainer [355]: Container [Exp3D_settings] added.
2018-05-07 11:07:36,100 - DEBUG - [MainThread] UM.Settings.ContainerRegistry.addContainer [355]: Container [Exp3D_user] added.
2018-05-07 11:07:36,127 - DEBUG - [MainThread] UM.Settings.ContainerRegistry.addContainer [355]: Container [fdmextruder #4_settings] added.
2018-05-07 11:07:36,129 - DEBUG - [MainThread] UM.Settings.ContainerRegistry.addContainer [355]: Container [fdmextruder #4_user] added.
2018-05-07 11:07:36,130 - INFO - [MainThread] cura.Settings.GlobalStack.addExtruder [74]: Extruder[fdmextruder #4] added to [Exp3D] at position [0]
2018-05-07 11:07:36,136 - WARNING - [MainThread] cura.Settings.GlobalStack.addExtruder [70]: Extruder [fdmextruder #4] has already been added to this stack [Exp3D]
2018-05-07 11:07:36,143 - DEBUG - [MainThread] UM.Settings.ContainerRegistry.addContainer [355]: Container [fdmextruder #4] added.
2018-05-07 11:07:36,153 - CRITICAL - [MainThread] cura.CrashHandler.init [66]: An uncaught error has occurred!
2018-05-07 11:07:36,155 - CRITICAL - [MainThread] cura.CrashHandler.init [69]: Traceback (most recent call last):
2018-05-07 11:07:36,156 - CRITICAL - [MainThread] cura.CrashHandler.init [69]: File "X:\3.3\build\inst\lib\python3.5\site-packages\cura\Settings\MachineManager.py", line 381, in addMachine
2018-05-07 11:07:36,158 - CRITICAL - [MainThread] cura.CrashHandler.init [69]: File "X:\3.3\build\inst\lib\python3.5\site-packages\cura\Settings\CuraStackBuilder.py", line 109, in createMachine
2018-05-07 11:07:36,159 - CRITICAL - [MainThread] cura.CrashHandler.init [69]: AttributeError: 'NoneType' object has no attribute 'node_for_global'
The text was updated successfully, but these errors were encountered: