search

microsoft / MixedReality-SpectatorView

Mixed reality spectator experiences
MIT License
194 stars 114 forks source link

QR and ArUco script reference issues after importing MRTK 2.4.0 #425

Open JavoNazarov opened 4 years ago

JavoNazarov commented 4 years ago

Hello!

I have the same errors as here #380

Environment info: Unity 2019.1.14f1 MixedReality-SpectatorView from Master Branch (i.e. v1.2.0) MRTK 2.4.0 Windows SDK

These are logs after creating Unity Package as instructed in README of this repository: Create Unity package Logs after -HardCopy.txt

My final goal is to integrate Spectator View to our project made on Unity 2019.1.14f1 with MRTK 2.4.0. But first, I created an empty unity project to test spectator view. I Referenced MixedReality-SpectatorView as a submodule, then added MRTK 2.4.0. Seems like MRTK caused these errors, because I could build "a flat" application for Hololens 2 from empty project with spectator view before importing MRTK 2.4.0.

After I imported MRTK, project can run in Play mode, but I unable to build (for VS) due to these errors:

Capture

I tried various solutions from Google like adding ::global keyword, but nothing worked. I spent two days trying to integrate SV to Unity 2019.1.14f1+MRTK 2.4.0. Is it possible at all ?

And could you please recommend me the exact environment where Spectator View and MRTK will definitely work? I only succeeded in running Build 2019 Demo, but it was made on Unity 2018 and MRTK 2.1.0 and there is no way to integrate it with our project.

RobertLee6108 commented 4 years ago

When using Unity 2019.4.10f + SpectatorView 1.2.0 + MRTK 2.4.0 I had the same error. and I succeeded in clearing the error. My workaround (error shown) is to change the preprocessor to UNITY_WSA -> UWP.

JavoNazarov commented 4 years ago

I managed to pass these errors by adding ::global keyword in all 6 places pointed in the console. But after building the project to Hololens 2 and Android I cannot connect to Host from Android device. Android debugger just shows "Trying to connect to IP....".

Moreover, I tried to use BUILD 2019 demo from Master branch(Unity 2019.2.19f1) and couldn't connect to Android Device as well. But BUILD 2019 demo from release branch 1.1.0 (Unity 2018.3.14f1) works on same devices with the same network settings.

Are the instructions missing something?

Here's what I see in the android debugger when device cannot connect to host: BUILD 2019 demo from Master branch: Capture1 Empty project with Spectator View: Capture

RobertLee6108 commented 4 years ago

That problem is not correct, but it seems to be an IL2CPP problem. In the past, when using MRSV 1.1.0 + 2019.4.3f, I had a problem that the socket could not be connected.

I referenced this thread and modified the IL2CPP code and it worked fine. It seems to have been fixed in the latest LTS version.

JavoNazarov commented 4 years ago

That problem is not correct, but it seems to be an IL2CPP problem. In the past, when using MRSV 1.1.0 + 2019.4.3f, I had a problem that the socket could not be connected.

I referenced this thread and modified the IL2CPP code and it worked fine. It seems to have been fixed in the latest LTS version.

Thank you very much, this approach seemed to solve the problem with sockets. However, now I am facing a problem with "Running Spatial Alignment", as in #426. This issue happens only on Master Branch of Spectator View.

genereddick commented 4 years ago

I was also having socket problems. For me, the issue was related to Windows SDK 10.0.19041.0. Removing this version and using the previous Win SDK version resolved the problem (in some cases it seems that the registry key is not updated on uninstall so I had to retarget the solution to make sure it was pointing to the correct version).

https://forum.unity.com/threads/il2cpp-failing-in-windows-machine.891436/

jasimmj commented 3 years ago

That problem is not correct, but it seems to be an IL2CPP problem. In the past, when using MRSV 1.1.0 + 2019.4.3f, I had a problem that the socket could not be connected. I referenced this thread and modified the IL2CPP code and it worked fine. It seems to have been fixed in the latest LTS version.

Thank you very much, this approach seemed to solve the problem with sockets. However, now I am facing a problem with "Running Spatial Alignment", as in #426. This issue happens only on Master Branch of Spectator View.

Any solutions yet for this ?