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 have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Microsoft.MixedReality namespace not found after Unity update

Discussion in 'VR' started by Entretoize, May 1, 2020.

  1. Entretoize

    Entretoize

    Joined:
    Feb 27, 2015
    Posts:
    44
    Hello, I just updated Unity to 2019.3.12f1 and upgraded my project, and it doesn't work anymore.
    Visual Studio doesn't find MixedReality namespace in Microsoft namespace.
    I tried to reimport the MRTK2 templates but it doesn't work.

    Any idea ?

    Thanks
     
  2. Draxi_

    Draxi_

    Joined:
    Sep 6, 2015
    Posts:
    7
    I'm having a similar problem with SteamVR. Trying to use "Valve.VR" but it can't find the namespace.
    Also my editor scripts in "Editor" folder can't see scripts in the normal Assembly.
    I guess we'll have to downgrade to 2019.3.11 :-/
     
  3. vrinaldi

    vrinaldi

    Joined:
    Mar 9, 2017
    Posts:
    6
    Same problem here, updating from 2019.3.10f1 to 2019.3.12f1
     
  4. keveleigh

    keveleigh

    Official Microsoft Employee

    Joined:
    Jun 19, 2015
    Posts:
    35
    Hmm, not sure exactly what could be causing this. The fact that there's a second report not specific to the `Microsoft.MixedReality` namespace is interesting. I just tried to repro locally and couldn't.
    One thing I'd recommend trying is deleting all the generated .csproj and .sln files in the root of your project, then restarting Unity to have it regenerate those files. Sometimes I've seen them get into an odd stale state.
     
  5. Entretoize

    Entretoize

    Joined:
    Feb 27, 2015
    Posts:
    44
    Just tried, it doesn't work, no change...
     
  6. vrinaldi

    vrinaldi

    Joined:
    Mar 9, 2017
    Posts:
    6
    Thank you keveleigh, I deleted all .csproj and .sln files but it didn't work.
    I'm back on 19.3.10f1 flawlessly, so I'll stick with it. I'm sorry I couldn't give more details about reproducibility, but the only thing I've done that broke the namespace was the Unity update.
     
  7. DarkSoulsBoss

    DarkSoulsBoss

    Joined:
    May 9, 2020
    Posts:
    1
    Just reiterating that I've hit this issue in Unity 2019.3.12 and couldn't get past the issue initially either (whether it be by reloading the library, deleting .csproj files, restarting Unity etc.)

    I was able to get it working with a fresh install of Unity 2019.3.13 though
     
  8. MisterMan123

    MisterMan123

    Joined:
    Jan 6, 2018
    Posts:
    5
    I also experienced this recently, couldn't get any script to see the Valve.VR namespace unless I put it in the SteamVR folder itself.