Issues getting World Terrain data from Ion

I’ve been using Cesium as an out-the-window visualization for an aircraft sim for a couple of months now. Everything was set up and working fine up until Sunday (3/15/22) where I was attempting to add additional controls for a VR headset. I no longer see terrain in the editor and the project now crashes upon play with the following error message:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000000


Other threads suggest this might be an issue with the camera size or using remote desktop to edit the project, so I created a brand new project using the tutorial to see if it was directly tied to my project. However, after placing Cesium World Terrain + Bing Maps Aerial imagery and Cesium SunSky / extending the default luminance range, I get the following message in the output log:

LogCesium: Warning: [2022-03-16 10:31:31.523] [warning] [TileContentFactory.cpp:112] No loader registered for tile with content type ‘image/jpeg’ and magic value ‘???’.
LogCesium: Warning: [2022-03-16 10:31:31.524] [warning] [TileContentFactory.cpp:112] No loader registered for tile with content type ‘image/jpeg’ and magic value ‘???’.

I am no longer getting terrain data from Ion and only the SunSky sphere shows up - sky over water - in the fresh project.

I also created a project from CesiumForUnrealSamples to verify it’s not some firewall issue on the machine and the sample project works.

I feel like I’m missing something obvious and I’m not sure what else to check - any advice
or suggestions would be greatly appreciated!

Hey @cnusbaum,

That is a strange issue. I’m looking into it. In the meantime, could you try the following?

While the UE editor is closed, open Windows explorer and navigate to %userprofile%\AppData\Local\UnrealEngine\4.26 . Delete the cesium-request-cache.sqlite file inside that directory. Then, reopen the project.

Please let me know if that happens to resolve this.


That fixed it! I should have posted on Sunday, haha.

Thanks for the help! Let me know if there’s anything I can do to help troubleshoot what triggered the issue.

Glad to hear it! I’m pretty sure this issue is caused by CachingAssetAccessor accidentally cache an invalidate response · Issue #152 · CesiumGS/cesium-native · GitHub. The weird part is that the error message you got was totally different than the error message that I thought was associated with that problem. Also not sure why this seems to have been popping up more often lately.

Out of curiosity, when was the last time you updated the plugin? What version of the plugin are you on now?

Using 1.11.0, updated when I saw the notification in the launcher. I believe I updated late last week and was having no issues initially.

FWIW, I have the project on two machines (dev & deploy). The deployment machine is the one that had the issue, so perhaps copying the project between two machines caused it?