21-03-2025, 08:47 PM
Thanks for the information!
I think some way to guarantee a distance in "mu space" would be very useful. In many cases you would want two pinhole joints close to each other to constrain the direction. But with the possibility of the constraints to pass over each other many simulations will become unstable.
Would it be possible to give each pinhole constraint a reference to another pinhole constraint which (if defined) modifies the constraint limits to keep a certain distance to the reference pinhole? Would this break the multithreading rules or is it fine a single reference to another constraint?
About the bug, I only see it in my script which is creating multiple pinhole constraints in the same batch. Sorry, I can't guarantee I haven't made an error there. I tried debugging best I could but havent found anything wrong in my modified script yet.
I think some way to guarantee a distance in "mu space" would be very useful. In many cases you would want two pinhole joints close to each other to constrain the direction. But with the possibility of the constraints to pass over each other many simulations will become unstable.
Would it be possible to give each pinhole constraint a reference to another pinhole constraint which (if defined) modifies the constraint limits to keep a certain distance to the reference pinhole? Would this break the multithreading rules or is it fine a single reference to another constraint?
About the bug, I only see it in my script which is creating multiple pinhole constraints in the same batch. Sorry, I can't guarantee I haven't made an error there. I tried debugging best I could but havent found anything wrong in my modified script yet.