stratified wrote:You should use graph.time
instead of rootGraph.time
, The time in the document is updated bottom-up. This means that the scripted graph is updated first and then the root graph. The callbacks are done as soon as the scripted graph is updated but at that point the root graph isn't updated yet and hence has still the old time stamp.
Thanks Thomas, that makes sense, unfortunately I'm still getting the lag after I changed the code to use graph instead of the root graph. Here is an updated test script:
stratified wrote:I haven't tested this but the turntable animation takes a copy of the full scene but your graph script still grabs the original root graph on initialization. So I think you're always querying the time of the original unmodified project.
Ah, that makes sense too.
So when you copy the root graph the script node doesn't get copied as well? I just tested it with the new script that uses graph but it doesn't get updated as well. I'm still missing an understanding of what goes on underneath. I guess I was assuming that when the graph was copied it would operate like a completely separate graph in it's own space per se?
stratified wrote:The crash is a bug in Octane you uncovered. It happens when you tried to access the root graph of the project while the project is still loading. You can work around this by refraining from doing anything with the root node graph in the onInit
function.
I removed all of the references to the root graph in onInit but it's still locking Octane up.
Here are the new files I'm using:
Edit: Or is the get project settings also affecting it?