Latest Contributions by AlexRobertson1

We seem to have a bit of an issue on Arc Pro using 3D scenes applied to a layout. Some of the outputs we need are perspective views of our city, printed at A3 and A4. Typically the workflow is to create the 3D global scene (extruded polygons, multipatch models, base map and 1m DEM) - typically this eats up about 2Gb of RAM.  Once this same scene is added to a layout, RAM usage spikes to around 4Gb (after ensuring the original scene is no longer visible in the project to free up memory). Attempting to then export as either jpg or pdf will further take the memory usage up to around 7.5Gb and near kills the PC. Once the export is completed memory usage drops again, but never down to the original level therefore gradually bringing the PC to its knees as more exports are done. Has anyone else come across anything like this/knows a work around (aside from buying more RAM)? PC specs are i7, 8Gb RAM, Nvidia K620, Windows 7, ArcGIS Pro 2. Cheers, Alex ... View more

Hi,   We have been generating a fair few 3D fly through videos of our city and whilst being a very effective way of communicating the information, there is something that happens which detracts from the experience for our viewers.   When exporting a 3D animation to a file, the renderer seems to generalise the DEM after what appears to be around 500(ish) metres away from the camera. I understand that this is likely a design decision to allow performance when rendering, but having the ground reshape itself as you move around isn't a very good look on a pre-rendered video!   Ideally, having an option/tick box that allows us to accept terrible performance when rendering (or a slide bar for distance) but drawing the DEM in full would be very handy. Perhaps then once ticked, each frame can be allowed to fully render prior to it being saved to the export file. Yes, it will take forever to run through the model and save it, but this can be run over night and would be fine.   Thanks,   Alex ... View more