Hi list,
Is there anyone but me that has noticed that the StrandVelocity value from Strand Dynamics Framework is to weak?
More exactly, its the Simulate Strand using Verlet Integration compound that is broken.
I also checked the Simulate Mesh using Verlet Integration and it also has the same error.
So the compounds affected by this should be these three:
Strand Dynamics Framework (StrandVelocity)
Simulate Mesh using Verlet Integration (PointVelocity)
Verlet Framework (PointVelocity)
It could be more compounds also but these was the ones I found quickly.
Anyway, the fix is to just Divide the value by Frame Step, see attached screen.
Hope this can be fixed to the next release.
Another question to AD: Are the Verlet compounds going to be updated to use the Simulation Subframe Sampling instead of the integrated Iteration to unify the workflow?
Right now the strands freak out when using the Subframe Sampling.
Cheers,
Jens
--
Jens Lindgren
--------------------------
Lead Technical Director