Hello, why I can't see the scalar field visualization in the viewport?
Do you have any idea why?

Hi, tried a similar setup, seem to be when ever a new reference field is attached to Gas Math Field, it overwrites the existing values - which shouldn't as the description says only the size and resolution. I can't see the whole setup, but if you intend to control the stick field with a mask, you can import that with the sop scalar field.



Take a look at the hip file.

viklc
Hi, tried a similar setup, seem to be when ever a new reference field is attached to Gas Math Field, it overwrites the existing values - which shouldn't as the description says only the size and resolution. I can't see the whole setup, but if you intend to control the stick field with a mask, you can import that with the sop scalar field.



Take a look at the hip file.

https://drive.google.com/file/d/1ltcYVTAYvsw3I271Zsnx1SvOuL8vI2Ke/view?usp=sharing [drive.google.com]]
Thank you, I will try, here is a simplify file ( too big to to join here)

viklc
Hi, tried a similar setup, seem to be when ever a new reference field is attached to Gas Math Field, it overwrites the existing values - which shouldn't as the description says only the size and resolution. I can't see the whole setup, but if you intend to control the stick field with a mask, you can import that with the sop scalar field.



Take a look at the hip file.

It works but I don't understand why it was not working with my setup...
Look the file reference I had...

Image Not Found

Activating the stick field in the solver only means that the data should be obtained from the field with the specified name, stick by default. The gas match field therefore does not pretend to transfer attribute data, only takes the resolution and size of the specified reference field.

You have first initialize a field, using the scalar field sop for example - which can take the volume data from the sops. There are several ways to get data from the SOPs, by binding data with the gas field wrangle, the volume source or again the SOP scalar/vector field. You can then look in your spreadsheet to see if the field is successfully listed there.

You can also create a new field directly in the DOPs with the scalar/vector field ops and write the attribute data with the gas wrangle.

viklc
Activating the stick field in the solver only means that the data should be obtained from the field with the specified name, stick by default. The gas match field therefore does not pretend to transfer attribute data, only takes the resolution and size of the specified reference field.

Image Not Found

You have first initialize a field, using the scalar field sop for example - which can take the volume data from the sops. There are several ways to get data from the SOPs, by binding data with the gas field wrangle, the volume source or again the SOP scalar/vector field. You can then look in your spreadsheet to see if the field is successfully listed there.

Image Not Found

You can also create a new field directly in the DOPs with the scalar/vector field ops and write the attribute data with the gas wrangle.

Thank you for helping, do you have some printscreen explaining this?

Here is an updated version of the simplify hip. Take a look at the dops, there are some notes and all the important nodes are highlighted in red. In this setup I used a volume source to import the volume from sops and put the data in the stick field created with the scalarfield op.

viklc
Here is an updated version of the simplify hip. Take a look at the dops, there are some notes and all the important nodes are highlighted in red. In this setup I used a volume source to import the volume from sops and put the data in the stick field created with the scalarfield op.

Image Not Found

Image Not Found

It works very well, thank you, I have to learn to do this by myself, thank you so much!
Otherwise, Do you think volume collider works fine? I have no resolution during the sim even with hight value? I was hesitating to use static object instead!

By default, the collision field resolution is the same as the particle separation specified in the flip object. If you are fine with the particle resolution but not with the collision, you can turn on collision separation and set a higher value.


The collision type is highly dependent on the use case. But as the name suggests, static collision for colliders that have no movement or deformation. If your sim is driven by a collision, then volume collisions are probably the better choice as they directly affect the velocity field. If you use volume collisions, make sure that the collision detection is set to "Move outside collision". Otherwise, the particles could pass through the collision volume.

Sebastien Levieux
I have no resolution during the sim even with hight value?

Check whether the volume resolution from the Sops meets your preferences.

viklc
By default, the collision field resolution is the same as the particle separation specified in the flip object. If you are fine with the particle resolution but not with the collision, you can turn on collision separation and set a higher value.


The collision type is highly dependent on the use case. But as the name suggests, static collision for colliders that have no movement or deformation. If your sim is driven by a collision, then volume collisions are probably the better choice as they directly affect the velocity field. If you use volume collisions, make sure that the collision detection is set to "Move outside collision". Otherwise, the particles could pass through the collision volume.

Thank you so much for all your explanations, that's make everything clearer!! I wish I can solve and make it great!

There is a lot of trial and error in dops as there are some many parameters that rely on each other. It takes some time to get in the right direction - just keep going