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

[FEATURE REQUEST] Disable spatial mouse control temporarily in editor when using MRTK input simulator #918

Open
NoTuxNoBux opened this issue Sep 11, 2024 · 0 comments
Labels
Priority: Low The priority of the issue is low. Type: Feature Request A request for a new feature that can be included with the next minor version release.

Comments

@NoTuxNoBux
Copy link

Describe the problem

  1. Place spatial mouse controller in scene.
  2. Enter play mode.
  3. Press the left mouse button, observe spatial mouse activating and taking over.
  4. Press escape to stop using spatial mouse.
  5. Press space to activate right hand simulation.
  6. Press left mouse button to do pinch gesture.
  7. Observe the spatial mouse taking over control again and the right hand jumping or clicking something unintended.

Describe the solution you'd like

Ideally the spatial mouse controller is automatically temporarily disabled when the MRTK input simulator activates, since having both active at the same time is rather painful during testing.

Describe alternatives you've considered

  • Disable the spatial mouse controller in the scene in play mode when you want to test the right hand. This has to happen every time you enter play mode. Doing so permanently in the editor doesn't work for us since we ideally want to be able to test both constantly.
  • Listen to the MRTKInputSimulator activating and toggle the spatial mouse controller ourselves, but there doesn't seem to be any event that fires from this class to do so with.
@NoTuxNoBux NoTuxNoBux added Needs: Triage Needs to be triaged. Type: Feature Request A request for a new feature that can be included with the next minor version release. labels Sep 11, 2024
@shaynie shaynie added Priority: Low The priority of the issue is low. and removed Needs: Triage Needs to be triaged. labels Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low The priority of the issue is low. Type: Feature Request A request for a new feature that can be included with the next minor version release.
Projects
None yet
Development

No branches or pull requests

2 participants