Notifications
Clear all

Slow GCODE export with 1.41.2 Win64 edition  

  RSS
SleepingGiant
(@sleepinggiant)
Eminent Member
Slow GCODE export with 1.41.2 Win64 edition

I am experiencing super slow export of GCODE after installing the new Slic3r 1.41.2 Win64 edition. This is precisely why I was nervous installing the update - whenever I have something working perfectly, then I upgrade, something inevitably breaks.
So... please - how can I download the previous version of Slic3r so that I can install it and get on with my happy printing experience with PRUSA?

I have an i7 Acer Nitro Black Edition very nice laptop with all SSD hard drives. In the previous version of Slic3r the GCODES would export nearly instantaneously. Never longer than 10 or 15 seconds to export any code.

I have currently been exporting this most recent GCODE for over 30 minutes - which I think we can all agree is ridiculous. 😆 UPDATE: The export began at 11:36 and finally finished at 12:17 🙄

The Slicing phase went very quickly, less than 10 seconds. I'm only having a problem when I export GCODE.

Last night when I exported this gcode for the first time (21Mb gcode file) I don't know exactly how long it took, after waiting 3 or 4 minutes I walked away and did other things for an hour or two and when I returned to the machine it had finally completed. Today I decided I wanted to modify some little things in the settings and re-export, and now the code exporting is taking forever. Slic3r is shown as using 20% of my CPU while generating the code.

Thank you.

Napsal : 07/02/2019 12:22 pm
SleepingGiant
(@sleepinggiant)
Eminent Member
Topic starter answered:
Re: Slow GCODE export with 1.41.2 Win64 edition

I think I discovered the answer to the problem. When I walked away from the problem for a while, I remembered that I had enabled "avoid crossing perimeters" and so when I disabled this - GCODE export went back to 15 seconds.

There's a warning there that pops up as a tool tip that "slows down GCODE generation" but it doesn't say it will slow it down EXPONENTIALLY. 😆

So please ignore my question, but I will leave this here in case anyone else has the same issue in the future.

Napsal : 07/02/2019 12:52 pm
Share: