Open nooxouille opened 4 years ago
We only support Unity 2019.2. currently. There are conflicting ar foundation dependencies between azure spatial anchors and the MRTK that have prevented us from moving to Unity 2019.4.. I am not sure if these android related import issues are due to using Unity 2019.4.*
Alright, my bad then ! Do you see the light at the end of the tunnel regarding the conflicts ? Or is it a HUGE piece that might take a while before being resolved ?
Hi there ! Hope you are doing well.
Versions & plateforms
Windows 10
Hololens2
Samsung Galaxy Tab 5se
Visual Studio 2019
Unity 2019.4 LTS on XR Legacy piepline
MRTK 2.4
ARKit, ARCore, ARFoundation, ARsubsystems all are on 2.2.0 preview 6 as advised thought Slack discussion, because of console errors
Problem
I have followed the instructions from the documentation. I have cloned the SV repo, checkout to master, executed the "CreateUnityPackage.bat", and referenced the package inside unity. I think I did it the right way : from the unity's package manager, I went in "...\MixedReality-SpectatorView\src\SpectatorView.Unity\Assets" and took the package.json file
Errors get fired but updating ARKit, ARCore, ARFoundation and ARsubsystems to 2.2.0 preview6 solve them but then, this one stays around :
Saving, closing and opening the project make the toolbar spectator view menu appears. But the error remain. I can't edit the spectator view settings nor any other SV related settings : on click, nothing happen but the error logs ...
Other informations
I am struggling for quite a long time with spectator view, probably misunderstanding something. I have try many, many times to make it work and lately, following the instructions with the submodule solution just trigger errors so I went for the other solution. I need to make this work for next week, sadly ...
[EDIT] Before that, I tried with the Unity XR SDK pipeline and the submodule solution. It worked "well" until starting the SV application on android. Connecting it to the HL2 made the HL2 app crach.
I am now trying inside an ampty project, again via the submodule. When going for the manifest.json, nothing happen but a red log: