Colliders disappear when Foot Tracking is activated

Custom Component "Foot Tracking" (from Assets Library)
causes problems in "Physical Collider" and "Phycical Body" in the entire Lens Studio project

Here
https://drive.google.com/file/d/1yjfPRmABMT-rd4bRx8rj5fiLdJlqjx_O/view?usp=share_link

you can see that when activating the Foot Tracking component the colliders disappear and re-appear when turning the Foot Tracking component off.

Here is the test project showing the issue:
https://drive.google.com/file/d/1QtzOG6JKXRxFFhWkpGWIYzDaJW0RjOah/view?usp=share_link

We could make the colliders work in Lens Studio preview but running the Lens on mobile device -- the colliders do not work. We do not understand what causes the issue.

Answers

  • Bakari Mustafa
    Bakari Mustafa Posts: 174 🔥🔥🔥

    It's likely that the custom "Foot Tracking" component is conflicting with the built-in "Physical Collider" and "Physical Body" components in some way. One possible solution would be to investigate the code of the custom component and see if any changes can be made to make it compatible with the other components. Another solution is to try to use a different custom component that is compatible with the built-in components, or use the built-in components without the custom component.

  • forwARdgame
    forwARdgame Posts: 41 🔥

    Is there an alternative component for foot tracking? We just want to use colliders with foot tracking. Clearly it's not possible. So is it a desired behaviour of killing the colliders when foot tracking is on?

  • forwARdgame
    forwARdgame Posts: 41 🔥

    @Bakari Mustafa said:
    It's likely that the custom "Foot Tracking" component is conflicting with the built-in "Physical Collider" and "Physical Body" components in some way. One possible solution would be to investigate the code of the custom component and see if any changes can be made to make it compatible with the other components. Another solution is to try to use a different custom component that is compatible with the built-in components, or use the built-in components without the custom component.

    Could you recommend any different components? And could you recommend whom to ask about the problematic component? After all it is provided in Lens Studio Assets and someone coded it :)