Latest Contributions by JeremyWright

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. ... View more

Hi James, 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. RECOMMENDED RESOLUTION: 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.   Regards, Jeremy W. ... View more

If it's the same MAP inside the layout, then changes to the map will propagate to other layouts that contain the same map. If you want to have different layer visibilities inside different layouts, you need to create 4 different maps in your 4 different layouts. ... View more

Just to clarify: we are using a different method of writing text into Pro PDFs that retains many of the advanced parameters such as intercharacter spacing in text placement.  So we can't just switch back to the way that ArcMap did it without bringing back some existing issues in text placement in ArcMap exports. We are evaluating a way to resolve this that does not lose those properties, and we'll put it in when we have a solid fix. As a workaround, we found that it is possible to select ALL the text in the string and then retype the new string.  I know it's not ideal, but that should at least let you replace the strings or edit them as needed. ... View more

Glad to hear it.  We do realize this is a little confusing - so in a future release we plan to consolidate/improve the UX disparity between feature caching and layer visualization caches. For now, the PROTIP is to disable the feature cache AND the display cache if you know the features will be updated frequently (such as when they are edited externally). ... View more

Kevin (and others) - one thing to consider is that you may need to disable the Feature Cache.  This is done from the workspace rather than on individual layers.  Click the data sources view on the TOC (looks like a geodatabase can), find the workspace your web layer is in, right-click on it and choose Disable Feature Cache.   ... View more

So, repackaging the map and opening the package it all works?   ... View more

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>? ... View more

Sarah, 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. J ... View more

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. https://blogs.esri.com/esri/arcgis/2016/07/26/pro_performance_troubleshooting/ ... View more

We also see this on certain NVidia models (Quadro 600) in our holistic lab.  We will report it to NVidia as it appears to be a driver issue. ... View more

Theo, You're running on a machine that doesn't meet the minimum requirements for ArcGIS Pro.  As such, your user experience will be severely degraded. The readout says WARP - that means your GPU is being emulated by the CPU.  This is because you're using a Citrix version that doesn't support GPU acceleration. Probably the easiest way to explain the need for an upgrade to your IT staff would be to run the "ArcGIS Pro system checker" - it should fail on the GPU requirement: http://links.esri.com/run-arcgis-pro See also the blog posts here for example: https://blogs.esri.com/esri/arcgis/2014/06/30/38908/ https://blogs.esri.com/esri/arcgis/2015/03/08/arcgis-pro-in-vmware-horizon-view/ Please let us know if you have any further questions or concerns in this matter. Regards, Jeremy W. ... View more

OK.  Packaging it puts it into another GDB. So...sounds like you'll need to call support directly to try and figure out why it's not drawing direct from your GDB. ... View more

please package up your repro and send it in to Esri Support ... View more

Our devs took a look and we've got some ideas.  Thanks for reporting! In the meantime, Akos has the workaround - the Layer 3D to Feature Class tool. ... View more