nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro 3.4.0 Visualization Issues-- Bug?

KCI

Hi,

I'm having an issue in 3.4.0 where ArcPro is creating weird artifacts in multiple unique Projects. Take a look:

The 2nd image shows that it's creating these artifacts around the basemap as well-- not just the features I'm using.
This issue doesn't exist outside of ArcPro, leading me to think it's not a PC issue, such as a bad graphics card.

No idea what's happening, preventing me from asking intelligent questions.

Thanks for your help!

Finde mehr Beiträge mit dem Tag

Accepted answers

Jeremy Wright

Hi, we've seen this visual artifact in the past with older drivers, especially with Intel GPUs, when using DirectX 12. We confirmed with Intel that later versions of the drivers fixed the artifacts.

Please let us know what is listed under \display adapters in Device manager and what date/version the driver shows in its properties.

To try and work around it, switch to DirectX 11 or OpenGL in Pro's options->display tab.

All comments

danielri

ArcGIS Pro 3.4 change the default driver from DirectX 11 to DirectX 12. Ways to resolve are to (1) ensure you have the newest DirectX 12 graphics driver, (2) change default back to DirectX 11, or (3) change default to OpenGL. Graphic card options can be set in Pro's options->display tab.

Jeremy Wright

hi just checking in @Minsley @S_RossWygmans_GISS-T can you please check what version of windows shows when you type "winver" in the start->run prompt?

And can you please confirm switching to DirectX11 fixes the problem for you?

Jeremy Wright

So just to be clear here this is a bug in the Intel driver itself. Unfortunately on my Iris Xe machine I can't repro the problem. @Minsley @rwygmans can you folks let us know what OS version you're running? you can run the command WinVer from start->Run to get this info.

In the meantime, you can work around this by switching to DirectX11 in the display options for Pro.

I'm on Win11 23H2.

I've got a list of possible issues we sent to Intel just last week for the q2 driver for various hardware, I can add this once we get specifics for your platform. If you can run dxdiag and save all the info as a Txt file and share it here that'd be much appreciated. Thanks!

HilaryFBrowning

I would also like to chime in with how easy it is to switch to DirectX 11 or OpenGL. Reading through this thread made me think that I needed to install something new, because I forgot about the Display options from within Pro. So - while it may be better to fix up your actual drivers - in a pinch, just switching what you use worked for me. This is probably obvious to everyone on this thread, but in the interest of helping out folks who come here from Google:

SaraBell1

Hi, I've been having this issue with 3.4 and DirectX12. Just updated to the 12/10 Intel driver, and I'm still getting the visual artifacts. It seems like it normally starts with the terrain map, but then every basemap is affected, and the issue gets progressively worse through time/switching basemaps.

MariusVerdes

@JeremyWright I have this driver installed and switched back to DirectX 12, right now it looks like it working fine with my maps. I will come back if I see any issues.

Thanks.

Jeremy Wright

There is a new version released 12/4 - I just updated my daily driver laptop with the intel utility. If you're still having trouble in DirectX12 after updateing to the 12/4 release, please let us know if it's reproducible with all maps or only with certain ones.

Jeremy Wright

Thanks Willard. I'll forward this information to our contact at Intel

WillardGustafson_FNI

@JeremyWright I had IT upgrade the Graphics Driver and still have the issue with DirectX 12. Changing to DirectX 11 seems to be a functional work around.

Jeremy Wright

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.

ShaneONeill_144

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

Jeremy Wright

@KCI Can you please go and tell us what shows up in device manager under Display Adaptors an open it and give us driver version and date?

KCI

I switched to OpenGL and my problems went away!

Jeremy Wright

Hi everyone - if switching to DirectX11 worked (as someone has marked this as "resolved") please let us know your display adaptor's model name and driver version shown in device manager. If needed we can contact the GPU manufacturer to report it as a bug (if updating the driver version doesn't fix it for you).

Jeremy Wright

Hi, we've seen this visual artifact in the past with older drivers, especially with Intel GPUs, when using DirectX 12. We confirmed with Intel that later versions of the drivers fixed the artifacts.

Please let us know what is listed under \display adapters in Device manager and what date/version the driver shows in its properties.

To try and work around it, switch to DirectX 11 or OpenGL in Pro's options->display tab.

WillardGustafson_FNI

I'm having this same issue, Random color blocks that cover whole sections of my maps, with "holes" where labels are.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.