usdgeom-mesh-identical-timesamples

Code	VG.015
Validator
Compatibility	core usd
Tags	🚀

Summary

Use time samples only when attribute values change

Why is it required?

• Playback performance issues

• Memory inefficiency.

  While binary “crate” USD layers may reduce the impact through de-duplication, this doesn’t fully solve the problem. Downstream systems like renderers may still experience memory inefficiencies when they don’t perform the same de-duplication and allocate unnecessary temporary buffers.

Examples

#usda 1.0

# Invalid: Identical time samples
def Mesh "MeshWithIdenticalTimeSamples" {
    uniform token subdivisionScheme = "none"
    int[] faceVertexCounts = [4]
    int[] faceVertexIndices = [0, 1, 2, 3]
    point3f[] points.timeSamples = {
        1: [(0.0, 0.0, 0.0), (1.0, 0.0, 0.0), (1.0, 1.0, 0.0), (0.0, 1.0, 0.0)],
        2: [(0.0, 0.0, 0.0), (1.0, 0.0, 0.0), (1.0, 1.0, 0.0), (0.0, 1.0, 0.0)]
    }
}

# Valid: No time samples
def Mesh "MeshWithoutTimeSamples" {
    uniform token subdivisionScheme = "none"
    int[] faceVertexCounts = [4]
    int[] faceVertexIndices = [0, 1, 2, 3]
    point3f[] points = [(0.0, 0.0, 0.0), (1.0, 0.0, 0.0), (1.0, 1.0, 0.0), (0.0, 1.0, 0.0)]
}


# Invalid: Some Identical time samples
def Mesh "MeshWithSomeIdenticalTimeSamples" {
    uniform token subdivisionScheme = "none"
    int[] faceVertexCounts = [4]
    int[] faceVertexIndices = [0, 1, 2, 3]
    point3f[] points.timeSamples = {
        1: [(0.0, 0.0, 0.0), (1.0, 0.0, 0.0), (1.0, 1.0, 0.0), (0.0, 1.0, 0.0)],
        2: [(0.0, 0.0, 0.0), (1.0, 0.0, 0.0), (1.0, 1.0, 0.0), (0.0, 1.0, 0.0)],
        3: [(1.0, 0.0, 0.0), (2.0, 0.0, 0.0), (2.0, 1.0, 0.0), (1.0, 1.0, 0.0)],
        4: [(0.0, 0.0, 0.0), (1.0, 0.0, 0.0), (1.0, 1.0, 0.0), (0.0, 1.0, 0.0)]
    }
}

# Valid: No sequential identical time samples
def Mesh "MeshWithoutIdenticalTimeSamples" {
    uniform token subdivisionScheme = "none"
    int[] faceVertexCounts = [4]
    int[] faceVertexIndices = [0, 1, 2, 3]
    point3f[] points.timeSamples = {
        2: [(0.0, 0.0, 0.0), (1.0, 0.0, 0.0), (1.0, 1.0, 0.0), (0.0, 1.0, 0.0)],
        3: [(1.0, 0.0, 0.0), (2.0, 0.0, 0.0), (2.0, 1.0, 0.0), (1.0, 1.0, 0.0)],
        4: [(0.0, 0.0, 0.0), (1.0, 0.0, 0.0), (1.0, 1.0, 0.0), (0.0, 1.0, 0.0)] 
    }
}

# Invalid: Only one time sample
def Mesh "MeshWithOneTimeSample" {
    uniform token subdivisionScheme = "none"
    int[] faceVertexCounts = [4]
    int[] faceVertexIndices = [0, 1, 2, 3]
    point3f[] points.timeSamples = {
        1: [(0.0, 0.0, 0.0), (1.0, 0.0, 0.0), (1.0, 1.0, 0.0), (0.0, 1.0, 0.0)]
    }
}

How to comply

• Remove animation (time samples) from static attributes / meshes

• Remove redundant time samples from animated meshes, for example with the Scene Optimizer in Omniverse

• For developers: Use UsdUtilsSparseValueWriter to write time samples in a sparse manner.

• For Meshes with only one time sample, validators should warn and offer to move the time sample to the default field of the layer. Remaining time samples should be blocked or removed to avoid accidentally exposing a weaker opinion.