microsoft / MixedRealityToolkit-Unity

This repository is for the legacy Mixed Reality Toolkit (MRTK) v2. For the latest version of the MRTK please visit https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity
https://aka.ms/mrtkdocs
MIT License
6.01k stars 2.12k forks source link

EyeTrackingDemo - 03-Navigation Example broken, Eye Tracking scrolling text and more is not working #10269

Closed D4ykoo closed 2 years ago

D4ykoo commented 3 years ago

Describe the bug

The Demo EyeTrackingDemo - 03-Navigation is not working.

That makes it impossible to create a auto eye scrolling text in a custom project.

To reproduce

Steps to reproduce the behavior:

  1. Imported the MRKT EyeTracking Samples: Depending folder -> MRKT > Samples > Mixed Reality Toolkit Examples > 2.72 > Demos - EyeTracking
  2. Followed the instructions from this website: https://docs.microsoft.com/en-us/windows/mixed-reality/mrtk-unity/features/example-scenes/eye-tracking-examples-overview?view=mrtkunity-2021-05 This includes:
  3. Load EyeTrackingDemo-00-RootScene.unity
  4. Added the scences in the correct order to the build menu: Build Settings > Scenes in Build
  5. Let the OnLoadStartScene checked
  6. Make sure GazeInput capability is set in appx build options
  7. Build the project
  8. Made sure in the Package.appxmanifest in functions gaze is checked to verify step 6
  9. Deployed it in Visual Studio 2019
  10. Run the app
  11. Navigated with the eyes to the "sample bar" looked on Navigation and air taped
  12. The text bug shows up
  13. Tested it in the Untiy Emulator and it works 100% fine

Expected behavior

Auto Eye Scroll:
Text is not completely shown, it should be hidden after overflowing the box (see screenshot 2)
Ey-supported Target Rotations:
Rotating based on the parts of the models i am looking at.

Screenshots

Screenshot 1

scrolling text bug

Screenshot 2

screenshot_expected_behavior

Your setup (please complete the following information)

Target platform (please complete the following information)

stale[bot] commented 2 years ago

This issue has been marked as stale by an automated process because it has not had any recent activity. It will be automatically closed in 30 days if no further activity occurs. If this is still an issue please add a new comment with more recent details and repro steps.