Unity 2017.2 / Fall Creators Update (Windows Insider) / Vuforia + HoloLens = startup crash

I have this strange problem nobody at Unity seems to be able to duplicate. Suddenly, any Vuforia project I create in Unity 2017.2 crashes on startup. Merely checking the Vuforia box off in the XR settings and building a blank scene with just a camera will cause a scene even without an ARCamera to crash at startup.

I've tried rebooting the HoloLens. Different HoloLenses. Re-installing 2017.2. Reinstalling Visual Studio. Nothing works. Crashes in Vuforia.VuforiaBehaviour:Start() on both IL2CPP and.NET. It must be something environmental on my machine, but I can't imagine what it is. Is Visual Studio somehow building with junk libraries?

I know it's a Unity/Vuforia issue but I figured I'd post here because I suspect it's something weird with Visual Studio or my UWP SDK installation.

Here's the crash log (IL2CPP)

Exception thrown at 0x770F2522 in HL20172.exe: Microsoft C++

exception: Platform::COMException ^ at memory location 0x029FC6F0.

HRESULT:0xC00D3E85 The request is invalid because Shutdown() has been

called.

WinRT information: The request is invalid because Shutdown() has been called.
Here's the debug console log:
Vuforia.VuforiaARController:Start()

System.Reflection.MonoMethod:InternalInvoke(Object, Object[], Exception&)

System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder,

Object[], CultureInfo)

System.Reflection.MethodBase:Invoke(Object, Object[])

System.Delegate:DynamicInvokeImpl(Object[])

System.MulticastDelegate:DynamicInvokeImpl(Object[])

System.Delegate:DynamicInvoke(Object[])

Vuforia.DelegateHelper:InvokeDelegate(Delegate, Object[])

Vuforia.DelegateHelper:InvokeWithExceptionHandling(Action)

Vuforia.VuforiaBehaviour:Start()
(Filename: C:\buildslave\unity\build\artifacts/generated/Metro_IL2CPP/runtime/DebugBindings.gen.cpp

Line: 51)
HL20172.exe' (Win32): Loaded

'C:\Windows\System32\Windows.Media.dll'. Cannot find or open the PDB

file.

'HLr20172.exe' (Win32): Loaded

'C:\Windows\System32\mfsensorgroup.dll'. Cannot find or open the PDB

file.

'HL20172.exe' (Win32): Loaded

'C:\Windows\System32\deviceaccess.dll'. Cannot find or open the PDB

file.

'HL20172.exe' (Win32): Loaded

'C:\Windows\System32\MFCaptureEngine.dll'. Cannot find or open the PDB

file.

'HL20172.exe' (Win32): Loaded

'C:\Windows\System32\policymanager.dll'. Cannot find or open the PDB

file.

'HL20172.exe' (Win32): Loaded

'C:\Windows\System32\igd11dxva32.dll'. Cannot find or open the PDB

file.

'HL20172.exe' (Win32): Loaded 'C:\Windows\System32\MFT0_OEM.dll'.

Cannot find or open the PDB file.

'HL20172.exe' (Win32): Loaded

'C:\Windows\System32\IntelCameraPlugin.dll'. Cannot find or open the

PDB file.

'HL20172.exe' (Win32): Loaded

'C:\Windows\System32\igfx11cmrt32.dll'. Cannot find or open the PDB

file.

HL20172.exe' (Win32): Loaded 'C:\Program Files\Intel\Media

SDK\libmfxhw32.dll'. Cannot find or open the PDB file.

The thread 0x16ec has exited with code 13430017 (0xcced01).

The thread 0xecc has exited with code 13430016 (0xcced00).

The thread 0xe14 has exited with code 13430018 (0xcced02).

The thread 0x330 has exited with code 13430019 (0xcced03).

The thread 0x2a8 has exited with code 13430016 (0xcced00).

The thread 0x760 has exited with code 13430018 (0xcced02).

The thread 0x18c has exited with code 13430017 (0xcced01).

The thread 0x1068 has exited with code 13430019 (0xcced03).

HL20172.exe' (Win32): Unloaded 'C:\Program Files\Intel\Media

SDK\libmfxhw32.dll'

Exception thrown at 0x770F2522 (KernelBase.dll) in HL20172.exe:

0x40080201: WinRT originate error (parameters: 0xC00D36B3, 0x00000027,

0x15CFED7C).

'HL20172.exe' (Win32): Loaded 'C:\Windows\System32\msvproc.dll'.

Cannot find or open the PDB file.

The thread 0x113c has exited with code 0 (0x0).

Exception thrown at 0x770F2522 (KernelBase.dll) in HL20172.exe:

0x40080201: WinRT originate error (parameters: 0xC00D3E85, 0x0000003A,

0x15BFF59C).

ralphbarbagallo.com - flarb.com - @flarb

Tagged:

Answers

  • I got the same issue and I am stuck. Were you able to solve it?

  • Despite the error, VS 2017 will deploy the app to HoloLens. Just start it from there.

  • Jimbohalo10Jimbohalo10 ✭✭✭
    edited December 2017

    The versions you using are old beta versions. download the updated HoloLens version Unity 2017.2.0p2-MRTP5 download
    Click UnityDownloadAssistant.exe
    Select Vuforia and .Net /UWP.
    Don't use the Unity download option of VS2017
    If you have used this option go to Vs2017 setup and remove the option

    Then download the Mixed Reality toolkit.

    Untick "Target Occluded devices" so that HoloLens is selected.
    Then read Vuforia documentation setup

  • Jimbohalo10, I tried the link and started the process. When I got to the selections, Vuforia was not there. There were 4 selections, the app, docs, .net, and IL2CPP. Could they have updated this?

Sign In or Register to comment.