I’m trying to load the instance of the Cesium Viewer and I’m not getting any imagery. I’m almost certain this is a file path issue, since in my web application the Cesium files have been added down in a sub folder of the base application files. I thought there was a global fille path variable in Cesium that could be defined when this issue occurs? I see there are some default imagery files in the Assets folder, so I would expect those files to be getting loaded if they can be found.
Hi @Scott_Haynes,
Thanks for your post and for being part of the Cesium community.
Could you tell us a little more about the setup of the app you are working on building with Cesium? This will help us give you the right advice to get it working correctly. Two common setup resources are our quickstart guide for the most basic apps CesiumJS Quickstart – Cesium and this blog with link to sample GitHub repos for building an app with webpack or vite Configuring Vite or Webpack for CesiumJS – Cesium.
Hopefully these resources answer your question but if not please send us more info about your setup and we would be happy to assist further.
Best,
Luke
I’m working with a fork of the virtual world framework. The Cesium library has been placed down in a subfolder, and I’ve added the natural earth imagery within the Assets folder. I’m having issues pointing Cesium to that new natural earth folder. I ended up writing a imagery provider service to work around the issue. I thought I remembered there being a global path variable inside of Cesium that could be set when the Assets.. folder was not found because of path related issues.