Edit: It appears the largest part of the estimate inaccuracy was being caused by animated alembic cache files. If you are going to use these, be aware they may slow down your frame initialization significantly on orc. Your estimates will be wrong if your local machine does not experience this slow initialization. Once I remove the alembic files, the estimates seem to be just about spot on for large renderings, and much closer for animation frames.
Suggestion: The calculator could take the time per frame into consideration as well as the orbx filesize and apply a factor to the estimate for animation frames. If OB/hr is going to be a trusted unit of measurement, it would make sense to avoid unnecessary confusion when using it.
-----------
The estimate provided is around 1/3 of what I am being charged. Also based on my understanding of the pricing model the reality seems to be about 3x the cost i was expecting. Does anyone agree with orc's estimates for animation?
This is purely based on their calculator and my math....I do not see a Run an Estimate button in the interface as the help docs show.
I have read other responses that point to loading/saving time being the culprit. If this is the case, surely otoy can take this into account when estimating (and make that it clear when quoting pricing)
I have sent an email to support and have not heard back in over 24 hours. Is this typical?