Yesterday, 09:52 PM
(This post was last modified: Yesterday, 10:08 PM by josemendez.)
Hi!
Decimation doesn’t replace the old proxies system - it’s more of an addition to it. The replacement for proxies is the new cloth rendering and skinning system, which is a simpler, more performant and streamlined encarnation of proxies: https://obi.virtualmethodstudio.com/manu...modes.html
ObiClothRenderer now takes an ObiCloth as input and will bind that object’s mesh to the cloth, same as proxies did. *Any* mesh can be bound to an ObiCloth actor, it may be the same used to generate the cloth blueprint or may be an entirely different one. The ObiCloth and the ObiClothRenderer do not need to be on the same object, in fact you can have multiple meshes bound to the same cloth.
For the common use case of low-poly mesh for cloth blueprint & high-poly mesh for rendering, you can still use entirely hand-crafted meshes as you used to with proxies. However, decimation comes in handy when you only have a high-poly mesh and want a quick, automatic low-poly version of it to generate the cloth blueprint. This doesn’t stop you from using a custom low-poly mesh with carefully designed topology.
Setting global wind in the solver is more efficient, as it skips the need to determine whether object particles are inside the force zone or not - it simply affects all particles. This is the equivalent of the old ambient force zone.
Let me know if you need further help,
kind regards
Decimation doesn’t replace the old proxies system - it’s more of an addition to it. The replacement for proxies is the new cloth rendering and skinning system, which is a simpler, more performant and streamlined encarnation of proxies: https://obi.virtualmethodstudio.com/manu...modes.html
ObiClothRenderer now takes an ObiCloth as input and will bind that object’s mesh to the cloth, same as proxies did. *Any* mesh can be bound to an ObiCloth actor, it may be the same used to generate the cloth blueprint or may be an entirely different one. The ObiCloth and the ObiClothRenderer do not need to be on the same object, in fact you can have multiple meshes bound to the same cloth.
For the common use case of low-poly mesh for cloth blueprint & high-poly mesh for rendering, you can still use entirely hand-crafted meshes as you used to with proxies. However, decimation comes in handy when you only have a high-poly mesh and want a quick, automatic low-poly version of it to generate the cloth blueprint. This doesn’t stop you from using a custom low-poly mesh with carefully designed topology.
Quote:Secondly, it seems that ambient force zones have been removed -- is it preferred to have a wind force zone follow affected objects around, or to set wind directly through the solver?
Setting global wind in the solver is more efficient, as it skips the need to determine whether object particles are inside the force zone or not - it simply affects all particles. This is the equivalent of the old ambient force zone.
Let me know if you need further help,
kind regards