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
6k stars 2.12k forks source link

ExamplesHub null active profile - Windows Mixed Reality #6209

Closed CDiaz-MS closed 2 years ago

CDiaz-MS commented 4 years ago

Describe the bug

While running the MRTKExamplesHub scene for Windows Mixed Reality, there is a null active profile error.

No Mixed Reality Configuration Profile found, cannot initialize the Mixed Reality Toolkit
UnityEngine.Debug:LogError(Object)
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:InitializeServiceLocator() (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:293)
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:ResetConfiguration(MixedRealityToolkitConfigurationProfile) (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:117)
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:set_ActiveProfile(MixedRealityToolkitConfigurationProfile) (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:87)
Microsoft.MixedReality.Toolkit.Examples.Demos.EyeTracking.LoadProfilesOnStartup:Start() (at Assets/MixedRealityToolkit.Examples/Demos/EyeTracking/General/Scripts/Utils/LoadProfilesOnStartup.cs:19)

To reproduce

Steps to reproduce the behavior:

Your Setup

Target Platform

Additional context

Eye tracking is causing the issue and WMR does not have eye tracking capabilities.

cre8ivepark commented 4 years ago

@Cameron-Micka @Railboy

Railboy commented 4 years ago

The error message is technically by design. The LoadProfilesOnStartup sets the ActiveProfile to null, and that action will always generate an error. We should change it from an error to a warning if we intend to support setting ActiveProfile to null.

stale[bot] commented 4 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.

stale[bot] commented 4 years ago

This issue has been closed by an automated process because it is stale. If this is still an issue please add a new comment with more recent details and repro steps.

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.

david-c-kline commented 2 years ago

This issue is unlikely to be addressed as primary development has moved to MRTK3 (and that this issue impacts only the Examples Hub)