When I was notified by Cura that 3.5 was out, I looked at the changelog, and I installed the new version. It worked normally for a time, until once when I went to launch it and
cura.exe forever sat idle in task manager doing nothing. I reinstalled Cura 3.5 and tried again.
That then worked for some time, maybe another couple days, and then the same thing happened again. Rince and repeat, maybe for a few more cycles. Now, Cura 3.5 doesn't like to do anything even fresh out of the box. Restarting the computer does nothing.
I've looked at the
cura.log file in
AppData/Roaming/cura and found a peculiar line:
2018-10-10 21:49:33,591 - INFO - [MainThread] UM.VersionUpgradeManager._upgradeFile : Upgraded .\fdmextruder+%232_user.inst.cfg to version 4000005.
2018-10-10 21:49:33,605 - DEBUG - [MainThread] UM.Backend.Backend._logSocketState : Socket state changed to Listening
2018-10-10 21:49:33,650 - INFO - [MainThread] UM.Backend.Backend.startEngine : Started engine process: C:\Program Files\Ultimaker Cura 3.5\CuraEngine.exe
2018-10-10 21:49:33,652 - DEBUG - [MainThread] UM.Backend.Backend._backendLog : [Backend] Calling engine with: ['C:\\Program Files\\Ultimaker Cura 3.5\\CuraEngine.exe', 'connect', '127.0.0.1:49674', '-j', 'C:\\Program Files\\Ultimaker Cura 3.5\\resources\\definitions\\fdmprinter.def.json', '']
It looks as if the issue is when the Cura GUI tries to connect to its backend slicing engine. Is my analysis correct? Is this a known issue/is there a known fix?
I'm going to try to report this to Ultimaker if nothing comes up here.