VPS with Niantic Studio - Objects don't Appear

I’m experimenting with the VPS project template in the Niantic Studio engine, following the documentation and some tutorial videos. I was running a very simple test of placing 3D objects around the given location, just to get a practical understanding of how accurate the AR positioning and tracking really is. In the simulator, the objects appear just fine. But after publishing the project and testing it on the real location, none of the objects is displayed. I’m able to see the reference mesh of the location being overlayed, but nothing else. I have some videos to demonstrate the issue, but I’m not able to upload it here since I’m a new user :frowning:

Is there anything that I’m missing on the configurations or deploy to make the objetcs appear? Is there any practical tutorial for VPS in Niantic Studio, placing simple assets with simple interactions?

Thanks in advance.

Strange that the objects would appear in the simulator, but not in real life.

Can you post a picture of your Studio window?

This is how my editor looks like. I’ve added 3 objects into the scene directly into the root hierarchy: a cube (that I created in the engine), 2 GLB instances - one that is just the mesh and another one that has a rotation animation component (thet is the one currently selected in the image below).

Below is a screenshot of what I see in the simulator (all objects appear in the proper position relative to the location).

And finally, below is a screenshot of what running the app looks like. Only the colorful mesh of the location appears (that is triggered by the code that comes as default on the VPS template).

I ran another test here, placing the desired objects as child objects of the location. With this, through the simulator, all objects will appear only when I manually trigger the “Location Found” event. Note that the colorful mesh appears when manually triggering the “Mesh Found” event. Testing it on the real location brought the same results as before: only the colorful mesh appears. This might indicate that the “Location Found” event is not being triggered. @GeorgeButler any suggestion on how to tackle this issue?

The team is currently taking a look. When you parented the objects to the location did you rebuild your project? Based on your screenshot looks like they’re still not children which is how you would solve the issue.

Yes I rebuild and tested it on the simulator. Then went to the physical location to test. The version I tested was this one with all objects as children of the location object:

Since I’m a new user I can’t upload videos here to give a better understanding of the project and the results.

Do you have any example project with VPS and with 3D objects that works? For example that one that was on the release post of VPS in Niantic Studio with the Niantic Gums?

This is what the simulator shows when it starts running:

After navigating a bit backwards with WASD and clicking the “Location Found” button, all child objects appear:

And when I click “Mesh Found”, the colorful mesh shows up:

The project is publicly published and there is no “republish” button. So I guess that rebuilding the project is enough to update the published version as well. Is this so or do I need to republish somewhere?

In order to update the published experience you have to land, and then re-publish your changes.

1 Like

When you tested the real-life scanning process were you using the QR code from Niantic Studio or the published public version?

For this test I’m using a VPS that is already activated. I didn’t scan nor publish a new location yet.
I’ll try again here to build and land to see if it changes the experience. Is there a republish button or I just need to click build and then click land?

Ok, I see now that I can select the commit that I want to have published! I’ll test the solution with the new hierarchy adjustment and leave a comment here if it worked.

I was able to test the most updated version of the project and placing all objects as child objects of the location object in the hierarchy did the trick! But it only works during the day… at night, even with good ligtinh conditions, the application was not able to localize itself. I’ll attach both pictures (working with daylight and not working at nightfall).

Just to summarize the solution in one post:

To make my custom objects appear at the VPS location I needed to:

  1. Place all objects as child objects of the location object in the scene.
  2. Republish the latest app version by clicking on: Build > Land + Publish. But we can also adjust the desired published version (after landing) by sellecting the commit to be published (under the Publish button).

P.S.: At the time of this particular experience, VPS might not work well at night.

Thank you @GeorgeButler for the help and support!

1 Like

This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.