08-20-2021, 07:12 AM
Thanks!
I haven't been aware, that a shape operator can enable this for cloth.
If someone knows a comprehensive tutorial about the operator compatibilities between physX and cloth and how to troubleshoot them, let me know.
I have seen many, but most only cover one workflow direction and show what is possible but never what is "not possible" and how to deal with it
I have a thought about a feature suggestion:
Couldn't a visual feedback be implemented into the operator stack, to see wheather there is an operator, that does not change the flow at all?
Imagine I put a cloth operator into a physX shape sim.
I guess that Tyflow can easily "see" that this operator doesn't work, when it compares the flow before and after.
So it could mark this operator with a certain color and the user instantly knows, that this operator makes no sense or has currently settings, that make it not working.
Sometimes changes are so small, that you think, an operator is doing something and let it simulate again and again until you realize, it is not.
Or you add three operators, whcih change the simulation drastically, but one of them is not doing anything. Because you only simulate after doing changes to all three of them, it takes a while until you find out.
I haven't been aware, that a shape operator can enable this for cloth.
If someone knows a comprehensive tutorial about the operator compatibilities between physX and cloth and how to troubleshoot them, let me know.
I have seen many, but most only cover one workflow direction and show what is possible but never what is "not possible" and how to deal with it
I have a thought about a feature suggestion:
Couldn't a visual feedback be implemented into the operator stack, to see wheather there is an operator, that does not change the flow at all?
Imagine I put a cloth operator into a physX shape sim.
I guess that Tyflow can easily "see" that this operator doesn't work, when it compares the flow before and after.
So it could mark this operator with a certain color and the user instantly knows, that this operator makes no sense or has currently settings, that make it not working.
Sometimes changes are so small, that you think, an operator is doing something and let it simulate again and again until you realize, it is not.
Or you add three operators, whcih change the simulation drastically, but one of them is not doing anything. Because you only simulate after doing changes to all three of them, it takes a while until you find out.