Help with VPS Location, Activation Limits, and Studio vs. Code Editor Workflow

Hi, we’re working on an AR installation in 8th Wall Studio using VPS and have a few questions:

  1. VPS Location:
  • The location mesh shows uneven ground, but it’s not in real life. Any suggestions to resolve this? This affects the accuracy of the 3d animation’s position/placement.
  1. Activation Limits:
  • How can we restrict activation to specific spots and prevent triggering from irrelevant locations (e.g., across the street)?
  • Is there a way to accurately determine the user’s coordinates at activation?
  1. 8th Wall Studio vs. Code Editor:
  • Can we work with code files exclusively within a Studio project, similar to the Code Editor?
  • Is there a way to bridge Studio and Code Editor for a single project?

Any advice or insights would be greatly appreciated. Thanks

Hi @chaeng_son ! I’ve done my best to address each question below:

  1. Are you able to share a photo of / link to the VPS Location so we can take a look in more detail? You might consider adding 5+ more scans and reactivating the location.
  2. Are you currently facing this issue? If so, are you able to share a video? A photo of / link to the Location would also be helpful to help us analyze this issue. Our VPS uses the device’s location and camera feed behind the scenes for localization, you shouldn’t need to do anything manually; however, you can always call navigator.geolocation.getCurrentPosition() to access the device’s coordinates.
  3. Technically it is possible to use code files exclusively within Studio but I would not recommend this at all, it will make development more challenging than necesarry. If you want to develop with code instead of with a visual editor, you should subscribe to the Pro Plan and develop your experience with A-Frame or three.js in the legacy code editor. You can access a code editor within Niantic Studio to add custom components/behaviors. For example, see this custom component in our This or That sample project.