It looks like you're new here. If you want to get involved, click one of these buttons!
After working with Fabric for a long time, I am still unsure how a graph should access 'time'.
On the one hand, we have the EvalContext, which has a time parameter. When I found this, I assumed that it is the way to access host time. Nice and easy.
However, most of the sample graphs rely on the input "timeline" parameter, which is a regular port that most (but, er... not all) DCC's automatically hook up to be driven by their own timelines.
I appreciate that time is a parameter, just like any other. Except it's not, because you don't want the user seeing it/messing with it in the UI. Internally, any preset should accept time as an argument rather than accessing a global. However, shouldn't a root-level graph just use the EvalContext?
What is the recommended method of accessing a host apps time? It should be consistent across all DCC's if Fabric is truly write-once, run-anywhere.
And would it be possible to get rid of the other (non-recommended) method to make things just a bit cleaner/clearer?
©Copyright 2017 Fabric Software Inc. All rights reserved. | Privacy