Thank you very much,
I mentioned the time here that I tried to see all (?) variables in this "game", and explored a few. (Like placing the position change into a Color Vertex Map, while using a range mapper to tame the results, then using this Color Vertex Map to drive the Displacement. The model exploded here and there
Time is one part of the game, but my main idea is that a problem comes back until it is solved. Sadly, with the forums 1-3, around 15+ years have passed. Since things change, that is not a problem, as more experience will lead to different outcomes.
However, sometimes I can't solve things, and the developers have to do it inside the code and provide a solution, whereby I can only share a process or workaround. The idea of having it solved in the app sounds to me more teamwork-friendly.
If you have any XPresso ideas, but something is missing, perhaps a little piece, I'm happy to look into it. Often, questions like yours need some "storage" to keep data for a moment. In the past, I used a copy of the model; these days, I add the Color Vertex Map into the mix. Perhaps the Joints can be a good driver in this case…
Anyway, sorry for the longer text, but your kind reply made my (Sun-)day. Thank you for that.
Enjoy!