I'm sorry, I've put the link to the relevant community post in the wrong place. Also, the link itself seems to be problematic, and I can't fix it myself. Could you please help me correct it?

@ordinc Thanks I will check it very soon.
Btw: did you closed on purpose your other PR? 😅

No worries about the link 😄

@miquelcampos I’m really sorry, I accidentally closed the previous PR about quickly updating component types by mistake—I’m still new to Git😅

@miquelcampos While testing the 'EPIC Template Samples', I discovered a bug in upv_visualizer.py. Instead of directly connecting the scale attribute, it should use the scale decomposed from the world matrix. This way, when the component's parent has scaling applied, the correct scale value can be obtained.

My adjustment is shown in the image below:

My question is: if I fix this bug and update the EPIC_arm and EPIC_leg components, do I need to submit a new PR?

@ordinc Thanks for the info!
I can add the change following the changes in the image
Thanks!

@ordinc
I did the update, but also planning to move some logic from the component to a centralized method on the component object
I will add more changes soon
;)

Sounds good. Looking forward to the upcoming changes.
During the process of updating the guide, there are duplicate naming structures in the scene (root, elbow/knee, wrist/ankle, eff, upv). This results in overly long names when creating nodes for calculating UPV positions. Therefore, in upv_visualizer.py, all parameters involving node names should use shortName. For specific details, please refer to the image below.