MARS and HoloLens 2

Unity Engine
, ,
1

Hello,

I’m trying to get MARS running on my HoloLens 2 but running into some issues. I’m able to deployed to the HoloLens 2 but when I install MARS I get an error:
Could not find file: “…\ScriptAssemblies\Microsoft.MixedReality.SceneUnderstanding.Projections.WSA.DLL”

I’m following this Building to devices with Unity MARS | Unity MARS | 1.4.1

I’ve followed the steps and tried a few different combinations but can’t seem to get past this. Happy to post what settings I’ve selected and Project Settings, but they are pretty much exactly what the examples shown in the steps are - tried to rule out any random unknowns from an existing project. I’ve installed the Mixed Reality Feature Tool (Welcome to the Mixed Reality Feature Tool - Mixed Reality | Microsoft Learn), and everything looks normal there. Any ideas?

Unity Version 2020.3.21f1
MARS Version 1.4.1

Really appreciate anyone taking the time to read this!

Thanks,
Flash

2

I feel I’ve seen this error before, but setting up for HoloLens seems to go a bit differently every time I try it so I don’t remember the details :frowning:

Can you send a list of the packages you have installed (the Packages/manifest.json file is fine)?

3

Hi,
I get the same error: (0,0): error System.IO.FileNotFoundException: Could not find file “…\Library\ScriptAssemblies\Microsoft.MixedReality.SceneUnderstanding.Projections.WSA.dll”

8107601--1049780--upload_2022-5-6_18-33-34.png
8107601--1049780--upload_2022-5-6_18-33-34.png1463×291 106 KB

I am on Unity 2020.3.34f1 and MARS 1.4.1.This is my manifest.json:
{
“dependencies”: {
“com.microsoft.mixedreality.openxr”: “file:MixedReality/com.microsoft.mixedreality.openxr-1.4.0.tgz”,
“com.microsoft.mixedreality.sceneunderstanding”: “file:MixedReality/com.microsoft.mixedreality.sceneunderstanding-0.6.0.tgz”,
“com.microsoft.mixedreality.toolkit.examples”: “file:MixedReality/com.microsoft.mixedreality.toolkit.examples-2.7.3.tgz”,
“com.microsoft.mixedreality.toolkit.extensions”: “file:MixedReality/com.microsoft.mixedreality.toolkit.extensions-2.7.3.tgz”,
“com.microsoft.mixedreality.toolkit.foundation”: “file:MixedReality/com.microsoft.mixedreality.toolkit.foundation-2.7.3.tgz”,
“com.microsoft.mixedreality.toolkit.standardassets”: “file:MixedReality/com.microsoft.mixedreality.toolkit.standardassets-2.7.3.tgz”,
“com.microsoft.mixedreality.toolkit.testutilities”: “file:MixedReality/com.microsoft.mixedreality.toolkit.testutilities-2.7.3.tgz”,
“com.microsoft.mixedreality.toolkit.tools”: “file:MixedReality/com.microsoft.mixedreality.toolkit.tools-2.7.3.tgz”,
“com.microsoft.spatialaudio.spatializer.unity”: “file:MixedReality/com.microsoft.spatialaudio.spatializer.unity-1.0.246.tgz”,
“com.unity.ar-companion-core”: “1.0.1-preview.2”,
“com.unity.collab-proxy”: “1.3.9”,
“com.unity.content-manager”: “0.1.6-preview”,
“com.unity.ide.rider”: “2.0.7”,
“com.unity.ide.visualstudio”: “2.0.7”,
“com.unity.ide.vscode”: “1.2.3”,
“com.unity.mars”: “1.4.1”,
“com.unity.mars-ar-foundation-providers”: “1.4.1”,
“com.unity.mars-nav-mesh”: “1.4.1”,
“com.unity.test-framework”: “1.1.22”,
“com.unity.textmeshpro”: “3.0.1”,
“com.unity.timeline”: “1.4.6”,
“com.unity.ugui”: “1.0.0”,
“com.unity.xr.openxr”: “1.4.1”,
“com.unity.xr.windowsmr”: “4.4.2”,
“com.unity.modules.ai”: “1.0.0”,
“com.unity.modules.androidjni”: “1.0.0”,
“com.unity.modules.animation”: “1.0.0”,
“com.unity.modules.assetbundle”: “1.0.0”,
“com.unity.modules.audio”: “1.0.0”,
“com.unity.modules.cloth”: “1.0.0”,
“com.unity.modules.director”: “1.0.0”,
“com.unity.modules.imageconversion”: “1.0.0”,
“com.unity.modules.imgui”: “1.0.0”,
“com.unity.modules.jsonserialize”: “1.0.0”,
“com.unity.modules.particlesystem”: “1.0.0”,
“com.unity.modules.physics”: “1.0.0”,
“com.unity.modules.physics2d”: “1.0.0”,
“com.unity.modules.screencapture”: “1.0.0”,
“com.unity.modules.terrain”: “1.0.0”,
“com.unity.modules.terrainphysics”: “1.0.0”,
“com.unity.modules.tilemap”: “1.0.0”,
“com.unity.modules.ui”: “1.0.0”,
“com.unity.modules.uielements”: “1.0.0”,
“com.unity.modules.umbra”: “1.0.0”,
“com.unity.modules.unityanalytics”: “1.0.0”,
“com.unity.modules.unitywebrequest”: “1.0.0”,
“com.unity.modules.unitywebrequestassetbundle”: “1.0.0”,
“com.unity.modules.unitywebrequestaudio”: “1.0.0”,
“com.unity.modules.unitywebrequesttexture”: “1.0.0”,
“com.unity.modules.unitywebrequestwww”: “1.0.0”,
“com.unity.modules.vehicles”: “1.0.0”,
“com.unity.modules.video”: “1.0.0”,
“com.unity.modules.vr”: “1.0.0”,
“com.unity.modules.wind”: “1.0.0”,
“com.unity.modules.xr”: “1.0.0”
}
}

Any clue what I am missing here?

Thanks,
David

4

I am having the exact same problem. :frowning: Has anyone come up with a solution for this?

5

Do you also have the com.microsoft.mixedreality.toolkit.* packages installed? What happens if you remove them?

6

That works now - I can successfully deploy to HoloLens 2.
However once I deploy and run the program, none of the image markers I set up worked. They work in simulation on Unity but not on the actual device.
Any ideas?