mct75

After chasing keys around in the registry, I punted and restored my entire NTUSER.DAT file and now Cura loads and all my profiles and printers are back. It wasn't a Cura problem, but instead a Windows one.

The set command works with echo but still not from a run prompt. Apparently there's a registry option that needs to be tweaked, I will try that.

Hmm, it originally echoed as %appdata% in a command line. I ran "set appdata=c:\users\me\appdata\roaming" and now "echo %appdata%" works as expected but Cura is still behaving the same.

Thanks nzo! I run Veeam and it works very well, but I'd rather not restore 3+ TB of data and reconcile everything I've changed in the past week just to fix an issue with a single application.

Hello! My computer got a BSOD and when I logged back in some of my Windows settings had been reverted, my Google Chrome profile was gone, etc. I assume environment variables and the like might be messed up too. Maybe Python and stuff too. Just a backstory. Cura worked great before the crash. When I try to launch Cura (2.6, 2.7 or 3.0) nothing happens. No splash screen or anything. I deleted the appdata/local/cura folders and when I launch Cura I get a stderr.log (which is empty) and a stdout.log which is pasted below. No other files or folders. I've tried reinstalling but this is all that happens. Thanks! stdout.log: UM.Qt.QtApplication.__init__ [55]: Adding QT5 plugin path: C:\Program Files\Ultimaker Cura 3.0\PyQt5\pluginsUM.Qt.QtApplication.__init__ [65]: Adding QT5 plugin path: C:\Program Files\Ultimaker Cura 3.0\PyQt5\pluginsUM.Resources.__initializeStoragePaths [342]: Initializing storage pathscura.CrashHandler.show [39]: An uncaught exception has occurred!cura.CrashHandler.show [42]: Traceback (most recent call last):cura.CrashHandler.show [42]: File "", line 969, in _find_and_loadcura.CrashHandler.show [42]: File "", line 958, in _find_and_load_unlockedcura.CrashHandler.show [42]: File "", line 664, in _load_unlockedcura.CrashHandler.show [42]: File "", line 634, in _load_backward_compatiblecura.CrashHandler.show [42]: File "__startup__.py", line 12, in cura.CrashHandler.show [42]: File "", line 969, in _find_and_loadcura.CrashHandler.show [42]: File "", line 958, in _find_and_load_unlockedcura.CrashHandler.show [42]: File "", line 664, in _load_unlockedcura.CrashHandler.show [42]: File "", line 634, in _load_backward_compatiblecura.CrashHandler.show [42]: File "Console.py", line 24, in cura.CrashHandler.show [42]: File "X:\3.0\build\inst\bin\cura_app.py", line 81, in cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\Application.py", line 321, in getInstancecura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\cura\CuraApplication.py", line 206, in __init__cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\Qt\QtApplication.py", line 70, in __init__cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\Application.py", line 89, in __init__cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\Resources.py", line 65, in getPathcura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\Resources.py", line 117, in getStoragePathcura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\Resources.py", line 154, in getStoragePathForTypecura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\Resources.py", line 352, in __initializeStoragePathscura.CrashHandler.show [42]: File "ntpath.py", line 113, in joincura.CrashHandler.show [42]: File "genericpath.py", line 143, in _check_arg_typescura.CrashHandler.show [42]: TypeError: join() argument must be str or bytes, not 'NoneType'

Hmm. I'll still update at home and see if the behaviour changes.

I saw that Cura 2.6.2 was available, so I downloaded it on my work computer. I set up a Prusa i3 Mk2, and it looks like the keepout settings are respected now. I will try it at home tonight and make sure it is the same for my configuration there, but this is very good to see!

Interesting, thanks! Is there a workaround or should I just hold on for a new release?

I noticed that if I change the print mode to "all at once", it will allow me to space the prints close together (as expected) and then I can change it back to one-at-a-time and it will slice some of them for me, but it still seems a bit unhappy about these large rectangular keepouts. Maybe there is a default value for the printhead dimensions that the "Prusa i3" profile isn't overwriting? If I can provide log files or anything to help, let me know.

I am using a Monoprice Maker Select V2, which I think is a Wanhao Duplicator I3. It works great in Cura 15.04 so either I don't know how to work Cura 2.6 or it's a bug somewhere.

Thank you for your reply. Sadly I have already done that.

Hi. I am using Cura 2.6.1. I need to print dozens of small 10x10x2.2 mm objects. Obviously, these are so short that there is zero interference with the gantry and printhead. I've got my gantry/printhead dimensions set in Cura, but I am getting a large offset rectangle of "keepout" on my prints. I'm not sure where this is coming from, since the gantry height is far taller than 2.2mm. How can I turn it off? Thanks!