@chrismakesstuff @KimballArms @Lumpy @jwoody18
I realize, Chris, that you posed your question only to Jeff, but since you included me in the targeted list of recipients, I figured that I would throw my 2 cents worth in.
I played for a while with the factor setting in VCarvePro - comparing its time estimates to actuals - and could never come up with a factor that held true for all toolpaths. In particular, 3D carving was really hit and miss, given all the Z movements. As you know, we can set X and Y to run at a given speed, but if the Z movement is slower, all of the movements default to the slowest speed.
For me, VCP was pretty close on toolpaths like simple profiles and pockets, so it seemed pointless to mess with the settings to get them to better reflect real time runs for 3D carves, only to negatively affect the estimates for those simpler toolpaths.
I believe, too, that trying to come up with factors that others could use would be a daunting task. There are so many variables between users. Feed rates, plunge rates, ramp lengths, safe Z heights, and even project size compared to material size will all affect how accurate the VCP estimate is.
I confess that all this is much beyond me, which is why, I guess, I gave up on it. Thankfully, I don’t need take into account any of the factors that Jeff mentions in his previous explanatory post, so the fact that VCP’s estimates are frequently off is not a game changer for me.
I refer here to VCP, but I’m assuming that the challenge will be same regardless of the CAM program.
As an aside, this is also an issue for gSender. I frequently start a job and gS shows it will take many, many hours to complete. However, within a few minutes, those hours and hours disappear in favour of a more realistic time span. Then, it can occur that, after settling down, the estimate goes up again. I am not even close to being competent enough to understand what it going on under gS’s hood, but it can be unnerving on some jobs until it settles down.