Azure Spatial Anchors
An Azure service that is used to build immersive three-dimensional applications and experiences that map, persist, and restore content or points of interest at real-world scale.
86 questions
Cannot save Azure Cloud Anchor with Unreal
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 18%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAV%3C/text%3E%3C/svg%3E)
Anastasios Voulgaris
0
Reputation points
I am working on an unreal engine 5.3 android app. I am trying to save a cloud anchor but I a keep getting this error in the logs: I have all the required permissions, I am connected to a wifi and have strong GPS singal.
LogPlayLevel: Error: UAT: 01-29 19:24:13.665 23280 26575 D UE : [2024.01.29-17.24.13:665][989]LogAzureSpatialAnchorsAndroidInterop: Error: Azure Spatial Anchors Session Encountered an error, ErrorCode: 4 ErrorMessage:Not enough Neighborhood Spatial Data was available to complete the desired create or update operation
LogPlayLevel: UAT: 01-29 19:24:13.720 23280 25985 D UE : [2024.01.29-17.24.13:720][991]LogAzureSpatialAnchorsAndroidInterop: Azure Spatial Anchors: StoreAndWatcherTrackedState::TryCreateInternalAsync for a new SpatialAnchor.
LogPlayLevel: UAT: 01-29 19:24:13.720 23280 25985 D UE : [2024.01.29-17.24.13:720][991]LogAzureSpatialAnchorsAndroidInterop: Azure Spatial Anchors: StoreAndWatcherTrackedState::TryCreateWithNewNeighborhoodAnchor
LogPlayLevel: UAT: 01-29 19:24:13.720 23280 25986 D UE : [2024.01.29-17.24.13:720][991]LogAzureSpatialAnchorsAndroidInterop: Azure Spatial Anchors: [MobileNeighborhoodManager::TryGetPoseBetweenAnchors] Pose computed successfully.
LogPlayLevel: UAT: 01-29 19:24:13.720 23280 25986 D UE : [2024.01.29-17.24.13:720][991]LogAzureSpatialAnchorsAndroidInterop: Azure Spatial Anchors: [MobileNeighborhoodManager::TryGetPoseBetweenAnchors] Pose computed successfully.
LogPlayLevel: UAT: 01-29 19:24:13.720 23280 25986 D UE : [2024.01.29-17.24.13:720][991]LogAzureSpatialAnchorsAndroidInterop: Azure Spatial Anchors: [MobileNeighborhoodManager::GetAnchorNeighborhoodDataAsync] Creating anchor blob using 3 key-frames.
LogPlayLevel: UAT: 01-29 19:24:13.720 23280 25986 D UE : [2024.01.29-17.24.13:720][991]LogAzureSpatialAnchorsAndroidInterop: Azure Spatial Anchors: [MobileNeighborhoodManager::GetAnchorNeighborhoodDataAsync] Does not have enough neighborhood data: NeighborhoodDataFeedback::NotEnoughMotion
LogPlayLevel: UAT: 01-29 19:24:13.721 23280 25986 D UE : [2024.01.29-17.24.13:721][991]LogAzureSpatialAnchorsAndroidInterop: Azure Spatial Anchors: [MobileNeighborhoodManager::GetQueryNeighborhoodDataAsync] Anchor neighborhood data is NOT available. Feedback: 0.
LogPlayLevel: UAT: 01-29 19:24:13.721 23280 25986 D UE : [2024.01.29-17.24.13:721][991]LogAzureSpatialAnchorsAndroidInterop: Azure Spatial Anchors: TryCreateWithNewNeighborhoodAnchor was unable to get enough neighborhood data.
LogPlayLevel: UAT: 01-29 19:24:13.721 23280 26576 D UE : [2024.01.29-17.24.13:721][991]LogAzureSpatialAnchorsAndroidInterop: Azure Spatial Anchors: OnError - Not enough Neighborhood Spatial Data was available to complete the desired create or update operation