Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We’re making changes to the Unity Runtime Fee pricing policy that we announced on September 12th. Access our latest thread for more information!
    Dismiss Notice
  3. Dismiss Notice

Crash in editor on play

Discussion in '2017.2 Beta' started by Code-ttt, Sep 29, 2017.

  1. Code-ttt


    Oct 20, 2014
    I'm getting a crash in editor every time I hit play in editor in a simple scene. I'm on Win10 build 16278.rs3_release. Win SDK 16288. Unity 2017.2.0f1 . I'm using the mixed reality toollkit for Unity Unity 2017.2 branch . I create a scene and add the HoloLensCamera prefab and the InputManager prefab to the scene. Hit play. Crash. I feel like there's something simple I'm missing since I haven't seen any reports about this. I can build this scene and run on HoloLens without a problem.

    The callstack looks like this :

    Assertion failed on expression: 'NULL != this->ptr'
    UnityEngine.XR.WSA.Input.InteractionManager:.cctor() (at C:\buildslave\unity\build\Runtime\VR\HoloLens\ScriptBindings\GestureSource.cs:410)
    HoloToolkit.Unity.InputModule.InteractionSourceInputSource:OnEnableAfterStart() (at Assets\HoloToolkit\Input\Scripts\InputSources\InteractionSourceInputSource.cs:250)
    HoloToolkit.Unity.InputModule.InteractionSourceInputSource:OnEnableAfterStart() (at Assets\HoloToolkit\Input\Scripts\InputSources\InteractionSourceInputSource.cs:237)
    HoloToolkit.Unity.StartAwareBehaviour:Start() (at Assets\HoloToolkit\Utilities\Scripts\StartAwareBehaviour.cs:34)

    [C:\buildslave\unity\build\PlatformDependent/Win/ComPtr.h line 84]
    (Filename: Assets/HoloToolkit/Input/Scripts/InputSources/InteractionSourceInputSource.cs Line: 250)
  2. Peter77


    QA Jesus

    Jun 12, 2013
    If you have a project that can be used to reproduce the crash, I recommend to submit a bug-report following the advice in this document.

    Using the bug-reporter seems to be an important step, because it makes sure the report is in Unity Technologies bug-tracking pipeline and has to be processed at some point. Using the forum is often used to add to a little more attention to a bug-report, but does not replace submitting the bug-report.

    It's from advantage to attach a project to the bug-report that UT can use to reproduce the issue and test their fix against. The easier an issue can be reproduced by QA, the more likely it is to get forwarded to a developer, who might or might not work on a bug-fix for that at some point.

    After you submitted the bug-report, you receive a confirmation email with a Case number. UT often asks us to post the Case number in the forum thread, which allows them to find that bug-report if they look at your post.

    Following these steps will increase the chance that UT is looking at your issue tremendously.