@arhi said in Time Estimates Idea:
simulatedTime? Is this time calculated like pushing file trough the actual RRF system simulating how fast it would exec it or?
That's right. You can run a simulated print and it will do a faster than real time run through of the entire gcode file. Don't interact with the duet during the simulation. It's much faster than real time, but with really long multi-day prints it's still going to take a long time to simulate.
I've found that PrusaSlicer and Cura are already really accurate with their estimates when you're setting the acceleration and jerk values in the slicer. Cura also has a printer settings plugin that lets you set max feedrates etc. I find them to be within 20 minutes on a long print. Which is the same as the amount of time it might take to simulate it first.