Latest Contributions by JeremyWright

If you build the map with CM on, and the user opens your ppkx or mpkx WITHOUT color management enabled in their viewing application, then it's not likely to look correct.  Color management is an application setting so its enablement is not saved in the project, so you'd need to instruct the user to enable it to get same results. ... View more

from the help: https://pro.arcgis.com/en/pro-app/latest/get-started/color-vision-deficiency-simulator.htm "An applied color simulation mode is also not included when exporting the map, layout, or report to a file, exporting to an animation video, or when sharing to a web map or a web scene." the tool is meant to be a way to check how your cartography works with those with color vision deficiency, not a way to export for those who have a color vision deficiency.  The recommended workflow would be to ensure that (for example) different symbology classes are still distinguishable/distinct when using the deficiency view, then modify the symbology if there are issues. ... View more

The checkerboard pattern indicates that the mosaic dataset's image data links are broken. See https://pro.arcgis.com/en/pro-app/latest/help/data/imagery/repairing-paths-in-a-mosaic-dataset.htm ... View more

The ArcGIS Pro's required platform architecture is x64.  The ARM64 architecture is not supported by Esri for ArcGIS Pro at this time.   ... View more

@RiaanBotes this sounds like you might be experiencing an issue with hardware acceleration. Do the following as a troubleshooting step: 1.  open the shortcuts menu (press F12 to bring it up) 2. under "global" check the box for "Drawing Performance Overlay" (This enables this shortcut, which is by default disabled) 3.  with your map view active and focused, press shift-E.  This will bring up the performance overlay. 4.  Post a screenshot.  Does it say "DX11" or "WARP" at the beginning?   as a preemptive step, you can also try running the system requirements evaluator at https://links.esri.com/run-arcgis-pro-33x - this report should let you know if your machine meets the minimum or recommended requirements for Pro 3.3. ... View more

This feature is already under consideration for a future release of ArcGIS Pro ... View more

Hi @MarcelSt-Germain sorry for the delay.  Here's an update on this:   1) The Layout team has a bug in their backlog to investigate ways to make the "preparing to export" phase more cancellable. 2) I reached out to support, unfortunately they were not able to recover the repro case you gave them due to a failure of the machine's storage.  Unfortunately this means that the repro case you sent was not able to be used by Development to debug the problem.  If possible we'd like to receive this repro package again.   I can send you an ad-hoc FTP server info if you are willing to upload it again. 3) Layout team also confirmed that at this time there is no way to avoid the "preparing to export" phase, but a suggested workaround is to export using the python window.  Below I've pasted a simple example script to export a layout using Python. The difference in using Python is that it does NOT require the clone - it exports directly from the already-opened view.  So it's worth a shot for sure in this particular case. sample python commands to export to PDF from current layout.  You can paste this into the Python window when you have the layout you want to export open in Pro. Replace the path with your desired values.   ##Export to PDF import time aprx = arcpy.mp.ArcGISProject("CURRENT") aprx.listLayouts() for lyt in aprx.listLayouts(): #Parameters: output name, resolution, image quality, compress vector graphics, image compression, embed fonts, layer attributes, georeference, jpeg compression, clip to elements, output as image, embed color profile #Image quality: "BEST", "BETTER", "NORMAL", "FASTER", "FASTEST" #Image compression: "ADAPTIVE", "DEFLATE", "JPEG", "LZW", "NONE", "RLE" #Layer attributes: "LAYERS_ONLY", "LAYERS_AND_ATTRIBUTES", "NONE" start = time.time() lyt.exportToPDF(f"C:\Temp\{lyt.name}.pdf", 150, "BEST", True, "ADAPTIVE", True, "LAYERS_ONLY", True, 80, False, False, False) end = time.time() print(f"{lyt.name} exported in {end - start} seconds") print("Done") ... View more

@MarcelSt-Germain I understand.  I am working with support to try and find the data shared last year with the support analyst, so we can get to the bottom of why this particular map/layout causes this problem. In the meantime I can talk with the team responsible for this UI to see if there's any other workaround we can provide - I agree it's infuriating when the stop/cancel button is not honored! ... View more

Hi Marcel, This step in the export process is making a copy of the persistence of the item being exported, so it can happen in the background and not block the UI. Unfortunately it sounds like you've run into a situation where that process is taking too long... It'd be great if we could get the repro case from you as a PPKX (share->Project package) - I can reach out separately to get your email and we can set up an ad-hoc FTP share to get your repro. In the meantime, you can workaround this issue by exporting using the Python window with the ArcPy.MP API (which won't make a copy before exporting) to export the map or scene or layout you're using.   Also be aware there have been many bug fixes and performance enhancements in releases since 3.1 - it might be worth considering updating to 3.2.2 to see if the problem has been resolved since then.   Looking forward to hearing from you!   Regards, Jeremy W. ... View more

Thanks for confirming  - I'm glad that you have engaged with product managers (kory and valeria) on this - I will leave the responses and follow-up to them on the specific topics you mentioned.  We are in pretty regular communication. For the original poster (@SteveJudge) question - I have answered it I believe, but I encourage them to reply if they have any further questions in this regard about the system requirements checker they originally asked about. ... View more

@RTPL_AU the issue you are reporting has to do with UI lag and responsiveness.  In the past, have you reported your concerns to Esri Support so that teams responsible for the UI can troubleshoot these problems?  If you have specific feedback or repro cases, we can ask the teams responsible for these UX evaluate and profile them to determine the cause of the delays. ... View more

Greetings, Unfortunately the checker is a web-enabled platform, so offline mode is not supported for it. BUT, we do have a subset of this functionality built into the app, specifically for the GPU itself.  The diagnostic is built into the Graphics engine itself. If you open Pro and open a "new global scene" (has to be a 3d view at this time) you will get a "no supported graphics adapter" warning if you don't have a GPU that meets min requirements as reported by the GPU driver. There's details about this warning here: https://pro.arcgis.com/en/pro-app/3.1/help/mapping/properties/unsupported-graphics-hardware.htm note this uses a different code path than the web checker, but should give similar diagnostics. We have considered adding this to 2d views in the past, so I'll bring that up with the team during our next planning sprint. Regards, Jeremy W. ... View more

@JoeBryant1 UPDATE: we have worked with Adobe and also determined that a specific setting in Acrobat causes the display artifacts.  One workaround we know of at this time is to have the user uncheck this option.  Please see https://support.esri.com/en-us/knowledge-base/problem-grid-lines-display-in-pdfs-exported-from-arcgis-000022758 ... View more

I would encourage everyone asking for this functionality to review the discussion here https://community.esri.com/t5/3d-mapping-questions/scene-exporting-to-image-instead-of-vectors-in-svg/td-p/1229801 If you are experiencing a situation in which the scene _does not draw at all_ in the exported SVG - that sounds like a bug and should be reported (and the repro case shared) to Esri Support. ... View more