Cura doesn't slice
$begingroup$
I can launch Cura with no issues, it runs fine. I can import objects and change settings, but when I click 'slice' it doesn't even show a progress bar on 3.6.0 and on v4 it shows a progress bar but there's never any progress.
I've looked in %appdata%cura4.0cura.log and it just stops at an entry like this:
2019-01-11 20:38:46,714 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend._onStartSliceCompleted [430]: Sending slice message took 0.7397589683532715 seconds
I looked in task manager and the system idle process has >95% cpu (cpu is almost completely idle), and like I said I can use Cura just fine (no stuttering when I rotate objects).
cura
asked 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
$endgroup$
add a comment |
$begingroup$
I can launch Cura with no issues, it runs fine. I can import objects and change settings, but when I click 'slice' it doesn't even show a progress bar on 3.6.0 and on v4 it shows a progress bar but there's never any progress.
I've looked in %appdata%cura4.0cura.log and it just stops at an entry like this:
2019-01-11 20:38:46,714 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend._onStartSliceCompleted [430]: Sending slice message took 0.7397589683532715 seconds
I looked in task manager and the system idle process has >95% cpu (cpu is almost completely idle), and like I said I can use Cura just fine (no stuttering when I rotate objects).
cura
asked 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
$endgroup$
add a comment |
$begingroup$
I can launch Cura with no issues, it runs fine. I can import objects and change settings, but when I click 'slice' it doesn't even show a progress bar on 3.6.0 and on v4 it shows a progress bar but there's never any progress.
I've looked in %appdata%cura4.0cura.log and it just stops at an entry like this:
2019-01-11 20:38:46,714 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend._onStartSliceCompleted [430]: Sending slice message took 0.7397589683532715 seconds
I looked in task manager and the system idle process has >95% cpu (cpu is almost completely idle), and like I said I can use Cura just fine (no stuttering when I rotate objects).
cura
asked 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
$endgroup$
I can launch Cura with no issues, it runs fine. I can import objects and change settings, but when I click 'slice' it doesn't even show a progress bar on 3.6.0 and on v4 it shows a progress bar but there's never any progress.
I've looked in %appdata%cura4.0cura.log and it just stops at an entry like this:
2019-01-11 20:38:46,714 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend._onStartSliceCompleted [430]: Sending slice message took 0.7397589683532715 seconds
I looked in task manager and the system idle process has >95% cpu (cpu is almost completely idle), and like I said I can use Cura just fine (no stuttering when I rotate objects).
cura
cura
asked 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 days ago
LinuxDiscipleLinuxDisciple
1513
asked 2 days ago
LinuxDiscipleLinuxDisciple
1513
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
$begingroup$
The culprit was ZoneAlarm firewall.
Cura runs and talks to another executable (CuraEngine.exe) for slicing, and ZoneAlarm never asked me whether CuraEngine should have the access it needed, so it got blocked.
Here are the steps I took to fix it:
- Open ZoneAlarm
- click the firewall tab
- click where it says "X programs secured"
- under "View Programs" you'll see a bunch of program names. It takes a while for my list to populate, you may have to wait a minute here.
- Find the entry for cura.exe (you can order them by alpha) and set "Outbound Trusted" to Allow
- Find the entry for "Slicing engine for Cura" (that's how CuraEngine.exe is listed). Set "Outbound Internet" to "Allow" and set "Inbound Trusted" to "Allow" (this will implicitly set "Outbound Trusted" to "Allow" as well).
- Click "OK"
You should be good to go. I didn't even have to restart Cura. I just hit 'cancel' on that slice and then clicked 'slice' again and it worked.
From my testing, the settings in 5. and 6. are the minimum you can allow and still get it to work.
answered 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
$endgroup$
$begingroup$
Welcome at 3D Printing.SE! Thanks for sharing your experience, I have struggled many times to find a similar solution for other applications that call executables instead of dll files. The actual slicing is indeed done by the engine of Ultimaker Cura, a separate executable.
$endgroup$
– 0scar
2 days ago
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "640"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
LinuxDisciple is a new contributor. Be nice, and check out our Code of Conduct.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2f3dprinting.stackexchange.com%2fquestions%2f7953%2fcura-doesnt-slice%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
The culprit was ZoneAlarm firewall.
Cura runs and talks to another executable (CuraEngine.exe) for slicing, and ZoneAlarm never asked me whether CuraEngine should have the access it needed, so it got blocked.
Here are the steps I took to fix it:
- Open ZoneAlarm
- click the firewall tab
- click where it says "X programs secured"
- under "View Programs" you'll see a bunch of program names. It takes a while for my list to populate, you may have to wait a minute here.
- Find the entry for cura.exe (you can order them by alpha) and set "Outbound Trusted" to Allow
- Find the entry for "Slicing engine for Cura" (that's how CuraEngine.exe is listed). Set "Outbound Internet" to "Allow" and set "Inbound Trusted" to "Allow" (this will implicitly set "Outbound Trusted" to "Allow" as well).
- Click "OK"
You should be good to go. I didn't even have to restart Cura. I just hit 'cancel' on that slice and then clicked 'slice' again and it worked.
From my testing, the settings in 5. and 6. are the minimum you can allow and still get it to work.
answered 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
$endgroup$
$begingroup$
Welcome at 3D Printing.SE! Thanks for sharing your experience, I have struggled many times to find a similar solution for other applications that call executables instead of dll files. The actual slicing is indeed done by the engine of Ultimaker Cura, a separate executable.
$endgroup$
– 0scar
2 days ago
add a comment |
$begingroup$
The culprit was ZoneAlarm firewall.
Cura runs and talks to another executable (CuraEngine.exe) for slicing, and ZoneAlarm never asked me whether CuraEngine should have the access it needed, so it got blocked.
Here are the steps I took to fix it:
- Open ZoneAlarm
- click the firewall tab
- click where it says "X programs secured"
- under "View Programs" you'll see a bunch of program names. It takes a while for my list to populate, you may have to wait a minute here.
- Find the entry for cura.exe (you can order them by alpha) and set "Outbound Trusted" to Allow
- Find the entry for "Slicing engine for Cura" (that's how CuraEngine.exe is listed). Set "Outbound Internet" to "Allow" and set "Inbound Trusted" to "Allow" (this will implicitly set "Outbound Trusted" to "Allow" as well).
- Click "OK"
You should be good to go. I didn't even have to restart Cura. I just hit 'cancel' on that slice and then clicked 'slice' again and it worked.
From my testing, the settings in 5. and 6. are the minimum you can allow and still get it to work.
answered 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
$endgroup$
$begingroup$
Welcome at 3D Printing.SE! Thanks for sharing your experience, I have struggled many times to find a similar solution for other applications that call executables instead of dll files. The actual slicing is indeed done by the engine of Ultimaker Cura, a separate executable.
$endgroup$
– 0scar
2 days ago
add a comment |
$begingroup$
The culprit was ZoneAlarm firewall.
Cura runs and talks to another executable (CuraEngine.exe) for slicing, and ZoneAlarm never asked me whether CuraEngine should have the access it needed, so it got blocked.
Here are the steps I took to fix it:
- Open ZoneAlarm
- click the firewall tab
- click where it says "X programs secured"
- under "View Programs" you'll see a bunch of program names. It takes a while for my list to populate, you may have to wait a minute here.
- Find the entry for cura.exe (you can order them by alpha) and set "Outbound Trusted" to Allow
- Find the entry for "Slicing engine for Cura" (that's how CuraEngine.exe is listed). Set "Outbound Internet" to "Allow" and set "Inbound Trusted" to "Allow" (this will implicitly set "Outbound Trusted" to "Allow" as well).
- Click "OK"
You should be good to go. I didn't even have to restart Cura. I just hit 'cancel' on that slice and then clicked 'slice' again and it worked.
From my testing, the settings in 5. and 6. are the minimum you can allow and still get it to work.
answered 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
$endgroup$
The culprit was ZoneAlarm firewall.
Cura runs and talks to another executable (CuraEngine.exe) for slicing, and ZoneAlarm never asked me whether CuraEngine should have the access it needed, so it got blocked.
Here are the steps I took to fix it:
- Open ZoneAlarm
- click the firewall tab
- click where it says "X programs secured"
- under "View Programs" you'll see a bunch of program names. It takes a while for my list to populate, you may have to wait a minute here.
- Find the entry for cura.exe (you can order them by alpha) and set "Outbound Trusted" to Allow
- Find the entry for "Slicing engine for Cura" (that's how CuraEngine.exe is listed). Set "Outbound Internet" to "Allow" and set "Inbound Trusted" to "Allow" (this will implicitly set "Outbound Trusted" to "Allow" as well).
- Click "OK"
You should be good to go. I didn't even have to restart Cura. I just hit 'cancel' on that slice and then clicked 'slice' again and it worked.
From my testing, the settings in 5. and 6. are the minimum you can allow and still get it to work.
answered 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
LinuxDiscipleLinuxDisciple
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
LinuxDiscipleLinuxDisciple
1513
answered 2 days ago
LinuxDiscipleLinuxDisciple
1513
1513
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
LinuxDisciple is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
$begingroup$
Welcome at 3D Printing.SE! Thanks for sharing your experience, I have struggled many times to find a similar solution for other applications that call executables instead of dll files. The actual slicing is indeed done by the engine of Ultimaker Cura, a separate executable.
$endgroup$
– 0scar
2 days ago
add a comment |
$begingroup$
Welcome at 3D Printing.SE! Thanks for sharing your experience, I have struggled many times to find a similar solution for other applications that call executables instead of dll files. The actual slicing is indeed done by the engine of Ultimaker Cura, a separate executable.
$endgroup$
– 0scar
2 days ago
$begingroup$
Welcome at 3D Printing.SE! Thanks for sharing your experience, I have struggled many times to find a similar solution for other applications that call executables instead of dll files. The actual slicing is indeed done by the engine of Ultimaker Cura, a separate executable.
$endgroup$
– 0scar
2 days ago
$begingroup$
Welcome at 3D Printing.SE! Thanks for sharing your experience, I have struggled many times to find a similar solution for other applications that call executables instead of dll files. The actual slicing is indeed done by the engine of Ultimaker Cura, a separate executable.
$endgroup$
– 0scar
2 days ago
add a comment |
LinuxDisciple is a new contributor. Be nice, and check out our Code of Conduct.
LinuxDisciple is a new contributor. Be nice, and check out our Code of Conduct.
LinuxDisciple is a new contributor. Be nice, and check out our Code of Conduct.
LinuxDisciple is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to 3D Printing Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2f3dprinting.stackexchange.com%2fquestions%2f7953%2fcura-doesnt-slice%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
