SUGGESTION: Print finish time in sliced info  

RE: SUGGESTION: Print finish time in sliced info

Maybe I'm missing something but how would the slicer know when you want to start the job? Should it just assume now? Many of us slice and send gcode to printers way in advance of when we want to print. and seeing a meaningless finish time would be, well, meaningless. The slicer already shows you print time, so all it takes is basic math.

RE:

The start time is not important, but if people finds that useful we could maybe have a start time field also or just a sentence like "If you where to start the job now, it will be finished approximately 10.05". And the whole thing could be a settings choice, to show or not show.

Sometimes when full production from different customers on many machines is going on, it is important to know if the job is finished 16.00 or 17.20.
But juggling many machines and several jobs in a long row for weeks, puts one more source of error in even the basic math to find the finish times. 

A typical example of where it is convenient to have the info in the system instead of your head.

RE: SUGGESTION: Print finish time in sliced info

FoxRun3D said it perfectly.  When the slicer slices the file, how does in know if the file is going to be used once or a dozen times?  How would that time be put in the file.  Example, yesterday I printed a file I created last year. 

All my files have the estimated print time on them.  I set a timer on my phone to give me a heads up when it is close to done.

For multiple printers, I would be using a remote monitor and alarms. I monitor my single printer through Octoprint and its time calculations are wrong but get closer as the print finishes.  There might be a way to have a program read the time left from the printer control board remotely.