You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Currently, in ObjectNavSegment, when using front facing camera of the phone, the vehicle's target control is incorrect. When the object is at the vehicle's left front, it turns to right, and vice versa. Currently, in order for the bot to do object nav correctly, one has to put the phone upside down, but consequently the controling UI is upside down too, which is inconvienient to use.
To Reproduce
Steps to reproduce the behavior:
With current release 0.7.1, let the phone screen facing to vehicle's front, and switch to front facing camera
Go to Object Tracking segment
Try object tracking
See error - control should be mirrored
Expected behavior
When the phone screen facing to vehicle's front, and using front facing camera, control target should be correct so that the bot can follow detected object.
Smartphone:
Device: some main stream phones, Samsung S20FE & Samsung A40S tested
OS: Android 10 & Android 13 tested
Version 0.7.1, master
Suggested fix
Fix should be easy, I'll create a pull request soon
The text was updated successfully, but these errors were encountered:
Description
Currently, in ObjectNavSegment, when using front facing camera of the phone, the vehicle's target control is incorrect. When the object is at the vehicle's left front, it turns to right, and vice versa. Currently, in order for the bot to do object nav correctly, one has to put the phone upside down, but consequently the controling UI is upside down too, which is inconvienient to use.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When the phone screen facing to vehicle's front, and using front facing camera, control target should be correct so that the bot can follow detected object.
Smartphone:
Suggested fix
Fix should be easy, I'll create a pull request soon
The text was updated successfully, but these errors were encountered: