Graphics Layers not showing in MapView - possible graphics card issue

[FC_Basson]

I have an issue with graphics layers on one of our PCs - graphics layers are not visible at all on a 2D MapView.  I can confirm that the graphics are indeed in the graphics layer items, with correct geometries and symbology.  This happens with the JS API (4.29) as well as in AGOL webmaps, so the issue is not on the code side.  When I switch from 2D MapView to 3D SceneView, using the same Map, the graphics layer is visible in the 3D SceneView.  The browser used is WebGL2 enabled, as can be confirmed by visiting https://get.webgl.org/webgl2.  The PC uses only an internal Intel Graphics card (no GPU) and has only 8Gb RAM.  Could the PC resources be the issue here or are there some other tests I can do ?

[FC_Basson]

I got a reply from the client and interestingly enough, the graphics of the Feature Layer example (2nd link) are visible, but not the graphics from the example in the first link.

[FC_Basson]

Hi @mgeorge 

I can confirm from a second client, also with a Intel HD Graphics 4000, that the same issue persists in the MapView for the Graphics Layer.  The Feature Layer displays correctly.

[mgeorge · Accepted solution]

Thanks for the information! We got access to an old machine with an Intel HD 4000, and can confirm the issue. At the moment though, because these chips are so old and no longer supported by the manufacturer, we do not plan on patching for this right now. We can try and investigate installing a workaround for this driver bug in 4.30, especially if more people start running into this. 

Edit: At the moment we do not have plans to workaround this driver bug due to how old these devices are. 

[katsick]

@mgeorge any updates on 4.30 release? we are also facing this issue. we have more than 100+ of our customers with Intel HD 4000, who are blocked to upgrade to 4.29 because of this.

[mgeorge]

Hi @katsick, 

Unfortunately due to how old these devices are & given that they are no longer supported by the manufacturer, we do not have plans to try and create a workaround this driver bug at the moment. 

Matt

[FC_Basson]

We have tested a different solution for some users, which seems to solve the issue.  On Windows the default graphics backend is D3D11.  If you change this to OpenGL, the graphics and feature layers seem to be working as expected.

To change the graphics backend, go to chrome://flags/#use-angle (Chrome) or edge://flags/#use-angle (Microsoft Edge), change the "Choose ANGLE graphics backend" option to "OpenGL" and relaunch the browser.