Jump to content

AttributeVOP - Not working as expected...


cwalrus

Recommended Posts

You had created the v attribute on the points. The attribVOP was looking for it on the primitives. 

 

I used an attribute promote SOP to put the velocity data onto the primitives so it could be read in the attribVOP

 

The other thing I added in the attibVOP was a bind export node so I could measure the length of the velocity vector to set the fit range node correctly. You had it set to -1 to 1 I think. The full velocity range was around 0 to 42.

 

Destruction_01.hipnc

  • Like 1
Link to comment
Share on other sites

Couldn´t have a look on the file at the moment but you can export the length of the the vector via a bind export as a geometry attribute and have a look on that in the geometry spreadsheet. So he knew how to set the parameters on the fit range. As rich_lord already wrote.

 

 

so I could measure the length of the velocity vector to set the fit range node correctly. You had it set to -1 to 1 I think. The full velocity range was around 0 to 42.

@rich_lord 

pls correct me if I´m wrong.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...