Skip to content

Conversation

@cameronwhite
Copy link
Contributor

Description of Change(s)

For the example file in the referenced bug report, the Alembic property has the metadata arrayExtent: 3, podExtent: 1, podName: float32_t.
This was translated into a float[] array with too many elements since the arrayExtent was ignored. This metadata seems to have an equivalent meaning to USD's elementSize, describing a grouping of consecutive elements in the array.

Houdini's Alembic exporter, for example, uses this in the generic case for translating float tuple attributes (which might have an arbitrary tuple size) if they're not a standard type like positions or colors.

(Note that if the property instead had metadata arrayExtent:1, podExtent:3, this behaved correctly as-is and would translate into a float3[] array)

Link to proposal (if applicable)

N/A

Fixes Issue(s)

Fixes: #3362

Checklist

These values are equivalent and describe how consecutive array elements
should be grouped.

This is used, for example, by Houdini's Alembic exporter to translate
float tuples that aren't standard data types such as positions or colors.

Fixes: PixarAnimationStudios#3362
@jesschimein
Copy link
Collaborator

Filed as internal issue #USD-11727

(This is an automated message. See here for more information.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Alembic importer bring in 3 float attribute as single float

2 participants