Hi,
In the Getting Started video, Matt Chan types in the string "color" into a set_geo_property node.
I do not know what properties exist, so I can't know what strings are meaningful for the Property field.
In the documentation, I could not find a list of what properties exist. How can I know what my options are?? Are they just the attribute names of the Maya node? I tried to hunt down the string "color" in both the mesh shape and transform node documentation, but came up with nothing.
Please help, my mind-reading skills are not sufficient to the task.
Use a watchpoint.
And there is a help tab with a lot of info in the Parameter Editor.
I did use a watchpoint. That only works if the property exists already. If the property has not been added to the graph, the watchpoint can't display it. In order to add the property, I need to know its name.
I also checked the Info panel, but there was nothing there to tell me what properties can potentially be added.
And here is the extremely helpful information found in that Info panel for set_geo_property:
property The name of the property.
Well, I'm glad that's cleared up. 😛
I agree it would be helpful to have a list of default properties for a mesh, volume etc. Especially what it takes to create a valid mesh.
Though you can make any property you like yourself...
It's not just helpful to have a list of default properties... it is absolutely essential.
Someone knows this information, but they did not think to tell the users.
Hi!
About the user experience.
https://forums.autodesk.com/t5/bifrost-forum/using-bifrost-perspective-on-the-current-ux/m-p/8931198
OK, looks like it's in the roadmap somewhere!
Get and Set Property Improvements | Automatically populate a drop-down list with available properties, including type information. |
In the meantime, here's a possibly incomplete list:
// Volume DataGeoProperties voxel_position voxel_fog_density voxel_mass_density voxel_signed_distance voxel_detail_size voxel_acceleration voxel_temperature voxel_ignition_temperature voxel_point_radius voxel_degree_of_freedom voxel_vorticity voxel_expansion_rate voxel_fog_density_signed_distance voxel_flame_level_set voxel_combustion_rate voxel_flame_speed voxel_refinement voxel_significance voxel_fuel voxel_fuel_propane voxel_fuel_ethane voxel_fuel_butane voxel_fuel_methane voxel_fuel_propylene voxel_fuel_propyne voxel_fuel_propadiene voxel_gas_carbon_dioxide voxel_gas_nitrogen voxel_gas_oxygen voxel_gas_vapor // Velocity Data geo porperties... point_velocity voxel_velocity face_velocity face_vertex_velocity // Point DataGeoProperties point_position point_size point_color point_orientation // Strand DataGeoProperties strand_offset point_strand_index point_tangent point_ratio // Mesh DataGeoProperties face_offset face_vertex point_normal point_size point_velocity face_normal face_vertex_normal point_uv face_uv face_vertex_uv
That list of property names, even if it's incomplete, needs to be in the documentation somewhere.
Thanks
Hey, did the list of reserved property names ever get published? I still need this desperately. Running into super confusing situations where, e.g. colors aren't showing up in the viewport, even though they are showing up in Arnold. Managed to stumble over the solution... the property inside set_geo_property needs to be "color" in order for the viewport to see it. I was trying to disambiguate by using the string "geo_color", which worked in aiUserDataColor, but not in VP 2.0.
Really, really, REALLY need a comprehensive list of reserved property names and their functions.
Thanks
Actually, for some nodes we now have a dropdown with possible choices. It's not an exhaustive list though; that would be both too many options and not possible because of custom user properties.
May not be convenient to read, but Bifrost has a dump_object node, which prints out all data into a .txt file.
So a structure like this
results in:
{
detail_size: 0.15 (float)
next_point_id: 12747 (long)
physical_material: 1 (char)
physical_material_int: 1 (int)
point_age:
{
data: [ ... ] 12747 elements (array<float>)
default: 0 (float)
depends_on: [ ] 0 elements (array<string>)
interp: (unknown data type)
target: point_component (string)
}
point_component:
{
count: 12747 (uint)
}
point_dead:
{
data: [ ... ] 12747 elements (array<bool>)
default: 0 (bool)
depends_on: [ ] 0 elements (array<string>)
interp: (unknown data type)
target: point_component (string)
}
...
}
yes...but that lists only existing property names, not all which are reserved for the respective object...
Can't find what you're looking for? Ask the community or share your knowledge.