Mixedrealitytoolkit-unity: Unity editor pauses for a significant amount of time when ending Play mode in a scene when using MRTK 2.0

Created on 10 May 2019  路  9Comments  路  Source: microsoft/MixedRealityToolkit-Unity

Describe the bug

The Unity Editor freezes for a significant amount of time when ending Play mode in scene

This has been corroborated by several developers in the HoloDevelopers slack channel:
https://holodevelopers.slack.com/archives/C2H4HT858/p1557497162412800

To reproduce

Steps to reproduce the behavior:

  1. Import MRTK2.0
  2. Configure a scene to use MRTK 2.0
  3. Play the scene
  4. Exit play mode and observe editor freeze for several seconds (some time as long as 30 seconds)

Expected behavior

The editor should not freeze when exiting play mode.

Your Setup (please complete the following information)

  • Unity Version [2018.3.11f1]
  • MRTK Version [v2.0 RC1 and RC1 refresh]

Target Platform (please complete the following information)

Unity Editor

4 - In Review Bug Speech Urgency-Soon

Most helpful comment

Marked as Urgency-Soon, because it's a huge pain to deal with daily development.

All 9 comments

You can work around this by creating a custom MRTK profile, then creating a custom input profile, and removing the following two Data Providers from the list:

image

Closing as duplicate of #3026. Please use the workaround mentioned above. One way we could fix this would be to remove speech input from the default providers, but that would have the disadvantage of removing speech support from MRTK.

Re opening based on suggestion from eprovencher that we should avoid running the speech code in edit mode, seems like a path to a solution

I am seeing lengthy delays in both startup and shutdown with MRTK RC1 Refresh and Unity 2019.1.1f1 as described in #3026, but I couldn't quite tell what the conclusion was to that issue. Disabling speech in the editor sounds like a good interim solution, but would it also be possible to fix the underlying problem? If it's a Unity issue, make sure they know that it's still a problem?

Just FYI, I was able to fix this in my fork by not destroying the DictationRecognizer & KeywordRecognizers when entering and leaving playmode.

Marked as Urgency-Soon, because it's a huge pain to deal with daily development.

Should be good now, please reopen if folks still hit this with the latest mrtk_dev

Just FYI, I was able to fix this in my fork by not destroying the DictationRecognizer & KeywordRecognizers when entering and leaving playmode.

Thank you for sharing this insight @StephenHodgson!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

markgrossnickle picture markgrossnickle  路  3Comments

Alexees picture Alexees  路  3Comments

chrisfromwork picture chrisfromwork  路  3Comments

reillydonovan picture reillydonovan  路  3Comments

ritijain picture ritijain  路  3Comments