stratified wrote:Hi Jason,
I think you're getting confused by the rounding errors:
- Code: Select all
Scrubber Time - 0.03999999910593
I think this is frame # 0
The time in Octane is represented in floating point. For example if you have 25 fps, the frame duration is 0.04 seconds. In floating point this is represented as 0.03999... . If you then use math.floor(currentTime / frameTime), you will always underestimate the frame number. What you should do is have an epsilon and if you're close enough to the integer, clamp it to the integer. I know it's subtle but there's not much we can do here.
Yarg, fp errors are a pita! Thanks Thomas.
stratified wrote:It is operating in it's own graph. The turntable animation script takes a copy of the root graph of the project but not of the project itself. But
octane.project.getSceneGraph()will always return the root graph of the original project. You can get around this by getting the parent graph of the scripted graph which is always the correct one.
Cool I will try that.
stratified wrote:Accessing the project settings is the culprit here. I guess the best thing is to always fetch them during evaluation.
I will move that too for now, thanks again.