No more maps shown on my computer (WebGL issue)

[scalvin1]

Describe the bug Since about 23.5.2023, the latest WebGL map plotting code does not seem to work on my hardware anymore. I tried it on this machine in Firefox/Linux, Chromium/Linux, Firefox/Windows, Chrome/Windows, Edge/Windows. The F12 Firefox Console shows me the following error pointing to a feature issue in the WebGL graphics stack:

Error: {"requestedAttributes":{"alpha":true,"stencil":true,"depth":true,"failIfMajorPerformanceCaveat":false,"preserveDrawingBuffer":false,"antialias":false},"statusMessage":"WebGL creation failed: \n* tryNativeGL (FEATURE_FAILURE_EGL_NO_CONFIG)\n* Exhausted GL driver options. (FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS)","type":"webglcontextcreationerror","message":"Failed to initialize WebGL"}

Not sure what changed, but it used to work well. Now unfortunately all I get is a blue to grey vertical gradient color area where the map should be (see example attached). On other hardware (newer PC), all seems well now. (I noticed on my phone FF browser, that things were changing and map/baro were sometimes broken on Tuesday/Wednesday requiring a cache clean/ browser restart to work again.)

To Reproduce Open any flight in any browser/ OS on my Dell Latitude E6410 notebook.

Expected behavior Show maps as before 23.5.2023

Screenshots

Device (please complete the following information):

• Device: Dell Latitude E6410, integrated Intel graphics.
• OS: Linux and Windows
• Browser Firefox, Chrome, Edge

00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 
(prog-if 00 [VGA controller])
        Subsystem: Dell Latitude E6410
        Flags: bus master, fast devsel, latency 0, IRQ 26
        Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at 70b0 [size=8]
        Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915
        Kernel modules: i915

https://browserleaks.com/webgl report:

[flyingjoe]

@scalvin1 Thanks for reporting! We had another (less detailed report) yesterday. ~We currently can't reproduce this on our own devices and are happy about every report (with system information) we come across. @scalvin1 have you tried doing a hard reload (Strg + F5)?~

[flyingjoe]

@scalvin1 we were able to reproduce this bug. It only happens in Mozilla based browsers on Windows (MacOS works), all chromium based browsers work fine.

[samuel-git]

As the WebGL report shows, your machine is lacking WebGL 2 support. We thought this would be widely available but it seems some have issues due to old hardware.

Currently checking the best way forward. Maybe revertig back to previous version.

[scalvin1]

Sure I have tried Ctrl-F5 many times, also different Browsers on different OSs (Windows/Linux) on this Dell Latitude E6410 machine, with the same negative result as described with all my browsers(!). (Just to be ultra-paranoid, I have cleaned caches/everything and tried on pristine accounts.)

Further data point: Identical OS setup on a newer machine proves to me that this issue is not due to the Browsers or OSs. They all work on different newer hardware with identical software setup (latest browsers in Win11 and Debian 12). To say it clearly: on better/newer hardware, this issue does not exist in any browser. They all work. FF, Chrome, Edge.

So as I said in the initial post, I think that changes on Weglide side are now using WebGL features that my present hardware here refuses to use or does not have. Maybe this will point you into the right directions. I hope you can go back to not using those new features or to have given hardware check if the are available, and if not provide a (slower?) fallback to the older version? Please let me know if there is anything I can do to help out!

[scalvin1]

As the WebGL report shows, your machine is lacking WebGL 2 support. We thought this would be widely available but it seems some have issues due to old hardware.

Currently checking the best way forward. Maybe revertig back to previous version.

Now we got our last posts crossed over. Indeed, we came to the same conclusion. Thanks!

[scalvin1]

@scalvin1 we were able to reproduce this bug. It only happens in Mozilla based browsers on Windows (MacOS works), all chromium based browsers work fine.

This may be coincidental. I think it depends on hardware features of the WebGL stack, not on browser type. Some setups may be using a software based WebGL (?) and this would mask such hardware issues.

[samuel-git]

We reverted back to old maps. Should work now when your WeGlide updates. Thanks for the awesome detailed report.