Avisos
Vaciar todo

Slic3r 1.41.0-alpha2 print time estimation display issue  

  RSS
Haku3D
(@haku3d)
Eminent Member
Slic3r 1.41.0-alpha2 print time estimation display issue

The "Estimated printing time" numbers don't update properly.

If you load up a .stl, slice & save .gcode you get the "Estimated printing time" numbers showing, but if you then select the object and press '+' to make 2 or more copies then slice & save .gcode, the "Estimated printing time" numbers don't get refreshed to show what they're supposed to be.

Respondido : 26/07/2018 9:34 pm
JoanTabb
(@joantabb)
Veteran Member Moderator
Re: Slic3r 1.41.0-alpha2 print time estimation display issue

Hi Ridwan
I am using Slic3r v1.40.1 +win64

with one small model the projected time is just over 16 minutes, and
with two small models, the projected time i just over 32 minutes

I wonder what's changed?

regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK

Respondido : 27/07/2018 11:54 am
Haku3D
(@haku3d)
Eminent Member
Topic starter answered:
Re: Slic3r 1.41.0-alpha2 print time estimation display issue

hi Joan,

I found with this Slic3rPE-1.41.0-alpha2+win64-full-201807211541.zip version I'm running, after doing a slice+gcode save, subsequent increasing/decreasing model copies doesn't update the print time estimation after slicing+gcode saving, I have to load or delete an additional model and then print time estimation numbers will show properly after slicing+gcode saving.

In the summary for 1.41.0-alpha2 they do say they've been working on the print time estimation code to also give an estimation in stealth mode, maybe this is where the bug crept in.

A little annoying but doesn't stop me printing, I guess this is why it's an alpha version 🙂

Respondido : 27/07/2018 6:22 pm
Vojtěch Bubník
(@vojtech-bubnik)
Miembro Admin
Re: Slic3r 1.41.0-alpha2 print time estimation display issue

Somebody reported the bug and it will be fixed in the upcoming beta.
https://github.com/prusa3d/Slic3r/issues/1081

Respondido : 02/08/2018 6:39 pm
Compartir: