Attribute Workflow *FIXED

Forums: Attribute Workflow *FIXED
Houdini Integrated Plugin

Moderator: juanjgon

Attribute Workflow *FIXED

Postby daryl.dunlap » Thu Jan 03, 2019 1:10 am

daryl.dunlap Thu Jan 03, 2019 1:10 am
Maybe not a bug, per-se, but, its not intuitive as it currently exists...

In the OBJ params, params are labeled Point Attributes, and only list Point attributes for selection for extraction in the drop-down. However, in the /mat context, the VOP nodes to consume the Point Attributes are labeled as <*> Vertex Attributes.

Is this intentional or some design restriction?
Last edited by daryl.dunlap on Fri Feb 01, 2019 3:15 am, edited 1 time in total.
daryl.dunlap
Licensed Customer
Licensed Customer
 
Posts: 12
Joined: Wed Dec 26, 2018 7:29 pm

Re: Attribute Workflow

Postby juanjgon » Thu Jan 03, 2019 10:13 am

juanjgon Thu Jan 03, 2019 10:13 am
Hi Daryl,

Currently, Octane only supports point level attributes (one value for each object point, not for each point of each polygon), although internally in Octane they are called "vertex" attributes, so I suppose that this is why the VOP node has this name.

Thanks,
-Juanjo
Computer Graphics Software Developer
Octane plugin development and support: LightWave and Houdini
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 6880
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Re: Attribute Workflow

Postby daryl.dunlap » Thu Jan 03, 2019 2:12 pm

daryl.dunlap Thu Jan 03, 2019 2:12 pm
I do understand that the internal name in the Octane API is 'vertex attributes', but since the implementation is actually 'point attributes' is there any hurdle to labeling the VOP nodes as 'point attributes' in the tool (Houdini)?

Since, if I understand you correctly, you cant actually consume vertex attributes.
daryl.dunlap
Licensed Customer
Licensed Customer
 
Posts: 12
Joined: Wed Dec 26, 2018 7:29 pm

Re: Attribute Workflow

Postby juanjgon » Thu Jan 03, 2019 2:30 pm

juanjgon Thu Jan 03, 2019 2:30 pm
All the VOP nodes names, parameter names, default values, etc. come from the Octane API to be sure that everything is the same across all the DCCs and the Standalone. I could hardcode the VOP node names in the Houdini plugin, but it is not a good idea at all, because some features, like the LiveDB or the future .orbx proxy referencing could be broken.

In any case, in the future Octane could add proper support for real vertex level attributes, probably retrieved using the same VOP node ... at this point, the VOP node name is going to have more sense ;)

Thanks,
-Juanjo
Computer Graphics Software Developer
Octane plugin development and support: LightWave and Houdini
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 6880
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Re: Attribute Workflow

Postby daryl.dunlap » Thu Jan 03, 2019 3:17 pm

daryl.dunlap Thu Jan 03, 2019 3:17 pm
Agreed.
daryl.dunlap
Licensed Customer
Licensed Customer
 
Posts: 12
Joined: Wed Dec 26, 2018 7:29 pm

Re: Attribute Workflow

Postby abstrax » Fri Jan 04, 2019 12:42 am

abstrax Fri Jan 04, 2019 12:42 am
Please bear with my lack of knowledge about Houdini, but if I understand you correctly, you would prefer to specify different vertex attributes for shared vertices, depending on the polygon that shares the vertex? I.e. similar to UV coordinates and normals?
Just want to confirm, because we can do that fairly easily since on the GPU side we already store the attributes per primitive, but have to change it now to avoid issues with the backwards compatibility of scenes later.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
User avatar
abstrax
OctaneRender Team
OctaneRender Team
 
Posts: 5069
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

Re: Attribute Workflow

Postby daryl.dunlap » Fri Jan 04, 2019 1:47 am

daryl.dunlap Fri Jan 04, 2019 1:47 am
Houdini has 4 levels of attributes, listed here based on data priority: Point -> Vertex -> Primitive -> Detail.

As described by this image: Image

So Yes, Vertex Attributes (similar to UV data) would be very helpful in allowing the Houdini plugin developer to support more levels of attribute data, intuitively.

Thanks guys.
daryl.dunlap
Licensed Customer
Licensed Customer
 
Posts: 12
Joined: Wed Dec 26, 2018 7:29 pm

Re: Attribute Workflow

Postby abstrax » Fri Jan 04, 2019 1:50 am

abstrax Fri Jan 04, 2019 1:50 am
Got it. If nothing goes wrong, we will change it with the next build.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
User avatar
abstrax
OctaneRender Team
OctaneRender Team
 
Posts: 5069
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

Re: Attribute Workflow

Postby blobbybarack » Fri Jan 04, 2019 7:08 pm

blobbybarack Fri Jan 04, 2019 7:08 pm
Will be great to be able to use string attribute too with a RGB texture like.
blobbybarack
Licensed Customer
Licensed Customer
 
Posts: 195
Joined: Sun Feb 03, 2013 9:11 pm
Location: Paris

Re: Attribute Workflow

Postby aLeXXtoR » Sun Jan 06, 2019 2:57 pm

aLeXXtoR Sun Jan 06, 2019 2:57 pm
Could you please help me with the primitive color attribute — what setup I must do in Houdini to use that colors with my mesh material?

Image
Image
Win 10 Pro 64bit | GeForce GTX 1660 Ti | AMD Ryzen 7 3700X | 32GB RAM
WebSite
Showreel
User avatar
aLeXXtoR
Licensed Customer
Licensed Customer
 
Posts: 270
Joined: Sat Oct 29, 2011 5:38 pm
Location: Russia, St. Ptetersburg
Next

Return to Houdini


Who is online

Users browsing this forum: No registered users and 1 guest

Mon Sep 16, 2019 8:55 am [ UTC ]