Cura doesn't slice












2












$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).










share|improve this question









$endgroup$

















    2












    $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).










    share|improve this question









    $endgroup$















      2












      2








      2





      $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).










      share|improve this question









      $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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 12 at 7:43









      LinuxDiscipleLinuxDisciple

      1613




      1613






















          1 Answer
          1






          active

          oldest

          votes


















          5












          $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:




          1. Open ZoneAlarm

          2. click the firewall tab

          3. click where it says "X programs secured"

          4. 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.

          5. Find the entry for cura.exe (you can order them by alpha) and set "Outbound Trusted" to Allow

          6. 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).

          7. 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.






          share|improve this answer









          $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
            Jan 12 at 11:50










          • $begingroup$
            Sounds like another app never to install in the first place. BTW, your name seems to conflict with your current OS :-) .
            $endgroup$
            – Carl Witthoft
            Jan 15 at 15:14











          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
          });


          }
          });














          draft saved

          draft discarded


















          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









          5












          $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:




          1. Open ZoneAlarm

          2. click the firewall tab

          3. click where it says "X programs secured"

          4. 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.

          5. Find the entry for cura.exe (you can order them by alpha) and set "Outbound Trusted" to Allow

          6. 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).

          7. 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.






          share|improve this answer









          $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
            Jan 12 at 11:50










          • $begingroup$
            Sounds like another app never to install in the first place. BTW, your name seems to conflict with your current OS :-) .
            $endgroup$
            – Carl Witthoft
            Jan 15 at 15:14
















          5












          $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:




          1. Open ZoneAlarm

          2. click the firewall tab

          3. click where it says "X programs secured"

          4. 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.

          5. Find the entry for cura.exe (you can order them by alpha) and set "Outbound Trusted" to Allow

          6. 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).

          7. 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.






          share|improve this answer









          $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
            Jan 12 at 11:50










          • $begingroup$
            Sounds like another app never to install in the first place. BTW, your name seems to conflict with your current OS :-) .
            $endgroup$
            – Carl Witthoft
            Jan 15 at 15:14














          5












          5








          5





          $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:




          1. Open ZoneAlarm

          2. click the firewall tab

          3. click where it says "X programs secured"

          4. 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.

          5. Find the entry for cura.exe (you can order them by alpha) and set "Outbound Trusted" to Allow

          6. 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).

          7. 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.






          share|improve this answer









          $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:




          1. Open ZoneAlarm

          2. click the firewall tab

          3. click where it says "X programs secured"

          4. 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.

          5. Find the entry for cura.exe (you can order them by alpha) and set "Outbound Trusted" to Allow

          6. 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).

          7. 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.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 12 at 7:43









          LinuxDiscipleLinuxDisciple

          1613




          1613












          • $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
            Jan 12 at 11:50










          • $begingroup$
            Sounds like another app never to install in the first place. BTW, your name seems to conflict with your current OS :-) .
            $endgroup$
            – Carl Witthoft
            Jan 15 at 15:14


















          • $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
            Jan 12 at 11:50










          • $begingroup$
            Sounds like another app never to install in the first place. BTW, your name seems to conflict with your current OS :-) .
            $endgroup$
            – Carl Witthoft
            Jan 15 at 15:14
















          $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
          Jan 12 at 11:50




          $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
          Jan 12 at 11:50












          $begingroup$
          Sounds like another app never to install in the first place. BTW, your name seems to conflict with your current OS :-) .
          $endgroup$
          – Carl Witthoft
          Jan 15 at 15:14




          $begingroup$
          Sounds like another app never to install in the first place. BTW, your name seems to conflict with your current OS :-) .
          $endgroup$
          – Carl Witthoft
          Jan 15 at 15:14


















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

          ComboBox Display Member on multiple fields

          Is it possible to collect Nectar points via Trainline?