A very simple setup. The stiffness in the solver should always be 1.00 per the expressions. Somehow the mop-falloff still has an effect over the bend stiffness.
What did I think wrong?
Please explain.
I am on MacOS ARM 19.5.330.
vellum solver dop internal value error?
793 2 0
-
- sda502
- Member
- 37 posts
- Joined: April 2022
- Offline
-
- Enivob
- Member
- 2535 posts
- Joined: June 2008
- Offline
It looks like order of operation, right? The code fetches the value for stiffness, which is 8, multiplies it by the fall off, let say it 0.5 on this frame. That produces a 4 result, which the max function evaluates as larger than 1. The 4 is stored in the stiffness field and gets multiplied by 0.01.
Try resetting the 0.01 to 1.0, and multiply the value of stiffness by 0.01.
Another way to approach this might be with a fit if you want to specify a specific range for the mops_falloff.
Try resetting the 0.01 to 1.0, and multiply the value of stiffness by 0.01.
stiffness = max(a*(stiffness*0.01),1);
Another way to approach this might be with a fit if you want to specify a specific range for the mops_falloff.
stiffness = fit01(a,4,8);
Edited by Enivob - Aug. 7, 2022 10:34:22
Using Houdini Indie 20.0
Windows 11 64GB Ryzen 16 core.
nVidia 3050RTX 8BG RAM.
Windows 11 64GB Ryzen 16 core.
nVidia 3050RTX 8BG RAM.
-
- sda502
- Member
- 37 posts
- Joined: April 2022
- Offline
Now I realised that I was misled to think the code fetched the value for stiffness premultiplied by the order of magnitude, which equals 0.008, also the stiffness value resulting from the vex code was the final stiffness value the machine reads for simulation.
Thank you so much, Enivob.
Thank you so much, Enivob.
Edited by sda502 - Aug. 7, 2022 11:40:03
-
- Quick Links