This change is addressing issues: #5570, #5305, #5321

Thanks. If any rotation is needed the rotation should be handled internally or hand-controls is not working properly.

@dmarcos sorry for the delay - the holidays were very busy hahah. What do you mean by internally? Should it be handled in some other module? I figured that I would place the rotation handling into the same place where it was being already modified previously.

@filandra This means removing offSetRotation offSetPosition properties you added, put back the offset directly in radians inline in the code, so Math.PI / 4 for everything.

@vincentfretin Well the whole point of the PR is to add the ability to set custom rotation and position. If not here, where should this logic be added?

The rotation is wrong on all Quest headsets right? After you fix the rotation inline in the component, why would you need to customize it?

Yeah we should just fix the rotation. No need of a public API

@dmarcos @vincentfretin I believe now the implementation should be correct?

Yes, that's correct, thanks. I tested on the showcase/tracked-controls/index.html example, with lowPoly, highPoly and toon hands on my Quest 3, hands position are correct with that change. @dmarcos good to merge, you can also close the linked issues.