When I open a Studio project that has VPS locations, the meshes do not load and the Location “component” (?) in the sidebar for the location entities is empty. I found that I have to open the VPS browser panel, manually navigate to the general area where the VPS locations are, and click on a location there to bring up its details before my own VPS locations load properly. It doesn’t seem to matter which location I click - just clicking anything in the vicinity causes all the VPS locations to load properly. FWIW I don’t live near the locations I’m building for, not sure if that makes a difference.
Do you have any errors in the console? Can you land your changes and share your project with the ‘support’ workspace?
No errors in the console for the Studio, just some warnings about color map textures that are being passed to materials before fully loading, which have always been there (THREE.WebGLRenderer: Texture marked for update but no image data found).
When I run the Simulator I get the typical 404 for the sourcemaps and some accumulating performance warnings.
How do I share a project with the support workspace?
Land your changes and follow this guide: Project Sharing | 8th Wall, just type support in the box that asks for workspace.
Done!
(adding more text to meet the 20 character min limit…)
Hey Jason! I’ve taken a look at your project and you’re right it looks like the locations were removed from the project.
Are you able to find the locations on the map and re-add them to your project? Or provide the names of the affected locations along with their coordinates?
Seems like the location entities are still there, but their data just isn’t loaded with the project initially. When I open the VPS browser and pan to the general area where the locations are, then they all automatically load and work normally in the project. Looks like this also affects the VPS options in the Simulator - I can’t select any location until they’ve been forced to load this way.
I removed one of the locations in the scene hierarchy, re-added it, then refreshed the page, but still none of them load with the initial project load.
The 3 locations I’m using are:
- ABG - Entry Figures @ 43.075143999999995, -70.759098
- ABG - 1779 Petition @ 43.07503, -70.759018
- ABG - Burial Vault & Community @ 43.074777999999995, -70.758845
FYI these are Private Locations, so I’m curious if they aren’t accessible to you.
On initial project load
After panning to the location area in the VPS browser
If you remove them from your scene and re-add them from the map do you see the location data appear in the viewport?
When I remove all 3 locations from the scene and re-add them from the map, they all load in the viewport as expected during that session. But when I refresh the page to load the Studio fresh again, they do not load.
Something interested I just noticed - if I just open the map and do nothing to it, then select any VPS location in the scene hierarchy, that location (and only that location) loads in the viewport and its data in the right sidebar loads automatically. It seems like the VPS system is not being initialized until the GSB map is opened.
Im also seeing this behavior in my VPS Studio projects fwiw
I’m having the team look into this now. Can anyone who’s experiencing this issue confirm if the VPS localization process is affected by the missing locations?
@GeorgeButler I can try later today. Right now I only have a test location, I might be able to get to a public location later today. Will keep you posted. Thanks for looking into this!
@GeorgeButler I could not reproduce the problem with a test location or a public location. Only my private locations have trouble loading in studio. I’ll be able to confirm later this week if this prevents localizing irl. Thanks!
Hello, some of my locations are not loading as well but say they’re there. Also, when I scan other locations that should work, the items in their location don’t appear. Something I believe is wrong with VPS and is causing both of these issues
I’m using 3 private locations in my project, and all 3 were localizing in person up until this week (it was the Studio that was having rendering issues originally). Starting yesterday, 1 of the locations is no longer localizing in person, rendering in Studio, or loading at all when trying to view the mesh in the GSB.
The person who is doing scanning and testing on-site for my project is reporting that they were unable to submit new scans for one of the locations this morning, and some new scans for another location he submitted are not showing up even though the location was reactivated. I’ll have them reach out about that separately, but I’m curious now if there are outages or critical issues going on in the VPS system?
@GeorgeButler it looks like VPS is not working at all in the Simulator now. When I set my location dropdowns to one of my VPS locations, all I see is a white background with my 3D content kind of floating in space. I can’t move at all with WASD or mouse.
This seems to correspond to some UI changes in the Studio - the Simulator controls have changed to a pause and play button in the top-middle of the screen, and the ability to connect live device via QR code is gone.
I hope these VPS issues can be prioritized and resolved quickly, since it sounds like I might not be the only person who can’t work on projects at the moment! 
White screen in Simulator pane
Console log
The ability to connect a device isn’t gone, it’s moved to the bottom of the window. Also I’m seeing Playback work as expected; we’re moving closer to how Unity play and pause works.
Thanks for explaining that! I just checked the Simulator again and after a couple hard refreshes and rebuilds it seems to be working again, so hopefully that was just an issue on my end!
I’m able to work on my project again, but the original issue around meshes not rendering in the Studio viewport until the GSB is panned to the general area is still happening. Let me know if there’s any more I can do to confirm or investigate that.
I can confirm the mesh not loading in Studio does prevent alignment in real life.
My method: I waited for the mesh to load by navigating to the location area in the Geospatial Map. Only after the mesh was loaded did I land and publish. I have one location that consistently does not load in Studio. I published this effect before the Location component was loaded. This location would not track in person while the others did.
