Required retargeting data is currently always calculated when start_retargeting() is used (or editor button pressed).
While not very noticeable in the C++ module this can add a lot of additional processing time on the slow GDScript version.
After the first retargeting the data does not really need to be recalculated as long as:
both skeletons (paths) stay the same
mappings are not changed
no user code from outside changes skeleton rest poses
A skip for (re)calculating offsets after the first retargeting and only reset when something changes could improve performance, especially for GDScript.
Required retargeting data is currently always calculated when
start_retargeting()
is used (or editor button pressed).While not very noticeable in the C++ module this can add a lot of additional processing time on the slow GDScript version.
After the first retargeting the data does not really need to be recalculated as long as:
A skip for (re)calculating offsets after the first retargeting and only reset when something changes could improve performance, especially for GDScript.