Hi there,
I’m currently developing an AR game for a specific location.
I paired Google and Cesium to render a detailed map and used Cesium’s Anchors to fix my hotspots in place.
The issue I’m having is the following:
This guide here: Placing Objects on the Globe – Cesium tells me to place my hotspots object inside a game object that has a Georeference component attached to it.
I’ve put them as children of my AR Georeference Origin game object, however, the hotspots game objects do not render while playing or building the game.
Additionally, if I put the hotspots outside of it, I will see them again but will shift and change position every now and then.
Is there a way to render them in a fixed position and stop reading GPS signal continuously? I guess this would minimize shifting.
My XR Origin contains the default Unity One, I’ve added an AR Earth Manager to it. The camera is stored inside of it, like in the standard XR Origin prefab.
My AR Session is the default one.
AR Core Extensions is all wired up and the ARCore Extensions Config has “Enabled” in Geospatial.
My Geospatial Controller “AR COMPONENTS” section of the script is filled with everything needed. I’ve left the second part empty since i’m using another interface.
My AR Geospatial Creator Origin contains two Sub-Scenes, one for Malaga and one for Avebury, England. Each of those has some Hotspot game objects containing my game logics.
Each of those Hotspots has a Geospatial Creator Anchor.
Lastly, ARCore Extension in Project Setting is set with a API Key connected to a Google project where Tiles API and ARCore API are enabled.
The issues I’m having are:
Being in Malaga at the moment, I can’t see the Hotspots game objects inside the sub-scene, even if I’m inside the radius of activation and Geospatial is using the MainCamera to activate the sub-scenes.
When I load a scene, Game Objects don’t stay fixed in place, but move a lot and their position depends on the orientation of my phone when starting the application.
@Alberto_De_Caro Unfortunately, there’s only so much I’m able to help out here because only part of this is our code - the rest is Google’s AR Core code, which we don’t work on. But from what I can tell, I believe part of the problem here is that the tutorial you’re following is talking about using Cesium Globe Anchors to position things, whereas Google is expecting you to use AR Geospatial Creator Anchor components instead. Have you given Google’s quickstart tutorial & sample a try? Do you see the same issues with the cube placed in the demo level after following the tutorial that you do with the hotspots in your level?
