attribute-bindings

Use persistent attribute bindings to optimize repeated writes to OVRTX prims and attributes. They persist the binding descriptor to avoid repeated setup, improving per-frame performance in animation loops or transform updates.

Per-frame update performance drops because creating repeated writes to the same prims and attributes is expensive, requiring descriptor rebuilds each frame. Persistent attribute bindings solve this by persisting the binding descriptor to avoid repeated setup overhead.

Yes, attribute bindings support per-frame updates in both Python and C/C++. You can apply the bindings to animation loops and per-frame updates, handling repeated writes, maps, and lifecycle management in either language.

The OVRTX APIs needed to bind and write persistent attributes include bind_attribute, bind_array_attribute, write, and map. These APIs handle the binding, writing, and mapping operations, along with proper lifecycle handling to create once and destroy when done.

You should destroy an attribute binding when you are completely done with all repeated writes or maps to those specific prims and attributes. Proper lifecycle handling requires creating the binding once and destroying it when done to manage resources effectively.

The best way to handle lifecycle management for persistent attribute bindings is to create the binding once and destroy it when done. This ensures proper resource cleanup while avoiding repeated setup overhead during continuous per-frame writes.