How to use set_geo_property_data for a property_proxy_field?

[andrea_pinto82]

Hi I was trying these days the property_proxy_field.
I thought I could use any property that's happening in simulation as field.
But when I use set_geo_property_data in the simulation doesn't happens anything with the property_proxy_field.
Instead if I use vary_source_property to randomize property it's works.

What am I doing wrong?

thanks

Andrea

property_proxy_field

[andrea_pinto82]

Hi I was trying these days the property_proxy_field.
I thought I could use any property that's happening in simulation as field.
But when I use set_geo_property_data in the simulation doesn't happens anything with the property_proxy_field.
Instead if I use vary_source_property to randomize property it's works.

What am I doing wrong?

thanks

Andrea

property_proxy_field

[andrea_pinto82]

If I use set_geo_property_data inside solve_particles it's works.
Is it the right way?

solve_particles

[andrea_pinto82]

If I use set_geo_property_data inside solve_particles it's works.
Is it the right way?

solve_particles

[brinsmeadd]

I'm not sure exactly what you are trying to do. The proxy field will let you access values for some per particle simulation property, like point_size, point_velocity, or any custom property you may have added through additional_properties. The influence_set_property will set values on any property that is part of the simulation... it will not create properties(for that add a set_property of the initial value and connect to addition_properties on the source). The setting of the geo property downstream of the simulate will work, but you need to make sure that the size of the random array matches the size of the of the geo( get_point_count ). Also if you set the value downstream the values do not feed back into the simulation( though they might be useful for things like rendering ). 

So if you want to add some custom dynamic property, create set_property for it and connect to additional_properties, then to modify each step use influence_set_property (and potentially property_proxy_field nodes to base the value on current simulation properties, including the one added).

Also with the latest version of bifrost the set_property (for the source) can be to a field (will create float property) or a vector field (float3 property), allowing you to better control the initial value at emit time.

[brinsmeadd]

I'm not sure exactly what you are trying to do. The proxy field will let you access values for some per particle simulation property, like point_size, point_velocity, or any custom property you may have added through additional_properties. The influence_set_property will set values on any property that is part of the simulation... it will not create properties(for that add a set_property of the initial value and connect to addition_properties on the source). The setting of the geo property downstream of the simulate will work, but you need to make sure that the size of the random array matches the size of the of the geo( get_point_count ). Also if you set the value downstream the values do not feed back into the simulation( though they might be useful for things like rendering ). 

So if you want to add some custom dynamic property, create set_property for it and connect to additional_properties, then to modify each step use influence_set_property (and potentially property_proxy_field nodes to base the value on current simulation properties, including the one added).

Also with the latest version of bifrost the set_property (for the source) can be to a field (will create float property) or a vector field (float3 property), allowing you to better control the initial value at emit time.

[andrea_pinto82]

Thanks brinsmeadd for your reply.

Yes, I already did it like you said.

My problem was that I didn't have the property inside the simulation.
Finally I calculate the property inside solve_particles.

I created a force for separation and cohesion

https://vimeo.com/576121470

bif_field_sep_coh

[andrea_pinto82]

Thanks brinsmeadd for your reply.

Yes, I already did it like you said.

My problem was that I didn't have the property inside the simulation.
Finally I calculate the property inside solve_particles.

I created a force for separation and cohesion

https://vimeo.com/576121470

bif_field_sep_coh