Windows Edge Browser And Cesium

CesiumJS
1

I have tried Windows 10 Edge on a few machines and have been getting mixed results, and was wondering if anyone else has been trying things with MS Edge, and what have the results been?

Desktop home machine works great with cesium. Some Work Laptops, thinkpads with dedicated video, Nvidia and ATIdepending on the model have been throwing errors and won't load cesium. These machins work fine with cesium and chrome 44.

Loading the "click to interact" on http://cesiumjs.org/ produces the following error message:

Error constructing CesiumWidget.
Visit http://get.webgl.org to verify that your web browser and hardware support WebGL. Consider trying a different web browser or updating your video drivers. Detailed error information is below:
RuntimeError: The browser supports WebGL, but initialization failed. Error at t (http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/CesiumViewerStartup.js:418:27331) at et (http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/CesiumViewerStartup.js:456:21442) at xt (http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/CesiumViewerStartup.js:461:27325) at A (http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/CesiumViewerStartup.js:463:669) at K (http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/CesiumViewerStartup.js:465:6157) at Anonymous function (http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/CesiumViewerStartup.js:466:16455) at i.execCb (http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/require.js:29:251) at X.prototype.check (http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/require.js:18:419) at X.prototype.enable (http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/require.js:23:233) at i.enable (http://cesiumjs.org/Cesium/Build/Apps/CesiumViewer/require.js:27:358)

2

  1. The first option, as always, is to make sure your graphics drivers are up to date. Not all vendors may have Windows 10 drivers available yet and ones that do normally need to be installed by downloading them from their website, not via Windows Update.

  2. Edge, much like IE before it, has a very aggressive black list of unsupported video cards (many of which work great in other browsers), which causes it to fall back to software rendering. In almost all cases, software rendering isn’t really an option for Cesium so it defaults to the context option of failIfMajorPerformanceCaveat : true. Can you try passing failIfMajorPerformanceCaveat : false to the Viewer or CesiumWidget contextOptions in your app and see if that fixes the problem. It should look something like:

new Viewer(‘container’, {

contextOptions : {

failIfMajorPerformanceCaveat: false

}

});

This means it will use software rendering, but it should work (even if slowly). I may try and convince the rest of the team to go back to the original default (false) so we favor compatibility over performance.

3, Also, if you can post the webglreport.com output from one of the failing machines, that could help too.