anchor doesn't appear when connecting to server on the computer that is different from the computer used for making that anchors.

혜진 서 91

HoloLens2 / Local Spatial Anchor / UE5.1

Open the server on computer A, connect to the server with HoloLens Remote Play, create an anchor, store the anchor on the HoloLens device, and then connect to the server with the HoloLens on computer B. The anchor created on computer A is not loaded. The anchor can be loaded only when the computer used to create the anchor is accessed as a client. Can you tell me why it is doing this?

Zuocheng Wang - MSFT 3,081 Reputation points Microsoft Vendor

2022-12-26T09:20:03.407+00:00

Hello, welcome to Microsoft Q&A,

Are "connect to the server with HoloLens Remote Play" and "connect to the server with the HoloLens on computer B" different operations? Can you describe them in detail? As I mentioned in your other thread, Local Spatial Anchor has nothing to do with connecting to the server or not. By default, the anchor data is stored on the HoloLens device. Based on your other threads, I'm guessing you're building your project as a windows package and then running it through Remote Play Mode. Are you running the same package on different computers? Are you using the same HoloLens device?
혜진 서 91 Reputation points

2022-12-29T08:49:05.287+00:00

I've discovered something..

There are 3 ways to create and load anchors on the HoloLens via window remote play in unreal engine.

The first is to play with VR Preview on the editor. The second is to open the server and then connect to the server through the editor vr preview to play. The third method is to open the server, connect to the server through the build exe file for Windows, and deploy to the HoloLens.

However, I found that anchors created with each method can only be loaded with each method.

Anchors created by each method are not compatible.

Even if the anchor is stored locally, it is not loaded if it is created in a different way.
Nathan Manis - MSFT 476 Reputation points Microsoft Employee

2022-12-29T16:37:00.817+00:00

In reading this last comment, this is UE 5.1 editor behavior in how the implementation is performed and makes sense to me since this is debugging facilities in the Unreal editor.

End users would not do the first two methods since those are specific to the development phase of the project. The end user experience would be using the built executable to stream to the remote HoloLens device. So, would be the final scenario to be testing once completed with project.
Islam El Tabie Ali Abu Derbala 41 Reputation points

2023-06-10T14:00:15.58+00:00

Are "connect to the server with HoloLens Remote Play" and "connect to the server with the HoloLens on computer B" different operations? Can you describe them in detail? As I mentioned in your other thread, Local Spatial Anchor has nothing to do with connecting to the server or not. By default, the anchor data is stored on the HoloLens device. Based on your other threads, I'm guessing you're building your project as a windows package and then running it through Remote Play Mode. Are you running the same package on different computers? Are you using the same HoloLens device

1 answer

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more