search

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

SteamVR takes over UnityEditor on Play MRTKV-Next #3087

Closed KatVHarris closed 5 years ago

KatVHarris commented 6 years ago

Mixed Reality Toolkit V-Next

When setting up a new scene, configuring for v-next, and hitting play, SteamVR takes over, freezing Unity and causing the user to TaskManager EndTask on Unity to regain control.

Unity Editor Version Unity 2018.3.0b8

Mixed Reality Toolkit Release Version Using the V-Next unity package - https://github.com/Microsoft/MixedRealityToolkit-Unity/releases/tag/2018.9.0-Beta

To Reproduce Unity

Expected behavior Example scene should run within the Editor

Actual behavior SteamVR takes control and opens the empty scene in their portal, freezing unity. I can move within SteamVR but that's about it. Trying to exit pops up a dialog telling the user that Unity will exit too. When the user hits close anyway the Unity editor does not close because it has crashed.

Screenshots steamvrtakeover1

steamvrtakeover

Possible Solution Just warn people that if steamVR is up (or on the initial start of the headsets and MRP), it may take control over the editor.

StephenHodgson commented 6 years ago

We don't fully support SteamVR yet, but we are talking with Valve engineers about the best way to support.

Related to https://github.com/Microsoft/MixedRealityToolkit-Unity/issues/3073

Thanks for reporting!

StephenHodgson commented 6 years ago

Is this also sounds like something that may be reproducible outside of the MRTK.

I'll keep you posted

SimonDarksideJ commented 5 years ago

OK, this is actually a Unity bug and not related to the MRTK. There is also a bug where SteamVR will be used on the WSA platform, if VR is enabled on Standalone but not WSA 📦

Unity also has a VERY annoying feature if the standalone build has VR enabled on startup, whereby Unity will launch SteamVR before the editor starts. It "should" eventually resolve it self and start.

My recommendation would be to open the MRPortal first, then start SteamVR manually, before opening Unity in Standalone or hitting play. Alternatively, start your Project in WSA mode (possible thanks to the hub), which does not start any VR "thing"

SimonDarksideJ commented 5 years ago

As a simple test, to show this isn't related to the MRTK:

You will find that it automatically tries to launch SteamVR to help VR devs when using Unity for VR.

Hint, It DOES NOT

Yoyozilla commented 5 years ago

closing since this is not an MRTK bug.