"request activity" for damper and bumstop doesent match?

Hello ,

funtion "request activity" can get request wrt-I and wrt-J. But for damper and bumpstop, the I marker and J marker are the same, which doesnt match what we want. Ohterweise, for bushing, spring, rebound are logical in the mind. So , is my thouht wrong?

Parents

0 zhenhui xu over 2 years ago

Hi Alex and Henrik

Thanks for you feedback.

In order to explain more clear from me, i attach the comprasion between bushing and bumpstop.

Please look at the difference about marker order for wrt_I and wrt_J both entries in the picture.

For example, if people was interested in request from I part. Then the I_marker should be imarker, J_marker shuold be jmarker, rmarker should be located in I part.

If people was interested in reqeust from Jpart. Then the I_marker should be jmarker, J_marker should be imarker, the rmarker should be located in J part.

It was what we want for bushing/spring/rebound entities. But it was not what we want for damper/bumpstop entities in version 2021.04. And it should be.

Is there anything wrong from my thought?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 zhenhui xu over 2 years ago

Hi Alex and Henrik

Thanks for you feedback.

In order to explain more clear from me, i attach the comprasion between bushing and bumpstop.

Please look at the difference about marker order for wrt_I and wrt_J both entries in the picture.

For example, if people was interested in request from I part. Then the I_marker should be imarker, J_marker shuold be jmarker, rmarker should be located in I part.

If people was interested in reqeust from Jpart. Then the I_marker should be jmarker, J_marker should be imarker, the rmarker should be located in J part.

It was what we want for bushing/spring/rebound entities. But it was not what we want for damper/bumpstop entities in version 2021.04. And it should be.

Is there anything wrong from my thought?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data