On Thursday, August 18, 2016 at 12:36:18 PM UTC-5, Scott Haynes wrote:
> The computers that are having a problem are on a closed network, so we can browse on the internet. :(
Scott,
The source for the webglreport page is up on github. Link is on the webglreport page. If you're going to be testing different hardware on your isolated network, you might want to consider pulling down the source for the page, scan and sneaker net it over to your isolated network, and host it on the same machine serving your cesium page.
I had issues with flakey performance and used the diagnostics from how webglreport pokes at your browser and gpu to determine the root cause was a rather anemic GPU...
On another network it was a rather obscure IA/IT security policy someone pushed to the browsers to turn webgl support off. Recent browser build, but crippled by an unannounced security pivot. Wasted a good 6 hrs chasing my tail thinking I'd broken something :(
I find having a local webglreport web page as valuable as the sandcastle environment.
Just a thought.
-f