Jump to content

Different result between VEX and vopsop


Linwood

Recommended Posts

Hi mates
this is my first post topic in here,  
recently, I start to practice basic scripting on VEX,
and I try to practice some example from vopsop to pointwrangle,
but in this case , I get the different result in the same things,
I dont know what's wrong in here,
so I hope someone might might check my file and  please tell why I got the different in this case,

thank so much !!!

post-9521-0-54701000-1442309005_thumb.jp

post-9521-0-32135000-1442309007_thumb.jp

practice.hipnc

Link to comment
Share on other sites

Thank you!! Gaurav !!!

But I don't understand why I need to define "@side" is vector again ? 

does it not inherit the type from parents node!?

If I need to do it again , why the "@up" and "@N" don't have this problem !?

 

thank for your reply ,  cheers  :)

Edited by Linwood
Link to comment
Share on other sites

you need to define the type as you need to let houdini know what type of values it will be dealing with so it can give you proper debugging info

 

certain attributes are simply assumed to be certain types as they are commonly used in various places in houdini

https://www.sidefx.com/docs/houdini14.0/vex/snippets#attributes

so it's just convenience

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...