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

Controllers not working - Entering MR portal fixes issue temporarily #1538

Closed milos12345 closed 6 years ago

milos12345 commented 6 years ago

Overview

On Unity Play the Controllers are not active. Pressing Win key on controllers to open MR portal and clicking the app again makes the controllers visible. Every time the play mode is restared the same steps are required to enable controllers

Steps to reproduce

Happens with example scenes, and also with an empty scene with just MR toolkit activated and project/scene settings applied

Unity Editor Version

2017.2.1f1

Mixed Reality Toolkit Release Version

2017.2.1.0

ivan2007 commented 6 years ago

I am experiencing the same problem

cre8ivepark commented 6 years ago

@NeerajW @keveleigh It seems like this is the regression in Unity 2017.2.1f1. Running the same project in MRTP5 does not show this symptom. Had the same issue in early MRTP version which has been fixed from MRTP4.

StephenHodgson commented 6 years ago

Has anyone opened a bug report with Unity yet?

ivan2007 commented 6 years ago

Hi Stephen, I didn't open a bug report with Unity.

StephenHodgson commented 6 years ago

Please do so and give us a case number here.

hridpath commented 6 years ago

With a little Debugging of the MotionControllerVissualizer.cs, I see that the UnityEngine.XR.WSA.Input.InteractionManager does not have any InteractionSourceStates available at the time the script is executed. Also when the action of clicking the Windows button to go to portal and then click on application to resume, the MotionControllerVisualizer does not execute the Awake override. But, the controller models become visible. Just wondering if Unity is loading the controllers themselves in this version?

ivan2007 commented 6 years ago

Hi Stephen, I created a bug report with Unity. Case 980399. https://fogbugz.unity3d.com/default.asp?980399_b1hka3slivv4klvn Ivan

hridpath commented 6 years ago

I have downloaded and installed Unity 2017.3.0f3 this issue is not present in the Unity version.

ivan2007 commented 6 years ago

I confirm that this issue is not present with Unity 2017.3.0f3.

ivan2007 commented 6 years ago

Official answer from Unity (https://fogbugz.unity3d.com/default.asp?980399_b1hka3slivv4klvn):

Hello,

My name is Denisas and I have been investigating your case. The issue with the controllers is fixed in the latest version of Unity

Best regards, Denisas Kirilovas Unity QA Team

sonicviz commented 6 years ago

I'm using Unity 2017.3.0f3 and having this problem. It does not appear to be fixed. The "workaround" of "Pressing Win key on controllers to open MR portal and clicking the app again makes the controllers visible" does not work.

I'm using an Acer MR kit as part of Microsoft MR dev program. Test scene is the MotionControllerTest from latest download of https://github.com/Microsoft/MixedRealityToolkit-Unity Headset and gaze tracking all works fine, just not detecting the controllers. They pop up fine when hitting the win key to drop into MR Portal, but disappear as soon as you go back to Unity.

ivan2007 commented 6 years ago

I'm using Unity 2017.3.0f3 and the problem is not present. You don't see nothing or you see two blocks as controllers?

sonicviz commented 6 years ago

Nothing at all, but switching to MR Portal they show up just fine. The disappear going back to Unity.

sonicviz commented 6 years ago

Update: My bad, I had not switched the project to Universal Windows Platform. All OK now! ty,

cybergoulion commented 6 years ago

I'm having the same problem with Unity 2017.2.1f1 and v2017.2.1.1 release. In the answer for the bug in unity reports it is closed and fixed in the latest version of unity. What version they refer to? What is the latest version of unity we should use with the toolkit?

ivan2007 commented 6 years ago

@cybergoulion, I'm using Unity 2017.3.0f3 with the current release of MRTK. The problem is not present.

cybergoulion commented 6 years ago

@ivan2007 Thank you, I was testing it myself just now and I also confirm that it works as expected up to 2017.3.1f1. Generaly I am reluctant to try the latest versions of unity because in the past I had compatibility issues with the toolkit, but it seems we are way past that now :-)

JamesMillsDev commented 6 years ago

Happening again on Unity-2017.4.12f1 with MRTK 2017.4.1.0