Problems creating user mesh property (masterclass tutorial)

Problems creating user mesh property (masterclass tutorial)

Anonymous
Not applicable
955 Views
10 Replies
Message 1 of 11

Problems creating user mesh property (masterclass tutorial)

Anonymous
Not applicable

Hey All-

 

Having problems creating a mesh user property while following the masterclass tutorial video. I have attached an image displaying my network.  You can see I add a property to the mesh called "relative_point_pos" and a watchpoint shows that there is data entering the set_geo_property but when I try to get the property immediately after another watchpoint shows there is no data.  I have tried setting a variety of data types but no luck.  Any thoughts?

 

Thanks,

Rick

 

bifrost_help.png

0 Likes
Accepted solutions (1)
956 Views
10 Replies
Replies (10)
Message 2 of 11

Anonymous
Not applicable

Following up on this. The type wants to be array<Math::double3> when getting and setting values in get_geo_property and set_geo_property for my data.  There is no way to set that type through the node UI.  The only way I was able to solve this was to pipe the data into the "type" port and let the node figure it out.

0 Likes
Message 3 of 11

Anonymous
Not applicable

Sorry,not quite correct (and this is driving me crazy).  See attached images. I was able to set the data type as array<Math::float3> earlier in my tree which is selectable as a type in get/set nodes.  Notice that in both instances Bifrost sees the data as float3 but only the version with the connected array to "type" passes any values.  bifrost_connected.pngbifrost_unconnected.png

0 Likes
Message 4 of 11

morten.bojsen-hansen
Autodesk
Autodesk

Can you share your scene? Then I can have a look. You need to be sure that both types are set to array<Math::float3>. You can see the type by middle-clicking on the port.

0 Likes
Message 5 of 11

Anonymous
Not applicable

The type is set to array<math::Float3>but for some reason wants a connection to determine the type.  I have shared my workfile.  In the Bifrost graph editor under the tab for "drive_meshes_with_face_points" there is a node called "get geo relative point pos" that has an input into its type plug and a watchpoint after the node.  Notice that when disconnecting the plug there is no longer any data in the watchpoint even though the type is still correct.  Thanks.

 

 

Having troubles attaching a scene file.  Any hints?  Getting this error-

 

Correct the highlighted errors and try again.

  • The attachment's bifrost_tut.mb content type (application/octet-stream) does not match its file extension and has been removed.

 

 

0 Likes
Message 6 of 11

Anonymous
Not applicable

Looks like I need to zip the scene file first....

0 Likes
Message 7 of 11

syracoj
Autodesk
Autodesk

I recreated new set and get geo_prop nodes and it seems to be working now.

When I turned on the display of the node type (pressing t on the keyboard) it revealed the set and get nodes as type compound. They should have revealed that they were of type set_geo_property and get_geo_property compound nodes.

 

theseCompoundsMayHaveBeenBad.png

Message 8 of 11

Anonymous
Not applicable

I had probably set the get/set nodes to editable to see if I could debug so they were showing up as compound. Unfortunately replacing those nodes does not fix my problem.  I have a feeling it might be might a Maya 2019 thing.  IT owns the install on my machine and will get them to version up to 2020 to see if that fixes it.

 

replace.png

0 Likes
Message 9 of 11

syracoj
Autodesk
Autodesk

which version of bifrost and RPOA are you using again? Is this the latest?

0 Likes
Message 10 of 11

jonah.friedman
Community Manager
Community Manager
Accepted solution

This graph looks correct to me. I think maybe the issue is that without a connection to the output, watchpoints don't actually work. Your data connection there is going to the out port of a compound called "make disjoint mesh", which is not necessarily being pulled. 

 

Here's a workaround - assuming the object connection there is being pulled. The set property is a temp node just to ensure the data is pulled. Another workaround is to use dump_object to put it into a text file. 

 

watchpoint_workaround.PNG

Jonah Friedman
Bifrost Product Manager
0 Likes
Message 11 of 11

Anonymous
Not applicable

This worked for me. Looking further downstream the data was getting propagated. That watchpoint was not being updated. Thanks

0 Likes