You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Time varying attributes - transforms, positions, normals or others we will need in the future - are sampled inconsistently and I think they should go behind the same interface similarly to HdCyclesSetTransform.
You make no assumptions about the samples/times are received
You approximate the input using a (configurable) number of samples which linearly interpolates them and formats them as Cycles like.
IMHO, this is something that should go inside Cycles and exposed through something like set_timevarying_attributes(times, samples).
I would say this has less priority than making the Sync process more parallel.
The text was updated successfully, but these errors were encountered:
Time varying attributes - transforms, positions, normals or others we will need in the future - are sampled inconsistently and I think they should go behind the same interface similarly to
HdCyclesSetTransform
.IMHO, this is something that should go inside Cycles and exposed through something like
set_timevarying_attributes(times, samples)
.I would say this has less priority than making the Sync process more parallel.
The text was updated successfully, but these errors were encountered: