Graphical glitches within map window

[Glasnoct]

This recently started occuring on my coworkers instance of ArcPro and we haven't been able to track down either a solution or a cause so I'm asking here whether anyone else might have an idea. When zooming around with any combination of map layers (this does not occur if all layers are turned off) random large colored squares/rectangles appear to be drawn. Colors doesn't seem to correspond to anything and the blocks appear to be drawn below layers that show geometry. anti-aliasing seems incredibly poor as evidenced by the blocky, stair-stepping between the labels/geometry and the graphical glitches. Messing around with all the graphics options within Arc doesn't make it go away, though clearing the graphical cache seems to make it go away for a little bit. As far as we can tell, nothing recently changed with the program or our system drivers or something of a similar nature. I don't get this error on my end with the same layers, hardware, and Arc version.

 

[JeremyWright · Accepted solution]

Greetings!

I have seen these incorrect tiles of content occuring in DirectX 12 when we tested on certain Intel GPUs.  We reported it to Intel and they were able to resolve it in a newer driver version.

So first off, please open device manager and go to Display Adaptors.  If you open the properties of the listed adaptor it will tell you driver version and date.  Please post here with that info.

To try and work around this problem, I would recommend:

1.  update the GPU driver from the manufacturer's site (AMD, Intel or NVIDIA) or from the laptop manufacturer's site.  

2.  Switch in the Display tab of the application options menu from DirectX12 (which is the default in 3.4) to DirectX11 (which was the default in 3.3).  You can also try OpenGL.

Give it a try, and let us know the results!

[Glasnoct]

In the process of further trying to troubleshoot this issue we discovered my coworker's laptop was missing it's discrete video card (the only one in the office missing one). Switching to one that had one fixed the issue and being that these Thinkpads are running Intel CPUs I think it lends credence to the issue you outlined as it didn't show up until he updated to 3.4

[AndreasSouropetsis]

Something very similar happened to me just recently as well, ArcGis Pro was recently updated but nothing major has changed with regard to settings on the laptop. It often takes the form of large red rectangles that appear and vanish as I move around or zoom in a map (my image shows this), however it has occasionally been different, including similar to what was shown in the example image from the original poster. I have asked colleagues and our tech support, and no one seems to know what the cause is. After seeing this post I have tried to change from DirectX12 to 11 as per Jeremys instructions which may have worked since the issue is now not appearing, however it was never active 100% of the time before. I also just now checked for all sorts of updates, including drivers and seem to be up-to-date but will bring this up to our tech support, and perhaps they will investigate further.

[JeremyWright]

Andreas we confirmed on the other thread reporting this issue that the user was as I suspected, a driver bug in Intel GPU.  https://community.esri.com/t5/arcgis-pro-questions/arcgis-pro-3-4-0-visualization-issues-bug/m-p/156...

If you have an intel GPU, you may need to use their driver support assistant to get the latest driver updates, if your manufacturer does not provide an updated driver.  https://www.intel.com/content/www/us/en/support/intel-driver-support-assistant.html 

Note that the bug existed in the driver before, but Pro 3.4 changes default graphics API to DirectX12.  So you would have had to switch to DirectX12 manually in PRo 3.3 to see the same issue. We originally identified this issue in the Intel drivers in Pro 3.3 during the alpha release phase

[ShaneONeill_144]

 BUG-000172455 : Layers in map do not render after upgrading to ArcGIS Pro 3.4 with rendering engine set to DirectX 11

[JeremyWright]

Shane,

Not sure why you're posting this here?  The reported issue you tagged is seemingly unrelated to this one, and the solution of updating to a newer driver and/or switching to a different rendering API has already been accepted. 

Regards,

Jeremy W.