Blue screen with Google Photorealistic 3D tiles

I’m experiencing a problem with the Google Photorealistic 3D tiles. Out of nowhere, the screen on my project turned blue, and I can’t see the map anymore. The same thing happened to me this morning, but it started working again after around 20 minutes. I was hoping that if I waited, it would be fixed again, but it’s been more than 3 hours and no luck. If I create a new project, I can see the map, but not the 3D buildings from Google Maps.


I am getting the same thing. Google Photorealistic 3D tiles is not showing up in ion. I can see it in my javascript builds but no longer in ion.

Hi,

Thank you for reporting this behavior. We have recently had a spike in our activity using Google’s data through the Cesium account and reached our daily experimental release quota several times. Since this feature is still experimental this may mean that Cesium Stories may not load Google’s data if we go over our limit.

For this reason we ask all our users to set up their own accounts to access the Google API directly if they are building applications using Google’s data. Instructions for creating your Google API account are: https://cesium.com/learn/photorealistic-3d-tiles-learn/

Thanks,
Ankit

Thank you! I have my Google API account, but where do I connect it with Ion? I’m also experiencing other bugs. For example, every time I position a 3D object, I get an “Internal server error,” and the position is set to the initial position again. It also happens quite often that when I try to capture a new view from a slide, it stays on the loading page that says “capturing view,” and I need to restart the project.

Hi,

As I said in my previous post, unfortunately with Cesium stories there isn’t a way to let users specify their own keys since it uses our account’s keys currently. Since this feature is experimental, some unusual behavior is expected to arise but there shouldn’t be any errors. I have added this thread to an internal tracking issue for updating our Stories for the full release.

Would you be able to provide any screenshots of the error you are facing and also the errors in the browser console if you see any? And confirm that there aren’t any network problems causing the “capturing view” issue. Finally, could you try positioning your assets with a base terrain different other than Google’s tiles and see if the problem persists.

Thanks,
Ankit

I don’t think it’s my network connection that’s causing the “capturing view” issue because every time that happens, if I go back and open the project again, I can do a new capture.

I created a new project using Cesium World Terrain, and I’m having the same problem when I try to position any asset. I can position my old assets, but when I try to do it with a new one, it’s not working. I know the problem is not related to the asset I’m trying to import because I also tried uploading the same asset twice. One I imported yesterday, and it works fine, but the new one won’t save the position.

This is the error I’m getting after saving the position:

Hi,

That certainly seems like a bug. I will open a ticket for the team to look at what may be happening with this particular asset. Does this still happen if you reupload the asset now and try to position it?

Thanks,
Ankit

Yes, I just tested it out, and I’m still experiencing the same bug. I don’t think it’s a problem with this particular asset since I uploaded several ones, and none of them worked.

I also uploaded one that worked perfectly fine on previous occasions, but if I re-import it, I get the error message, and it won’t save a new position. The problem seems to be with all the new assets; if I try to re-position an old asset, it works well.

I really appreciate your help since I’m working on a project, and to finish it, I need to position different assets along the experience. Thank you!

Hi,

We have deployed a fix for the positioning issues you were seeing. Please give it a try again and reach out again if you continue to see any issues.

Thanks,
Ankit

Thank you so much. Now it’s working.