Latest Contributions by TylerSchwartz2

I thought I would just chime in here and mention that if anyone is encountering this error, it is because I commonly find that there are customer features with a <null> STORE_ID assignment.  The tool will error out if it there is not a store assignment for every one of the customer features.  In my case, I set these to a non-existent store ID, such as "0" or "99" etc, using a select by attribute and then a field calculator on the selected features. ... View more

In terms of using ArcMap .lyr files in Pro, they do import (last I remember), but best practice is to resave all your .lyr files as .lyrx files (Pro equivalent).  The way you do this is right click your layer in the ToC and select Sharing=>Save As Layer (or something similar to that - dont have Pro open in front of me to check). This is what I ended up doing after finding that the .lyr files arent supported in Pro and that Pro uses .lyrx which is basically the same thing.  Long and short of it is that in general,.lyr/.lyrx files are not compatible between Pro and ArcMap. ... View more

We need to get Pro speeds on par with ArcMap, that will take care of 80% of the issues I personally have with Pro.  Its just way slower than ArcMap and that should not be the case.  The other 20% are the bugs and crashes that continue to persist update after update. ... View more

Yep, filled out the error report probably at least 100 times for this exact crash and Ive watched multiple versions come and go with no acknowledgement or fix ... View more

Kory, I just tested as well and I am still crashing and its reproducible. Where can I find the crash dump report and how do I get it into your hands? I outlined the process in my post above.  Raster in question is a raster derived from Kernel Density using various UTM projections (depending on what part of the country our study is in).  Perhaps I need to capture a video to better show you whats happening? Let me know on both of those points.  Out of all the crashes I get, this one is the most common and most frustrating so I would love if we can get this resolved. Pro v2.2.0 Thank you! ... View more

Good one!  Sad but true ... View more

Will do ... View more

"For example even something simple like opening an attribute table.  In Desktop, bang, open pane with first X lines, done.  In Pro it was doing some kind of indexing, analysis, calculating different font sizes, column width etc to make it all 'look nice' before opening the table, and then of course depending on docking it had to resize multiple other objects and re-render them as well." This is precisely my experience as well. But its not completely because you have a slow computer. Even with a very fast computer, it runs slow.  As you mentioned, it seems pro needs to re-render and reprocess everything anytime you click.  I am running an Intel i7 2.8ghz with 16gb ram and an NVME SSD hard drive and I get the spinning wheel anytime I click something in pro (and this is the second computer Ive run Pro on).  This is not acceptable. ... View more

Take a raster, apply a color ramp symbology to it (in my case I use "classify" symbology).  Change the source to another, different raster (right click the layer, properties, change source) and see if that causes a crash.  Its as if the classes that are set with the old raster dont match the new raster and Pro crashes because of it. The work around I have found is to remove the symbology (back to "stretch") on the raster and also hide the symbology pane first before changing the source and then reapplying the symbology after you have changed the source.  The reason I am changing sources instead of adding new data and applying symbology that way is because I have many layers setup as templated symbology styles where its very quick and easy to simply change the source of the layer (and preserving the symbology) instead of restyling all the symbology every time. I also employ saved symbology layers (.lyrx) and apply symbology to layers that way as well. I have had similar issues with polygon feature classes (like block groups) using the same process, but its less frequent and inconsistent.  I am not sure where to find the thread you mentioned. ... View more

Thomas you bring up a good point that there are some things, so specialized, that no QA/QC team will discover, and I accept that.   ... View more

To me the frustration stems from the perception that ESRI expects its customers to QA/QC their products for them by submitting arduous and time consuming bug reports (and replications) to support.  That might be fine for public sector workers, but I work for a for profit company and time is money.  We pay a lot of money for ESRI products and the level of bugs and issues that go out the door and then remain unaddressed (especially in pro) is unparalleled in my experiences with other software companies (like Adobe).  One example is that when opening a project, snapping remains on even when the snapping button (in Layout) is turned off.  You need to cycle the button twice before it actually turns off.  When the project is saved after snapping is turned off, it gets turned on again when you reopen the project (with the button showing its off).  Every time you open that same project you need to cycle the button a couple of times.  This very obvious bug has never been noticed by the dev team, despite being there for now 2 or 3 major patches?  The snapping example may not seem like a big deal (and its not) but its indicative of what I can only assume is an extremely poor QA/QC process that I can only imagine is there to save money.  There is also an issue with symbology updating causing Pro to crash when you change the data source of a layer, which has remained in Pro gosh, since 1.0.x, despite bug reports that I took valuable time to report. ... View more

I find that in Pro, even simple maps with only a few layers is very sluggish.  Even just clicking a layer (and doing nothing else) causes the spinning wheel.  Right clicking to open an attribute table, and then scrolling through the attribute table is just horrible in Pro, whereas in ArcMap its highly responsive and fast....  I have installed Pro on two different computers with the exact same results.  Its not my local settings, its Pro. Pro development team really needs to do better - Pro needs to be faster and better than ArcMap.  Despite the nicer interface and more diverse symbology options (which is great!), at the end of the day, if the program isnt at least as crisp and responsive as ArcMap, I get less work done.  I work in the private sector and efficiency/quickness with UI interactions is highly important to me. ... View more

From my understanding, the only advantage is that some video cards work better with the OpenGL architecture (although DirectX is recommend and is the most widely supported across all video card manufacturers). I have no where near any expertise on the subject, just the little bit that I know.   The first thing I would check is to make sure you have the most up to date graphics card drivers. Your settings appear to mirror my own, so it might be more related to your specific video card and drivers. ... View more

I have found that in 2.1.1 that the snapping (in layout view) is automatically enabled every time you reopen a project even though the snapping button shows its off.  You need to cycle it on then off again for snapping to be disabled.  This is a new bug introduced in 2.1.1 ... View more

Although I have not encountered this issue, I would suggest: 1) Updating graphics card drivers (already mentioned) 2) Try switching between OpenGL and DirectX and see if that makes any difference 3) Check/uncheck vertical synchronization (checking it will synchronize your screen refresh rate with the GPU frames per second, which when unchecked can cause display tearing issues) Those are my suggestions. ... View more