Skip to content

Conversation

@davidsminor
Copy link
Contributor

It turns out that if you give the SXExecutor a V3fVectorData parameter called "v", it complains at you, as it thinks "v" is a texture coordinate and demands a FloatVectorData instead. This caused puzzlement when a lighter tried to use SX to scale a velocity primvar called "v", so I've changed the logic a bit.

It turns out that if you give the SXExecutor a V3fVectorData parameter called "v", it complains at you, as it thinks "v" is a texture coordinate and demands a FloatVectorData instead. This caused puzzlement when a lighter tried to use SX to scale a velocity primvar called "v", so I've changed the logic a bit.
johnhaddon added a commit that referenced this pull request Jun 18, 2015
Changed SXExecutor parameter interpretation
@johnhaddon johnhaddon merged commit e45ac17 into ImageEngine:master Jun 18, 2015
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.

2 participants