I’m getting a bit tired of Slic3r not giving print time estimates. I’ve been using gcode.ws to estimate print time and its okay for single color prints but with multi-color (via y-splitter) the time estimate is off by a factor of 4 for some prints. Any suggestions on how to estimate print time?
Doesn’t really answer your question but, why not invest in simplify?
In regards to time estimation- a lot of the time discrepancy is due to your acceleration and jerk settings. Because your slicer does not know these values, it cannot accurately tell you print times as it is unaware when the head starts to decelerate and accelerate.
Try Slic3r Prusa Edition, it’s Slic3r tweaked heavily, maybe it can give better print time estimates.
wasn’t there correction multiplayer for estimations, i know i saw it once… 
@Griffin_Paquette i agree with you on acc/jerk, but simplify can’t print *.obj files for instance… it’s not so all in one, as some might suggest.
@Griffin_Paquette I have it and would love to use it but I can’t get it properly configured for the Prusa MMU setup. BTW Slic3r PE does have all the acceleration values.
@Rob_Wilson I’m using Slic3r PE, there are no time estimates. Your response confuses me.
Yes I know most slicers don’t calculate time correctly but I usually get within 25% of the actual time. I’m getting an error of over 300% with multi-color prints using http://gcode.ws
This is a nice one:
http://www.gcodeanalyser.com/
Using Cura I just add 20% to the estimated print time and it comes out within a few minutes of that result.
By increasing my Jerk from 6 to 10 and my acceleration from 900 to about 1600 the default print time in Crua was just about right on but the print quality suffered so I dropped them back down.
The version of Slic3r I have gives me print times that are about 30% off. I don’t use it anymore. Not sure why you are getting no print time estimate at all. Is there a setting to turn off the display completely that might have inadvertently been triggered?
@Adam_Steinmark I slice with Slic3r Prusa Ed, but not it’s interface, Repetier Host is my interface and it’s time estimates are pretty close. Wasn’t sure if it got those estimates from Slic3r or calculated the times itself.
I use Printrun and it gives me pretty close estimates.
My last print was 4h long and it missed by about 20min.
@Jeff_Parish Where are you seeing time estimates, can you post a screenshot? When I couldn’t find it at first I did some research and came across the following: https://shop.prusa3d.com/forum/print-tips-slic3r-settings-kisslicer-model-repair--f12/estimating-print-time-with-slic3r-t2969.html
@Rob_Wilson @Andre_Frazatto I’d like to know before I start a print how long it will take. All interfaces I know of estimate time during the print.
@Adam_Steinmark Printrun tells the estimate time when you load the model.
@Adam_Steinmark Looks like I was mistaken. Must have gotten confused when I had 4 slicers open running some comparisons. I could have sworn I had a print time displayed in the upper left corner. I opened it back up by itself and checked again and you are right. There is NOT a print time estimate in the standalone version that I can find. That is really annoying.
Also did some searching while scratching my head trying to figure to what I remembered seeing and as of at least a month ago the feature is still not supported? Apparently you need to use some other program to calculate.
While we prefer Slic3r over Cura and Kisslicer, it is true that Slic3r does not give time estimates. But since we use Pronterface (AKA Printrun) that will give decent estimates. And of course you can alwas crunch it through Cura using nominally similar settings as what you have specified for Slic3r.
@Andre_Frazatto @American_3D_Printing been a while since I used Pronterface (early 2016?) and forgot it can calculate print time. Estimates are actually pretty good, only underestimating by ~6%. @Rudy_Van_Parys ’ suggestion http://gcodeanalyser.com overestimates by the same amount.
Still disappointed that this popular slicer is missing this very basic and essential feature but at least now I can accurately estimate print time. Thanks guys!