Jump to content
Sign in to follow this  
Linwood

Different result between VEX and vopsop

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

Share this post


Link to post
Share on other sites
Two ways in wrangle

 

1. append v before @side

rotate(rot, rot_mul ,v@side)

 

2. or declare before using as variable.

 

vector side = v@side;

rotate(rot, rot_mul , @side);

 

 

Cheers!

Share this post


Link to post
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

Share this post


Link to post
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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×