I’m going to start this thread because my issue has been going on for a week, in case I’m not the only one having an issue
I am about to test v1.28, hoping my hardware bug has been fixed in this release. Hannah, please wait to respond until I test the v1.29 update.
I have been developing a WordPress plugin to support an online Google map of daily avalanche forecasts since October 2013, and was excited to discover the initial release(s) of Cesium in the Fall of 2014. For three years plus, I have been developing the Cesium map as a replacement for the Google map; the inability to clamp-to-ground geoJSON polygons in Cesium has forced me to use the 2D Google map for 3 Winters… NOW, I finally have the functionality in Cesium to use it for my avalanche forecast map, but my hardware is aging (and I’m an unpaid volunteer…).
My Cesium development and initial testing are on localhost using a Windows7 laptop with Intel HD graphics chipset, for which the newest available driver is 8/31/2011, which may limit this hardware’s support for the latest WebGL 1.0.3 standards published 10/27/2014, but I haven’t had any problems on this laptop yet…
As soon as I have a stable version on the laptop/localhost, I upload the code to a GoDaddy server, running WordPress on IIS, and test the online Cesium map using several additional devices & browsers. My wife usually gets an email from me, when my latest Cesium map is ready to test in Safari browser an her iPhone, iPad, and Mac laptop…
I test Cesium in Chrome on Android using my Samsung S5 phone, which was new when I started this project 3-4 years ago; its also the mobile device that the snow rangers use(d), who post the daily advisories. I’ve never had a problem running Cesium on the S5, including initial 1.27 clampToGround implementation, which was rendering polygons on terrain during some brief tests before I updated Cesium to 1.28
Since updating Cesium to 1.28, I’ve had inconsistent results reproducing this bug in Chrome on my Samsung S5 device; maybe its my hardware, maybe its my code, maybe its the Cesium core…?
- Cesium map occasionally initializes okay, but geoJSON polygons render on the WGS84 spheroid, underneath the STK terrain, only visible in 2D, and briefly in 3D before view renders image provider tiles over the terrain (these same polygons render correctly clamped-to-ground in Chrome on Windows7); eventually, in this state the map fails with a FragmentShaderFailedToCompile error
- Cesium map will not initialize at all, renderer fails with error message regarding FragmentShaderFailedToCompile
- Briefly today, the map initialized okay; the geojsondatasource polygons rendered underneath terrain; geoJSON point billboard and markers displayed okay on terrain, but the map crashed with an array index, when removing datasources from the viewer - maybe this one is caused by my code…?
- Late yesterday, the Chrome browser crashed with a FragmentShaderFailedToCompile error initializing the home-page demo on Cesiumjs.org, failing several tries; this demo/test has never failed on the Samsung S5 before; it’s had a few knocks, maybe this phone is having a unique issue; I was not sure if the cesiumjs.org demo is still running 1.28 or 1.29… the demo still crashes today, after restarting the phone…
It should look like this: