Hello. I am looking to locally host Cesium imagery tilesets and stream them using the file path URL dynamically. I’ve been able to successfully do this with json files dynamically (tileset.json), but some files from Cesium Ion are downloaded as xml files(tilemapresource.xml) . Is there any built in methods to load xml files using file URLs for imageries? Or will I have to convert my xml to json before loading it? Thanks in advance!
I have now found out that I have to use the TMS Raster Overlay and upload the file URL to that component, but I am now getting many errors along the lines of:
LogStreaming: Warning: Failed to read file ‘C:\PATH\20\184\622.png’ error.
LogCesium: Error: [2025-06-12 17:09:20.753] [error] [ErrorList.h:88] Errors while loading image for tile:
- Received response code 404 for image file:///C:/PATH/10/0/0.png.
Any tips on why I’m getting these errors? I downloaded the asset directly off of Cesium Ion and extracted the zip.
Hi @dyllan-aeroai,
Is the path shown in the message the one you expect? Does that file exist?
Hi Kevin,
I’ve since made some more efforts with getting this to work and I’ve appeared to gotten the local tileset to load in the editor, but I’m having some difficulties getting it to work at runtime. I’m no longer receiving the LogCesium error code 404, but am still experiencing the LogStreaming warnings and to answer your question, the png files do not exist, but the rest of the path, up until what I believe are the zoom level directories, is as expected.
More recently during my efforts to load xml files from file URL, I’m getting LogStreaming warnings which keep failing to read .png files that do not exist, but everything related to the path is correct up until the actual .png file that is trying to be loaded. I do believe that I had similar LogStreaming warning messages appear when loading from file URL in the editor, but now that I’m doing the same actions dynamically in blueprints, the same warning messages are appearing, just no imagery.
The LogStreaming warning file path also seems to be specifying the zoom level correctly. As I get closer, the zoom level in the file URL increases, and decreases as I get further. Although I do not think this is related to the issue I’m experiencing, just an observation.
In regards to the problem I was having initially, I truly just did exactly what I did the first time around, but it happened to work this time. Same file URL, same component, etc. Not too sure why but I’m not complaining!
Hello again.
I had a typo in the material layer key when spawning dynamically. Oops. Still getting those warnings from LogStreaming but do not seem to effect the imagery.
Thank you for your help.