Mixedrealitytoolkit-unity: Hololens Unet client places anchor at headset position

[benjamincoven]

Overview

After a hololens starts to host and place corectly an anchor somewhere in the room. When a second hololens connects to the first one with Unet, it succesfully gets the server anchor (with the good id) but the anchor is placed at the headset position when the app connected. Note that all shared holograms and player controllers are well placed relatively to this anchor so all the scene is incorect of only one translation. Debug panel show nothing special except anchor set to true.

Expected Behavior

The client should place the anchor at the same real position than the server.

Actual Behavior

The client place the anchor at its headset position one second after connected to the server

Steps to reproduce

Here a summary of what contains ma scene:
SpatialGameObject
UIContainer (prefab with UNET UI from MRTK)
NetworkGameObject
SharedCollectionGameObject
UNetAnchorManager

Unity Editor Version

2018.1.2f1

Mixed Reality Toolkit Release Version

2017.4.0.0

Thank you very much for your help

[zachyale]

Acknowledged- nothing else to add, but I am also encountering the same issue.

Encountered using Mixed Reality Toolkit ver. 2017.4.0.0, and Unity ver. 2017.4.5f1.

[StephenHodgson]

Duplicate of #2276?

[benjamincoven]

Not sure, I don't have the error "This script is not intended to be run from the Unity Editor".

EDIT: And the client seems to successfully download the anchor because AnchorPlaced is set to true with the same anchor ID than the server.

[hansbickhofe]

After we changed some of the Compilerdirectives we got rid of the error "This script is not intended to be run from the Unity Editor". But we noticed the Debug Message that tells "Downloading from ...." seems to have missing Strings (two Spaces). So we think that the Client Lens try'd to download the Anchor, but doesnt know where to get it.

[benjamincoven]

Is SpatialUnderstanding necessary for shared anchors? It is disabled in our project because it is not necessary. We keep SpatialMapping active and the Observer working.

No thought about the issue? Our application will be presented next week at an international exhibition with hundreds of potential Hololens customer from heavy industry.

Thank you very much.

[keveleigh]

I believe I've root caused this issue and have opened #2319 with a fix. Please take a look and let me know if it fixes your issue! I was able to repro it before this fix and now the test scene works for me.

[benjamincoven]

Thank you very much, we have tested the branch SharingInvestigation successfully with our app, however it breaks Vuforia, we will investigate tomorow.

EDIT: There is no problem with Vuforia, our bug was something else.

[Redge-Ballard]

@keveleigh this is a dumb question but how would I go about checking out your branch? Or do I need to wait until the PR is merged in?

[benjamincoven]

@Redge-Ballard Clone the following repository: https://github.com/keveleigh/HoloToolkit-Unity

Then checkout on branch SharingInvestigation.

Edit: My bad, didn't check that the branch was merged, checkout june18_dev from official repository https://github.com/Microsoft/MixedRealityToolkit-Unity

You can use assets in folders Sharing and SharingWithUnet in HoloToolkit and Holotoolkit-Exemples