I've noticed that when I move from using the CDN api (<script src="http://www.webglearth.com/v2/api.js"></script>)) to the locally-hosted '/v2/api.js' implementation, it's displaying a wide range of errors (in the order of thousands!) in OSX Safari 10.0.1 that aren't problematic in Firefox or Chrome (OSX, 10.12.1). This is seen on both a local python server, as well as my live production environment.
The plugin itself is initialising, and you can see the markers appearing and animating at their correct co-ordinates. The issue seems to reside in the rendering of the sphere itself.
The CDN hosted version works without a problem, so the obvious solution at the present is to use that. However, I thought I'd let you know that these errors exist if you weren't already aware.
On a related note, there seems to be a problem with both the locally hosted and CDN versions in IE11. I am aware this has been previously reported however. (Below from Edge 20.10240)
I'd also like to say a massive thanks to you for this project, I'm adapting it into a collateral site at present and while I'm possibly pushing the plugin to it's upper limits, it's a great piece of code. So thanks for putting in the hard yards developing it.
Hi @klokan
I've noticed that when I move from using the CDN api (
<script src="http://www.webglearth.com/v2/api.js"></script>)) to the locally-hosted '/v2/api.js' implementation, it's displaying a wide range of errors (in the order of thousands!) in OSX Safari 10.0.1 that aren't problematic in Firefox or Chrome (OSX, 10.12.1). This is seen on both a local python server, as well as my live production environment.The plugin itself is initialising, and you can see the markers appearing and animating at their correct co-ordinates. The issue seems to reside in the rendering of the sphere itself.
The CDN hosted version works without a problem, so the obvious solution at the present is to use that. However, I thought I'd let you know that these errors exist if you weren't already aware.
On a related note, there seems to be a problem with both the locally hosted and CDN versions in IE11. I am aware this has been previously reported however. (Below from Edge 20.10240)
SCRIPT5022: RuntimeError: The browser supports WebGL, but initialization failed. Error at t (http://www.webglearth.com/v2/api.js:428:16014) at H (http://www.webglearth.com/v2/api.js:462:31759) at Dt (http://www.webglearth.com/v2/api.js:473:4281) at Y (http://www.webglearth.com/v2/api.js:563:475) at Anonymous function (http://www.webglearth.com/v2/api.js:636:356) at initialize (http://fintech.ipventures.com.au/:67:9) at Anonymous function (http://fintech.ipventures.com.au/:475:4) at i (http://fintech.ipventures.com.au/node_modules/jquery/dist/jquery.min.js:2:27146) at j.fireWith (http://fintech.ipventures.com.au/node_modules/jquery/dist/jquery.min.js:2:27856) at ready (http://fintech.ipventures.com.au/node_modules/jquery/dist/jquery.min.js:2:29705) api.js (462,31759)
I'd also like to say a massive thanks to you for this project, I'm adapting it into a collateral site at present and while I'm possibly pushing the plugin to it's upper limits, it's a great piece of code. So thanks for putting in the hard yards developing it.