Select to view content in your preferred language

After Update to 3.4 raster layers are not showing and other are transparent

595
7
11-11-2024 03:08 AM
Labels (1)
GottfriedKenda
New Contributor

This morning I worked with ArcGIS pro and all my projects where open normally and I was able to work on them. Then I installed the newest update and now I cant see most layers from my projects anymore. Also when i try to create a new projects layers are transparent or doesn't show up at all. 

What is going on and how can i fix this?

GottfriedKenda_0-1731323302140.png

 

7 Replies
DanPatterson
MVP Esteemed Contributor

right-click on a raster layer in the table of contents and select ... zoom to layer

Does it appear?  

If so, then the raster needs a defined coordinate system

Define Projection (Data Management)—ArcGIS Pro | Documentation


... sort of retired...
0 Kudos
GottfriedKenda
New Contributor

if i click on zoom to layer it is zooming to the extend but still not showing any raster layers. tried also to create new project just with data from living atlas and it is also not showing anything

0 Kudos
DanPatterson
MVP Esteemed Contributor

run the check on this page

ArcGIS Pro 3.4 system requirements—ArcGIS Pro | Documentation

and review your video (Directx etc) since the recommendations for video have changed


... sort of retired...
0 Kudos
ShaneONeill_144
Esri Contributor

It would be worth trying a clean uninstall and reinstall of ArcGIS Pro

I've seen this fix many similar issues in the past

TammiDoyle
Occasional Contributor

I'm having exactly the same issue. Currently uninstalling. I think this is a bug.

edited to add: reinstall did nothing. Now not even the base maps aren't displaying. I wonder if this is to do with new Windows 11 incompatabilities?

0 Kudos
TimCoulombe_DES
New Contributor

I was having the same issue. Changing the Rendering Engine to DirectX12 from DirectX11 in Project-->Options-->Display fixed it. 

TimCoulombe_DES_0-1733928577962.png

 

 

TammiDoyle
Occasional Contributor

Oooh Tim, you legend. How on earth you found that solution is beyond me, but it appears to have fixed the issue. Thanks for that!

0 Kudos