|
POST
|
Brian, Please send in the error reports when you receive a crash - those all go into prioritized queues as well and we do demand-based triage on them. FYI - If it's crashing WITHOUT displaying an error report dialog, the most common culprit is a system level driver - usually the GPU driver. You can try updating to the manufacturer's latest (nvidia/AMD or if it's a laptop, the laptop maker) and also can try switching to OpenGL to try to alleviate the crashing. Also FYI we've made some significant changes that will be available in the next release of Pro that should help mitigate GPU driver issues as well as out of memory conditions. I tried to look up the numbers you gave above but couldn't find them in my interface (I can only see BUG numbers, not support incidents) - so I'll send them to our support liason and get details on them. Regards, Jeremy W.
... View more
09-23-2016
04:19 PM
|
1
|
0
|
1222
|
|
POST
|
Rachael, I checked with the Data Management group's product owner and he let me know they do have a plan to improve that experience at a future release of ArcGIS Pro. Thanks again! Regards, Jeremy W.
... View more
09-22-2016
11:20 AM
|
2
|
1
|
2154
|
|
POST
|
Brian, Thanks for your feedback. If you can give me a rundown of the issues you've experienced and reported (similar to Tyler's BUG number list) that have affected your workflows, that would definitely help us to evaluate their priority. Regards, Jeremy W.
... View more
09-22-2016
11:17 AM
|
0
|
2
|
3287
|
|
POST
|
Tyler, The first of your two reports is already assigned to a developer for investigation. The second is in the triage queue, assigned to the owner of the symbology queue. As I explained earlier, every defect reported to us is prioritized based on the number of customers reporting, the evaluated impact to the user, and many other factors. This reprioritization happens on a daily basis, and we also have people in support working regularly to advocate for issues that they have seen particular customer impact from. On the development side, we also have a triage queue and myriad prioritization strategies. Tyler if you have an issue you feel is severely impacting your workflows you can also call to escalate said issue or suggest a revision to the repro case or description. If the bugs in the ArcMap/BA queue that you mentioned are in this category, I'd encourage you to talk to support and lobby for their modification - perhaps the existing defect report doesn't properly convey the severity of the issue and can be modified to better communicate the effect it has on your workflows. Also keep in mind that that many ArcMap bugs may be limitations of the architecture (for example, issues with output and print due to GDI limitations) - and some of the most "popular" of these were a major part of impetus for us to build ArcGIS Pro. As Dan said and Adrian reaffirmed, thanks for taking the time to report. All bugs reported to Esri do matter, and we try to address them in the order of their effect on our users' ability to perform useful work with our software. Regards, Jeremy W.
... View more
09-22-2016
10:29 AM
|
3
|
0
|
1222
|
|
POST
|
Rachael, What type of data are you trying to make these fields changes to? (GDB, SHP, feature service, etc.) Also, is it consistently reproducible? Regards, Jeremy W.
... View more
09-22-2016
10:00 AM
|
0
|
3
|
2154
|
|
POST
|
Brett, Please report this issue to Esri Support, so they can get this assigned to the appropriate dev team. regards, Jeremy W.
... View more
09-21-2016
02:07 PM
|
0
|
0
|
3067
|
|
POST
|
Folks, You may have noticed Pro is releasing several times a year, whereas previously our desktop products had an 18-24 month release cycle. So we're releasing on a regular rhythm and hope to keep the tempo for the foreseeable future. Yes, Pro is a little more complicated than a browser to update, so I don't see updating once a month (externally) as a feasible goal in the foreseeable future. And we have done some patches even more quickly as needed (for instance, current version is 1.3.1 - a dot-dot release). Daniel, just FYI: I've been in contact with our support liaison about the issues you had reporting bugs, and she's actively looking into this issue as well to see if there's a way to make reporting bugs even more expedient. Regards, Jeremy W.
... View more
09-21-2016
02:03 PM
|
2
|
0
|
3287
|
|
POST
|
Pie charts are not yet available in Pro layer symbology. It is on the roadmap for a future release.
... View more
09-19-2016
02:12 PM
|
2
|
7
|
5367
|
|
POST
|
Ugh. OK can you please contact Esri Support directly with details? They'll have you give a report of machine config and send in any crash reports you have received. They will also want to retry the installation of the microsoft patch (maybe with installer logging turned on) so they can see why it fails to install.
... View more
09-19-2016
02:10 PM
|
1
|
1
|
1369
|
|
POST
|
Dan, At each release we add more functionality and fix more bugs. We release several times a year. ALSO at each release the product teams and doc team update the "what's new" document and "known issues" FAQ pages in the help and at http://pro.arcgis.com The current release is 1.3, and we have the following documents that list the information you seek: What's new doc: What's new in ArcGIS Pro 1.3—ArcGIS Pro | ArcGIS for Desktop Release notes (issues addressed): Release Notes for ArcGIS Pro 1.3—ArcGIS Pro | ArcGIS for Desktop FAQ: Frequently asked questions—ArcGIS Pro | ArcGIS for Desktop Regards, Jeremy W.
... View more
09-19-2016
02:02 PM
|
1
|
0
|
3287
|
|
POST
|
Adrian, How would you like to report a bug? On the front page of http://support.esri.com are many methods to contact support. To wit: you can use email, interactive online chat, or direct phone calls. I'm in the trenches on the development teams - so I'm a little removed from the website and support tiers, but as far as I know Geonet is (like esri forums before it) primarily a user-to-user resource, though many Esri staff do keep an eye on it as a matter of their day to day work. Bottom line is if you want a bug to be resolved, we need to have a report of it through support. What does that mean for you, the users? 1. Error reports: if you get a crash report dialog, put in your email and other info about the repro case if you know it. Development does respond to users on occasion (no, not everyone) to gather more information about a particular crash. If the dmp is too big to send via the normal reporting mechanism, please email it to us. FUN FACT: at Esri's major conferences (DevSummit, EsriUC) we collect error reports from each machine at the Esri showcase directly so we can triage and prosecute any errors encountered by users or employees during the conference at the showcase. 2. When you encounter a bug, SEND IT IN to Esri support through whatever means necessary. We have extensive tests, including literally thousands of automated tests over many many different harnesses that are run on multiple platforms, databases, and web browsers, and we also conduct in-house testing in our first-floor holistic lab as well many times a week. We test the dickens out of ArcGIS Pro and indeed all our products, but sometimes what it takes to repro a bug is users' unique data, perspective, or workflow. If that issue is not reported, it's a tree falling in the woods. DO NOT just report it on geonet - send it to support. Even if you find out that it's already been reported, support tracks the number of times a particular issue is reported and regularly audits those issues for development to prosecute based on demand factors. Hopefully this info is helpful to you folks here. Thanks! Regards, Jeremy W.
... View more
09-19-2016
01:55 PM
|
5
|
0
|
3646
|
|
POST
|
Daniel, Rest assured we hear you and we strive to fix lots of bugs each release. Please _report_ any bugs you find to Esri Support. We can't fix them if you don't tell us about them - and reporting them gives them a lifecycle (you get a tracking number) and also lets other users affected by same issues add their reports, which increases priority of repair. Regards, Jeremy W.
... View more
09-19-2016
01:26 PM
|
2
|
6
|
3646
|
|
POST
|
Carlos, If you get a crash on starting a new map, most likely crash is occurring on initialization of view. This probably means GPU problems. Two things to try: 1. update your GPU driver from manufacturer (of card if desktop, of laptop if laptop). e.g. Nvidia or Dell. 2. Try switching to OpenGL in Project->Options->Display.
... View more
09-19-2016
01:24 PM
|
0
|
3
|
1369
|
|
POST
|
try pressing CTRL-F5 to force a refresh. If it still won't display package the raster layer (SHARE->Layer) and send it to Esri Support.
... View more
09-12-2016
02:30 PM
|
0
|
0
|
1201
|
|
POST
|
you should be able to use the Locate tool and type in the coordinates you want to go to. then, you can use the WASD keys to _rotate_ the camera without moving it.
... View more
09-12-2016
02:28 PM
|
0
|
0
|
1342
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 12-12-2023 11:54 AM | |
| 1 | 12-11-2023 04:07 PM | |
| 1 | 12-13-2023 01:28 PM | |
| 1 | 11-25-2024 03:40 PM | |
| 3 | 03-07-2025 10:29 AM |
| Online Status |
Offline
|
| Date Last Visited |
06-03-2026
02:28 PM
|