I have met and exceeded the recommended spec to run pro, but it is so very slow to do just about everything. Any Ideas?
1. Please contact technical support so they can help you through this issue.
2. Can you elaborate on what is slow? Is the UI greying out? Is the map display jerky? More specifics will help to figure out where the problem may lie.
Once data is loaded from a local source, it becomes unbearable to zoom, pan, and even identify. I can't even begin to try any processioning, because the application freezes. The ribbon does grey out, and the data being displayed is very large in size and blurry.
From your comments it sounds like you're in Scene view (Global or Local) in 3D. Is that correct?
quick diagnostic: with the map view focused, press shift-e to bring up a diagnostic readout overlaid on the map display. This will tell us some more about what's going on. Please post a screenshot of this here.
Some troubleshooting tips:
1. Update your graphics card driver _From the Manufacturer's website_ (not from Windows Update)
2. try switching to OpenGL (in Project->Options->Display tab)
3. Please run the diagnostic linked here and post your results: Can You Run It?
No I was in the Map tab. I have completely removed the software and re-installed it. It now seems to be working correctly.
I tried this just to see what happens and got the following:
Can you shed some light on what information is being reported here or direct me to some useful info that would explain it please?
I can't see the image you posted. was it an image of the "can you run it" tool results?
The diagnostics say:
DX11 High 68.470 (7.070) FPS 74 Tri/F 0.01M Tri/sec | MemMb VB 0.77
Tile 0 E 0 C | Unlocked | 832x522
I’m not having any problems running Pro but I had to exclude it from scanning by my antivirus software.
I had planned to write up a blog post about this (still on my list).
The first section shows you're in DX11 and you're in "High" rendering detail (you can control this from Display Options).
The second section shows average framerate, and Min framerate over last few seconds.
Third section shows Triangles processed per frame and per second.
third shows memory being used for different buffer types. Last section shows how many Elevation and Color tiles are being processed (this means ground and other elevation sources, if Any). These will be 0 for any 2D view.
The readout also shows the size in pixels of the client area being rendered (map view)
Unlocked is a developer thing you should never see anything other than Unlocked
Did your antivirus flag it as a virus? Or are you saying you are excluding its file read/write actions from the antivirus scanning for the sake of performance? What Antivirus software are you using?
Yes, I excluded it from the anti virus scanning software (Sophos). My desktop was slow as well when I was online, probably because it was trying to connect to argis online so I excluded that too and they are both start up much quicker.
Thanks for the reply to the post. That will be a useful blog!
How did you get it to stop using ArcGIS Online? I suspect this is what is causing mine to be so slow as well. For exmaple, it automatically loaded an Esri elevation source in the Scene tab. I don't need this as I have a bunch of TINs which have their own elevation data and I want my imagery draped on that. It's silly Esri are assuming I want their elevation data when I have my own. Even sillier to see my TINs draped on their elevation surface!
You can verify whether it is using AGOL by using a debugging proxy such as Telerik Fiddler. This gives a report of each http access. You can even add a "time elapsed" to the readout so you can see how long each request is taking. It's a powerful (and free) troubleshooting tool for any web-enabled application.
If you want to remove the default elevation, you can do so from map properties->elevation surface.
Remove the reference to elevation3d.arcgis.com to remove the global elevation source coming from ArcGIS Online.
If you want your TIN data ONLY as an elevation, don't add them as layers in the map. Instead, ONLY add them in the elevation surface dialog as elevation sources for the ground. this way you won't see them draped on the surface at all, but you'll still be using them directly as elevation for your imagery. This support got even better at 1.1 as we added lighting support rather than baking the lighting into the TIN.
Thanks for your help. I want to be able to see my TINs because it's easier to see if they are valid rather than with something else draped over them. So I guess I'll have to add them as elevation sources and as layers.
Fiddler is installed, any tips how to do the operations you're talking about with it?
By the way, one really important function of ArcScene for me was being able to compare visually the elevation of two layers, such as bottom of contamination vs bottom of excavation. I can’t see how I’m able to do this in ArcGIS Pro. I found that when I dragged a bunch of TINs in, it grouped them all under the ‘ground’ elevation surface. This is not correct because these surfaces cover the same location horizontally. It would be better if when dragging a new DEM into Pro it would ask you into which surface group, if any, you want it to go, or if you want to create a new surface.
If you want your TINs to be separate surfaces, you can achieve this by removing them from ground, and adding individual "surfaces" on the Elevation Surface dialog under map properties. Then each individual surface's TIN (if you want the symbolization) will have to be changed to be "on surface 1" or "on surface 2" on the Elevation layer property page. Does that make sense?
Does Pro support Proportional Symbology? Also is there a way to get the measure tool to display in inches?
the measure tool will display in any units you ask for. Just click on the options drop-down.
PROTIP: If you don't see the units you want, go to Project tab->Options->Units tab. here you can set the default (using the radio button) or ADD a unit (say, if you want to measure in Smoots).
also Brig, we do support proportional symbols in Pro (graduated symbols, graduated colors).
What I am trying to do is have my pipeline draw based on pipe diameter. I want the pipe to be drawing not in a graduated scheme but in a true size. So if the pipe is 90 inches, I want to have it be drawn at 90 inches on the map. This is currently possible in ArcMap.
sounds like you want to do attribute-driven size, and use "real world sizes". The former is available from symbology properties pane, the latter is available from the Display tab in layer properties.
If you're looking for where to set the proportional symbols it's a bit hidden away.
Select a point feature layer > Symbology > Options > Review connected attributes.
I agree, Pro is incredibly slow on routine functions. Good example, I have a class with ~2,000 fields, in 10.3 I can set layer visibility in in 15 seconds. In Pro it takes nearly 15 minutes, 5 minutes to load all the fields into the grid and 10 minutes to cycle through each field after clicking save.
Secondly, there is no way to save the visibility setting so this painful process needs to be repeated over and over.
To be fair, some of the more intensive tasks, such as spatial join, are faster in Pro.
Tested with a table that has close to 2000 fields and Field Views loaded all the fields in the view in a minute. Would you please share the File GDB that contains the table you are having an issue with? Send it to our Support team through an incident.
In Fields View, you can save any edits made to the layer properties using the 'Save' button in the view ribbon. Is the button not enabled?
GDB is too large to send, however you already have the data. The class I was working with is the ESRI 2014 demographic data for block group centroids. I inserted the class into a new project, opened the field list, unchecked visibility on everything except the ID field.
I realize I can save my edits for this specific class. What I was referring to by not being able to save the field settings was as in creating a .fvl file.
Also paging through hundreds or thousands of variables is very tedious in the table view. What is needed in Pro is the equivalent of the field visibilities (BA). With this tool it is quick to filter for desired fields, add or remove from visibility group, and if desired save these settings to apply to another class or the same class in another mxd (project). It is distressing to see such good functionality being degraded to the table view method of field control.
Staff Technical Analyst
Corp. Prop. - GIS
P Please consider the environment before printing this e-mail.
I just wanted to add a little to this discussion because this thread kept popping up on my search for sanity. A little history, started Pro with 1.0 and am now up to 1.4. My typical pattern would be: I would say to myself "I should test out Pro again to see if it is working ok", so I will start a new project. The software would run fine, so I would add more and more to the project thus getting deeper in to debt with the software. After a couple of days it would start hanging up, start random crashes, and eventually become unusable. I would then issue a support request and run through the default procedures: Upgrade the Graphics Card, remove Space Patterns tool box, etc etc, and eventually Repair the software. After that it would seem to work enough to get my project complete and out the door. I then wouldn't touch Pro for weeks/months because of my trust issues with it. Then a new release would come out and I would treat Pro like an ex-girlfriend and say to myself "Ohh she is looking good. Maybe this time will be different, she's proably changed..." only too realize she is still temperamental and unhinged.
All this leads to today: I think two modifications I have made have helped. I have an NVIDIA graphics card, and I had to turn on the Antialiasing - Transparency option to "Multismaple" within the NVIDA Control Panel. The next change and this I feel might be the important one. As I was changing my display settings back to OpenGL (I've switched many times to try to resolve my issues btw), I noticed that the display cache was at 36 Gigs!!!!!! HOLY MOLEY. With that storage it was pushing my storage threshold on my hard drive to over 90% capacity which I think is what was making my machine go a little bonkers. When going through the ESRI procedures we would eventually repair the software, and that would clean the cache thus allowing me to operate the software to get my projects out the door. This all feeds into my narrative of I would start out in pro fine but eventually crapola. What I can ascertain is as I would build the project up, I was eating more and more of my storage with the cache getting so large until I would hit some threshold of available space and boom it would all stop working. I'm going to continue testing, and am hopeful I have found the culprit. Hope this helps someone.
Thanks for this note. I have experienced exactly the same thing and searched for sanity. I've gone through all the recommendations to speed things up and no matter what I do, Pro is still significantly slower than Desktop even when working with data that is local. And it crashes. I so wish that your suggestions to clear the display cache (which only had a couple hundred MB), and setting the multi sample for antialiasing suggestions had worked, but alas, on my machine there appears to be no difference. GP tools take anywhere from 30 seconds to a couple minutes longer to complete in Pro than Desktop. I just wanted to thank you though because I take solace in finding others out there who are experiencing similar frustrations. I want Pro to work, and I want / need to incorporate it into my teaching and research, but ..... I too have the "trust issues".
Just as a follow up, it's been about a month since I've kept tabs on my cache, other than random crashes (typical in ESRI software) the performance is substantially better. All that being said, there are many features unavailable in Pro that make it more difficult than Arcmap to use for quick analysis. For the life of me, I can't figure out why they didn't develop a field statistic option with a right mouse click as found in ArcMap. If you want to total your area field, for instance, you have to run the Summary Statistics geoprocessing. I didn't realize how much I depended on that small simple tool until it became unavailable.
As a side note you can run python to calc your area
x = [row for row in arcpy.da.SearchCursor("layer", ["Shape@Area"])]
Note that Summary Statistics Workflow in ArcGIS Pro is in the product plan for Pro. We'll hopefully see that this year.
I have been experiencing slow drawing speed in ArcGIS pro 2. I have noticed this most when I have a layout, versus a scene. I had been originally working in 1.4, but just upgraded to 2.0, I cleared the cache, and switched to webGL. I have been working with this file, which is large, for a few years, and this slow behavior just started recently. I cannot figure out what changed.
Any ideas why it is slow?
Same issue here. Using ArcGIS Pro 2.0. Tried to open a geotiff fil (870 mb) but just got stuk. I'm running on a server (dual 12 cores Xeon, 128 GB ECC DDR4 RAM and Nvidia Quadro 4000). The same file opens in seconds in QGIS and ARCMAP. I have tried OpenGL and DirectX options, cleared cache, set options to low/fast but nothing seems to be working. ESRI should really work this out. ARCGIS PRO is bricked and useless at the moment.
Can you guys take a look at the troubleshooting procedures listed here? In particular if you could provide a screenshot with the framerate showing (shift-e with the view focused to see the framerates) that'd be a great first step before calling Support directly. If it says WARP you're using the CPU to emulate GPU, probably due to needing a driver update or reinstall for your graphics hardware.
I have just updated the Nvidia graphics driver. I noticed there's improvement but still slow. I did two things to further speed up my processing:
1. Build pyramid for raster data. This made opening huge raster files instant.
2. For large vector data, I applied query to display subset of data. This also speed up rendering.
It's ok now. I can live with Pro but still feel a little let down since I'm trying to make transition from QGIS to ArcGIS.
Attached is a frame rate screen capture. I have created this map with this dataset repeatedly in the past year.
One day I opened Pro and it just would not load anymore.
This is a large dataset.
What happens when it "will not load"? Do you get an error? Does the application crash? While you're not getting the best framerates I don't see anything alarming in the polygon count or FPS shown above.
The map will not load the data. It draws and draws, but eventually after a long time it freezes.
Also, when it takes this long to draw, I am concerned not all features have drawn even if it looks complete.
OK usually divide and conquer is the first step - turn off ALL the layers except basemap and turn them on one by one until you find the one that takes a long time to draw. Then create a layer package of that layer and open it in a fresh map. Still slow>?
The map package works. Thanks
So, repackaging the map and opening the package it all works?
Hello, The map package worked that one time. I still cannot get the program to run most of the time.
it just hangs and the graphics get fragmented.
I have to close it and re-open it.
I've had some performance issues with clipping and also doing large select by location functions. The latter got so bad I had to go back to ArcGIS Desktop to complete the work. It took about 3 seconds to do it in Desktop.
Jason, what type of database are you working with (file gdb, enterprise (if so, what RDBMS, versions))? Where is the data stored - local drive, network share, etc.? I realize that these don't necessarily isolate the issue if it takes a long time in Pro and seconds in ArcMap. That makes it seem the issue is with Pro...
Can you give us some steps to reproduce? What does the Select by Location look like? How many features in the Input Feature Layer? What Relationship? How many Selecting Features? Search distance, etc.? If you could list out steps and provide zipped data, that would be great. I understand that you may not be able to provide data here, but this is a good candidate for a technical support case which will be a more productive way to troubleshoot what is happening and if needed, get the issue directly to the development team.
It was a point feature layer in a gdb. It was a simple select by location where the points were completely within a polygon. No search distance anything like that. Maybe 800-1000 features in each polygon. I'll be happy to send some data if you want to send me an email.
Thanks, Jason. I just messaged you an email address.
I have found that ArcPro is slow and freezes when I create a layout.
When is ArcGIS Pro slow; i.e. what are you doing in Pro that is slow and what is the performance comparison between Pro and ArcMap?
Have you run Can You Run It? from the ArcGIS Pro system requirements page? ArcGIS Pro 2.0 system requirements—ArcGIS Pro | ArcGIS Desktop
If it is freezing up when creating a layout, I would recommend logging a case with technical support. There will be some standard questions they'll want to go through to help troubleshoot what is happening. There are also a couple of blogs (Part 1 and Part 2) called WWTSD (What Would Tech Support Do?) Part I | Support Services Blog Reading through these will give you an idea of the troubleshooting process. Working through some of this on your own may help you figure out what is happening, or at least get things pretty well narrowed down before opening a case.
I hope this helps. Please do reach out so that we can help get Pro running smoothly for you!
I am running 3 (2.5) D models of a large parcel dataset, So I have not modeled this in ArcMap. I can test in arcScene.
I have not run the run it tool I will see that, but I'm not sure what that will do, I ran ArcPro successfully for months.
I will look at the blogs, Thanks!
Map View + Attribute Table & Map refreshes constantly whilst editing. Seems like every mouse click triggers a map & attribute table refresh (3000ish polygon records)... very painful experience. The same layer in ArcGIS for Desktop behaves much better... very poor experience with Pro (2.0.1) so far
Ryan, I'll message you offline to see if we can connect and maybe get a copy of your project and data to take a look at the issue.
I had problem with Arcgis pro .First I got a blue screen during the work and shut my pc down . I solved this problem by update the BIOS. But my ArcGIS pro was still very slow and crushed again and again . This problem is solved too , by replacing the old graphic card with a new one
I'm running a Dell Precision M6800 with 16GB RAM, Intel Core 1704940MX CPU @ 3.10CHz 3.30 GHz with NVIDIA Quadro K5100M. My my tech's machine is running a newer more robust machine: 64 GB ram, Intel Xeon CPU E5 2637 v4 & 3.5 GHz (2 processors), NVidia Quadro M5000.
Both machines handle Pro fairly well, but I am not seeing the vast improvements I would expect from this new multi-threaded 64bit app. Also, there are random latency issues my tech and I experience. Not deal breakers but annoying. Sometimes changing a symbol could take 10 seconds for the processing bars to go away and then update. Turning a layer on could be instantaneous or could take a few seconds. This seems to vary by the day and by project. In addition, geoprocessing doesn't seem to be enhanced from ArcMap, some even feel they take longer to complete.
Do others have these type of issues?
In addition, I wanted to know if those who are having a good experience with Pro, can give us their computer specs and workflow environment?
I'm running a machine well in excess of the minimum, and I too am puzzled by how Pro seems to do many things much slower than Arc. For example, changing symbology where the data is coming from SDE makes Pro so slow as to be unusable. Each change to a symbology property recalls all of the data from the SDE. This is not the case in ArcMap, where any change to the exact same SDE-sourced symbology is instantly reflected.
I'm not sure if this thread is still being followed, but I'd just like to chime in with my experiences as well. I'm trying to work through one of ESRI's 3D visualization tutorials in Pro, but can't even pan the map with 3D trees enabled.
I have followed the steps recommended earlier in the thread with zero success. Below are my results from Can You Run It? and the in-Pro diagnostic tool.
My drivers are all up to date, and I was running Pro with no other programs open while recording those diag results.
I reviewed the info you sent in, and with a bit of searching it appears the GPU you are using was a low-cost part (<$50.00) when it was released circa 2010 or so. You will also note that AMD considers this "legacy" hardware - meaning it does not actively update the drivers: https://support.amd.com/en-us/download/desktop/legacy?product=legacy3&os=Windows%2010%20-%2064 (Anecdotally I have an old HP laptop at home with the mobile version of this GPU...)
So unfortunately, while it "ticks all the boxes" WRT the system requirements, there are inherent limitations to its 3d capability and capacity. That is why the "recommended" requirements mention 2GB VRAM.
You can see in the readout you sent the "Tex" shows 608MB. This means textures alone are consuming more resources than your GPU has. These resources when this occurs will start paging out to system memory, and this incurs a substantial performance hit.
SUM: Your current GPU has very limited resources and is a "legacy" product per the vendor.
a GPU upgrade (if possible) will definitely give you much better performance in 3D workflows. I think you'll find that a GPU with 2GB dedicated VRAM can be had for a reasonable price, that would give you a much better experience.
FWIW we're updating the system requirements for Pro 2.2 (in Beta imminently) to better clarify the need for GPU resources. While the above GPU should not see any challenges in 2D workflows, it is not optimal for 3D workflows.
Please let me know if you have any questions regarding the above information or recommendations.
Thanks so much for your prompt response. At your recommendation, I'll look into trying to upgrade my hardware.
Again, much appreciated!
Will the 2.2 system requirements specify for what purpose one would need the "bling" GPU (3D) versus what the minimum requirements are for most of us that do not have any need for 3D (and stubbornly will continue mapping in 2D 'till we retire). I'm having a hard time convincing upper management that we need to start getting computers outside of the normal "email checker" that is the default desktop config, on which Arc Map runs fine.
The changes we made to 2.2 system requirements boil down the shader model/level to more concise terms, and add an emphasis on dedicated GPU memory versus "shared" memory such as the integrated GPUs in Intel core i series or AMD APUs.
As to your request: while some users may prefer to continue in only mapping in 2D, Pro is an integrated 2D/3D GIS.
Consider that the ArcGIS desktop requirements previous to Pro also included GPU requirements, for usage by ArcScene and ArcGlobe.
But, if you need an argument to give your IT staff for an upgrade...
Per your readout in your post above (from 2017) you have a Quadro 600 - that GPU is an entry-level "Fermi" generation GPU. That generation of GPUs is also in "legacy" support from NVidia after the latest driver release, meaning no more driver updates.
Also the Quadro 600 has some known issues WRT "ghosting" and artifacts in UI elements when drawing on the non-primary monitor in a multi-monitor setup, probably due to some vagaries of windows' desktop compositing in modern OS versions.
We've reported this through our normal channels to NVidia, but any fixes WOULD NOT be available for Q600, due to its aforementioned "Legacy" status.
So hopefully those two arguments should be sufficient to get you a new GPU at least?
One more Q for you: did you ever send in the performance issue you reported above (issues with updating symbology when using SDE database) to support? Kory Kramer might be interested if you're still seeing this issue.
Retrieving data ...