Latest Contributions by JeremyWright

Hi folks, we realize this and related ideas have a good deal of interest from our user community. We added an ArcGIS Pro SDK method that allows export of an Area of Interest of a Local Scene to an STL file at ArcGIS Pro 3.5. Documentation on this API is available here: https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic32384.html This method creates an .STL file from the specified extent, including all compatible content in that extent.   Since it's only available via SDK, I haven't marked the IDEA as implemented yet, we hope to have a product team build UI/UX for this in a future release, and we'll continue to expand the capabilities of this API in future releases on the backend as well. ... View more

We added "export warnings" to the export experience, warning users if anything went wrong with drawing or exporting their PDF/AIX etc, in the 3.5 release of ArcGIS Pro. This includes notifications when a layer will rasterize due to symbology, as the original poster reported. For more info on Export Warnings in ArcGIS Pro 3.5, see the help at https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/export-a-map-or-layout.htm#ESRI_SECTION1_F796217224664085BFC33DEA5F75C3F0 Please give it a try, and let us know if you encounter any other unexpected changes to your export that are NOT enumerated on the Export Warnings report. ... View more

hi just checking in  @Minsley @S_RossWygmans_GISS-T  can you please check what version of windows shows when you type "winver" in the start->run prompt?   And can you please confirm switching to DirectX11 fixes the problem for you? ... View more

So just to be clear here this is a bug in the Intel driver itself.  Unfortunately on my Iris Xe machine I can't repro the problem.  @Minsley @rwygmans can you folks let us know what OS version you're running? you can run the command WinVer from start->Run to get this info.    In the meantime, you can work around this by switching to DirectX11 in the display options for Pro.   I'm on Win11 23H2.   I've got a list of possible issues we sent to Intel just last week for the q2 driver for various hardware, I can add this once we get specifics for your platform.  If you can run dxdiag and save all the info as a Txt file and share it here that'd be much appreciated.  Thanks! ... View more

@ErikBreedon yeah, we knew it was hard to detect unless you're looking for it.  To that end - this upcoming release (3.5) we worked with the layout team and now you'll get a warning when anything triggers rasterization during export.  So at least you'll know when something goes a little askew during your export in 3.5 and later! ... View more

this one got fixed in ArcGIS Pro 3.4, marking as Implemented ... View more

As per the description, the behavior described is As Designed for "screen sized" symbols, and the workaround is to not use these types of symbols in a scene when draped on the ground.   ... View more

Folks, I'm marking this "In Product Plan" because ArcGIS Pro 3.5 will expose a new SDK function that allows you to export an AOI (specific extent) of a local scene view to STL.   I'll update this thread with a link to the SDK documentation once Pro 3.5 SDK is released. caveat: There isn't a BUTTON for this on the UI yet, and the STL export will require some post-editing to be really 3d printable, but I wanted to get this out into the hands of our users as soon as it was ready to go.  We'll work with a product team to find a place to expose this in the Pro UI in a future release. ... View more

I've marked this idea as In Product Plan and it'll change to Implemented when we ship Pro 3.5. NOTE: The defect being reported here is a result of the anti-aliasing applied by the viewing application to partially transparent raster tiles in the PDF.  There are tiles in PDFs in ArcMap too (to allow allocating smaller chunks of memory to write the raster content into, and to allow the loading application to allocate memory in smaller chunks while reading it), but ARcMap didn't support transparency in raster content - it all got flattened together into opaque raster tiles.  So you can only SEE this artifact with raster content with alpha channel transparency, which you can only write from Pro.     We've gone back and forth with Adobe about this for years, and there are even settings in the Page Display options dialog for Adobe Acrobat that can help - BUT, you can't set these from the document in the PDF spec as it stands currently, and since PDF is now an ISO spec we can't ask Adobe to change it without the ISO spec needing to be bumped too. We know this is a huge impediment for our users.  As such, we've engineered a workaround for this problem, adding an option for users to export their raster content as a single tile in the PDF in ArcGIS Pro 3.5.  This will remove the tile boundary lines in displaying the PDFs and still allow you to keep the layers in your PDFs.  However, it can cause larger exports to fail if you're using higher anti-aliasing options or if the resolution and page size requested is very large, because it has to allocate a large block of contiguous memory to complete during the export process.  Adobe Acrobat or other viewing applications might also have problems allocating larger blocks of contiguous memory to display these PDFs. Please give this new option a try in ArcGIS Pro 3.5 - it has already been tested with positive results by our early adopter program participants at a few different large/national mapping agencies. ... View more

you didn't post a picture but this could be a known issue with certain GPU drivers (usually intel integrated graphics) and DirectX12.  Try opening display options and changing the Rendering Engine to DirectX 11 instead.  If this fixes it then you can update your GPU drivers from computer or GPU manufacturer's site to resolve the issue permanently. ... View more