Mixing
Cura 3.5 doesn't launch repeatably
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
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 [369]: Upgraded .fdmextruder+%232_user.inst.cfg to version 4000005.
2018-10-10 21:49:33,605 - DEBUG - [MainThread] UM.Backend.Backend._logSocketState [178]: Socket state changed to Listening
2018-10-10 21:49:33,650 - INFO - [MainThread] UM.Backend.Backend.startEngine [74]: Started engine process: C:Program FilesUltimaker Cura 3.5CuraEngine.exe
2018-10-10 21:49:33,652 - DEBUG - [MainThread] UM.Backend.Backend._backendLog [94]: [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.
cura
edited 5 mins ago
Greenonline♦
2,9313844
asked 3 hours ago
ifconfig
307116
add a comment |Â
up vote
2
down vote
favorite
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 [369]: Upgraded .fdmextruder+%232_user.inst.cfg to version 4000005.
2018-10-10 21:49:33,605 - DEBUG - [MainThread] UM.Backend.Backend._logSocketState [178]: Socket state changed to Listening
2018-10-10 21:49:33,650 - INFO - [MainThread] UM.Backend.Backend.startEngine [74]: Started engine process: C:Program FilesUltimaker Cura 3.5CuraEngine.exe
2018-10-10 21:49:33,652 - DEBUG - [MainThread] UM.Backend.Backend._backendLog [94]: [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.
cura
edited 5 mins ago
Greenonline♦
2,9313844
asked 3 hours ago
ifconfig
307116
1
This should be mentioned at the Ultimaker forums, not here. I have had similar experience with an older version of Ultimaker Cura. Removing the appdata and re-install fixed it for me. Look at this topic.
– 0scar
2 hours ago
Yea... that seems to work. Any word on why the issue exists in the firstplace?
– ifconfig
2 hours ago
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
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 [369]: Upgraded .fdmextruder+%232_user.inst.cfg to version 4000005.
2018-10-10 21:49:33,605 - DEBUG - [MainThread] UM.Backend.Backend._logSocketState [178]: Socket state changed to Listening
2018-10-10 21:49:33,650 - INFO - [MainThread] UM.Backend.Backend.startEngine [74]: Started engine process: C:Program FilesUltimaker Cura 3.5CuraEngine.exe
2018-10-10 21:49:33,652 - DEBUG - [MainThread] UM.Backend.Backend._backendLog [94]: [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.
cura
edited 5 mins ago
Greenonline♦
2,9313844
asked 3 hours ago
ifconfig
307116
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 [369]: Upgraded .fdmextruder+%232_user.inst.cfg to version 4000005.
2018-10-10 21:49:33,605 - DEBUG - [MainThread] UM.Backend.Backend._logSocketState [178]: Socket state changed to Listening
2018-10-10 21:49:33,650 - INFO - [MainThread] UM.Backend.Backend.startEngine [74]: Started engine process: C:Program FilesUltimaker Cura 3.5CuraEngine.exe
2018-10-10 21:49:33,652 - DEBUG - [MainThread] UM.Backend.Backend._backendLog [94]: [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.
cura
cura
edited 5 mins ago
Greenonline♦
2,9313844
asked 3 hours ago
ifconfig
307116
edited 5 mins ago
Greenonline♦
2,9313844
asked 3 hours ago
ifconfig
307116
edited 5 mins ago
Greenonline♦
2,9313844
edited 5 mins ago
Greenonline♦
2,9313844
edited 5 mins ago
Greenonline♦
2,9313844
2,9313844
asked 3 hours ago
ifconfig
307116
asked 3 hours ago
ifconfig
307116
asked 3 hours ago
ifconfig
307116
307116
1
This should be mentioned at the Ultimaker forums, not here. I have had similar experience with an older version of Ultimaker Cura. Removing the appdata and re-install fixed it for me. Look at this topic.
– 0scar
2 hours ago
Yea... that seems to work. Any word on why the issue exists in the firstplace?
– ifconfig
2 hours ago
add a comment |Â
1
This should be mentioned at the Ultimaker forums, not here. I have had similar experience with an older version of Ultimaker Cura. Removing the appdata and re-install fixed it for me. Look at this topic.
– 0scar
2 hours ago
Yea... that seems to work. Any word on why the issue exists in the firstplace?
– ifconfig
2 hours ago
1
1
This should be mentioned at the Ultimaker forums, not here. I have had similar experience with an older version of Ultimaker Cura. Removing the appdata and re-install fixed it for me. Look at this topic.
– 0scar
2 hours ago
This should be mentioned at the Ultimaker forums, not here. I have had similar experience with an older version of Ultimaker Cura. Removing the appdata and re-install fixed it for me. Look at this topic.
– 0scar
2 hours ago
Yea... that seems to work. Any word on why the issue exists in the firstplace?
– ifconfig
2 hours ago
Yea... that seems to work. Any word on why the issue exists in the firstplace?
– ifconfig
2 hours ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Issues like these are not new, I have experienced similar issues (see e.g. this topic, but more can be found) with an installation of an older version. At the moment of writing there is already a reported issue with Ultimaker Cura 3.5.
It is generally best to mention problems with a specific software application at the developers own forum or tech support. This will catch a more specific type of users as well as the developers themselves.
A workaround, but not a definite solution, is to remove the settings (on the Windows platform these files are located in AppData/Roaming/cura) that Ultimaker Cura uses and remove prior installations and do a fresh re-install of 3.5 and see if this works. Just rename the directory to e.g. AppData/Roaming/cura_old, this way you can always go back.
The drawback of this solution is that all material profiles and printer setups are lost as you start completely new. This is not a problem if you have a single printer and no custom materials defined, but in my case it was a lot of work to get all profiles back.
These issues could be related to the profile settings and storage model, which, at the time of the older installations was not very stable. A new material model was required, if that has been replaced is still a question.
answered 2 hours ago
0scar
6,24911037
A crude solution if there ever was one, but it does work.
– ifconfig
2 hours ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Issues like these are not new, I have experienced similar issues (see e.g. this topic, but more can be found) with an installation of an older version. At the moment of writing there is already a reported issue with Ultimaker Cura 3.5.
It is generally best to mention problems with a specific software application at the developers own forum or tech support. This will catch a more specific type of users as well as the developers themselves.
A workaround, but not a definite solution, is to remove the settings (on the Windows platform these files are located in AppData/Roaming/cura) that Ultimaker Cura uses and remove prior installations and do a fresh re-install of 3.5 and see if this works. Just rename the directory to e.g. AppData/Roaming/cura_old, this way you can always go back.
The drawback of this solution is that all material profiles and printer setups are lost as you start completely new. This is not a problem if you have a single printer and no custom materials defined, but in my case it was a lot of work to get all profiles back.
These issues could be related to the profile settings and storage model, which, at the time of the older installations was not very stable. A new material model was required, if that has been replaced is still a question.
answered 2 hours ago
0scar
6,24911037
A crude solution if there ever was one, but it does work.
– ifconfig
2 hours ago
add a comment |Â
up vote
2
down vote
accepted
Issues like these are not new, I have experienced similar issues (see e.g. this topic, but more can be found) with an installation of an older version. At the moment of writing there is already a reported issue with Ultimaker Cura 3.5.
It is generally best to mention problems with a specific software application at the developers own forum or tech support. This will catch a more specific type of users as well as the developers themselves.
A workaround, but not a definite solution, is to remove the settings (on the Windows platform these files are located in AppData/Roaming/cura) that Ultimaker Cura uses and remove prior installations and do a fresh re-install of 3.5 and see if this works. Just rename the directory to e.g. AppData/Roaming/cura_old, this way you can always go back.
The drawback of this solution is that all material profiles and printer setups are lost as you start completely new. This is not a problem if you have a single printer and no custom materials defined, but in my case it was a lot of work to get all profiles back.
These issues could be related to the profile settings and storage model, which, at the time of the older installations was not very stable. A new material model was required, if that has been replaced is still a question.
answered 2 hours ago
0scar
6,24911037
A crude solution if there ever was one, but it does work.
– ifconfig
2 hours ago
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Issues like these are not new, I have experienced similar issues (see e.g. this topic, but more can be found) with an installation of an older version. At the moment of writing there is already a reported issue with Ultimaker Cura 3.5.
It is generally best to mention problems with a specific software application at the developers own forum or tech support. This will catch a more specific type of users as well as the developers themselves.
A workaround, but not a definite solution, is to remove the settings (on the Windows platform these files are located in AppData/Roaming/cura) that Ultimaker Cura uses and remove prior installations and do a fresh re-install of 3.5 and see if this works. Just rename the directory to e.g. AppData/Roaming/cura_old, this way you can always go back.
The drawback of this solution is that all material profiles and printer setups are lost as you start completely new. This is not a problem if you have a single printer and no custom materials defined, but in my case it was a lot of work to get all profiles back.
These issues could be related to the profile settings and storage model, which, at the time of the older installations was not very stable. A new material model was required, if that has been replaced is still a question.
answered 2 hours ago
0scar
6,24911037
Issues like these are not new, I have experienced similar issues (see e.g. this topic, but more can be found) with an installation of an older version. At the moment of writing there is already a reported issue with Ultimaker Cura 3.5.
It is generally best to mention problems with a specific software application at the developers own forum or tech support. This will catch a more specific type of users as well as the developers themselves.
A workaround, but not a definite solution, is to remove the settings (on the Windows platform these files are located in AppData/Roaming/cura) that Ultimaker Cura uses and remove prior installations and do a fresh re-install of 3.5 and see if this works. Just rename the directory to e.g. AppData/Roaming/cura_old, this way you can always go back.
The drawback of this solution is that all material profiles and printer setups are lost as you start completely new. This is not a problem if you have a single printer and no custom materials defined, but in my case it was a lot of work to get all profiles back.
These issues could be related to the profile settings and storage model, which, at the time of the older installations was not very stable. A new material model was required, if that has been replaced is still a question.
answered 2 hours ago
0scar
6,24911037
answered 2 hours ago
0scar
6,24911037
answered 2 hours ago
0scar
6,24911037
answered 2 hours ago
0scar
6,24911037
6,24911037
A crude solution if there ever was one, but it does work.
– ifconfig
2 hours ago
add a comment |Â
A crude solution if there ever was one, but it does work.
– ifconfig
2 hours ago
A crude solution if there ever was one, but it does work.
– ifconfig
2 hours ago
A crude solution if there ever was one, but it does work.
– ifconfig
2 hours ago
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2f3dprinting.stackexchange.com%2fquestions%2f7164%2fcura-3-5-doesnt-launch-repeatably%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
This should be mentioned at the Ultimaker forums, not here. I have had similar experience with an older version of Ultimaker Cura. Removing the appdata and re-install fixed it for me. Look at this topic.
– 0scar
2 hours ago
Yea... that seems to work. Any word on why the issue exists in the firstplace?
– ifconfig
2 hours ago