Assigning materials to different geometries loaded as one sop
3698 4 1-
- asrgnii
- Member
- 24 posts
- Joined: July 2022
- Offline
HI! I'm running into a couple of issues when assigning materials and importing from a SOP context.
Firstly, I understand that I did not correctly create NULL for each geometry to send to Solaris. If I merge the geometry via MERGE and output to NULL, then I get one merged geometry, to which I assign the material through the shader principal. So I don’t understand how to fix the problem so that I can load the geometry via SOP Import and be able to assign the material to EVERY element individually.
Secondly, there is a problem that the OUT_pillows pads interact as needed with each other, through the force of popaxisforce, but as soon as I load another geometry, it starts to pass through each other, how to solve this problem?
Firstly, I understand that I did not correctly create NULL for each geometry to send to Solaris. If I merge the geometry via MERGE and output to NULL, then I get one merged geometry, to which I assign the material through the shader principal. So I don’t understand how to fix the problem so that I can load the geometry via SOP Import and be able to assign the material to EVERY element individually.
Secondly, there is a problem that the OUT_pillows pads interact as needed with each other, through the force of popaxisforce, but as soon as I load another geometry, it starts to pass through each other, how to solve this problem?
Edited by asrgnii - March 5, 2023 14:18:56
-
- jsmack
- Member
- 8252 posts
- Joined: Sept. 2011
- Online
-
- asrgnii
- Member
- 24 posts
- Joined: July 2022
- Offline
jsmack
Use the name or path attribute to partition the geometry for import. Multiple imports is unnecessary.
That is, do I understand you correctly, you are saying that after each geometry, before putting it into Vellum Solver, add a name node and give each mesh a name ??? So that in Solaris, when importing the entire scene, I could refer to each mesh and import through the group?
-
- jsmack
- Member
- 8252 posts
- Joined: Sept. 2011
- Online
asrgnii
That is, do I understand you correctly, you are saying that after each geometry, before putting it into Vellum Solver, add a name node and give each mesh a name ???
Before importing to Solaris, add a name attribute to each part to be treated separately.
asrgnii
So that in Solaris, when importing the entire scene, I could refer to each mesh and import through the group?
The name tells the sop import to put each uniquely named part under a different primitive. This allows assigning a different material for each primitive using the primitives field on the material assign node.
An alternative to using name attributes is to assign the materials in SOPs and use the SOP import to bind and create the materials using geometry subsets.
-
- asrgnii
- Member
- 24 posts
- Joined: July 2022
- Offline
-
- Quick Links

