Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MoveNet Draws Skeleton on the Edge of the Screen on iOS Device #182

Closed
cagri-beep opened this issue Nov 17, 2021 · 2 comments
Closed

MoveNet Draws Skeleton on the Edge of the Screen on iOS Device #182

cagri-beep opened this issue Nov 17, 2021 · 2 comments

Comments

@cagri-beep
Copy link

Environment (please complete the following information):

  • OS/OS Version: iOS 14.7.1 (iPhone 11 Pro)
  • Source Version: master/2.4.0
  • Unity Version: 2020.3.11f

Describe the bug
MoveNetSinglePose sample behaviour is different in iOS than it is in the editor. The skeleton is drawn on the edge of the screen instead of on detected person's body/face.

To Reproduce
Steps to reproduce the behaviour:

  1. Clone master repo.
  2. Open with Unity 2020.3.11f with target set to iOS
  3. Navigate to Samples > MoveNet > MoveNetSinglePose and open the scene.
  4. Click File > Build Settings (Switch target to iOS if it is different)
  5. Select All scenes in build settings and delete them.
  6. Add MoveNetSinglePose scene to build settings (by clicking add open scenes button).
  7. Build and run the sample on iPhone.
  8. Accept camera permissions (it'll crash because of the camera permissions)
  9. Close the app
  10. Open the app again

Expected behaviour
Skeleton drawing on detected body instead of at the edge of the screen.

Screenshots

Expected Behaviour (In Unity Editor Screen Shot)
Screenshot 2021-11-17 at 15 31 11

Buggy Behaviour (iOS Device iPhone 11 Pro Screen Shot) Drawn line is visible at the lower right corner.
img_0277 (1)

Additional context
Lines are drawn regardless if there is a body/face in camera feed or not.

@sonnybsj
Copy link
Contributor

See my comment in #145 as it could be related to your issue.

I recommend trying out #183.

@cagri-beep
Copy link
Author

Yep, #183 fixed the issue. Thanks for notifying me @sonnybsj

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants