PROBLEM
The Reality workspace in ArcGIS Pro 3.6.0 with deep learning libraries installed shows the Gaussian Splats product grayed out after adjustment. Hovering over the disabled button displays the message "Not ready for product generation. Or, option is not available due to missing prerequisites," but all other products are enabled.

When ArcGIS Pro 3.6.0 has a per-user configuration and the deep learning libraries are installed, the Reality workspace cannot check for the install directory. When a Reality workspace is adjusted with this setup, the Gaussian Splats product will remain grayed out as the system is not able to complete the requirements check.
When an adjusted Reality workspace presents this issue in an ArcGIS Pro per-user installation with deep learning libraries, the Reconstruct Surface geoprocessing tool can be used to process Gaussian Splats. The default Python environment with the deep learning libraries installed has the required components to generate this product.
Follow these steps to configure the geoprocessing tool with the adjusted image collection.


The Results folder will follow the same structure as the folders generated using the Reality workspace, and Gaussian Splats can be generated even when ArcGIS Pro was installed with the per-user configuration.
Another method that can be to install the required deep learning libraries when installing ArcGIS Pro 3.6.0 with the per-user configuration is to use the Package Manager to install the deep-learning-essentials package. This will ensure the Reality workspaces are able to find all required components, and the Gaussian Splats product will be enabled after adjustment.
Follow these steps to install the required deep learning libraries to generate Gaussian Splats products.


After confirming that the deep learning libraries were added to the cloned Python environment, the Reality workspaces will show the Gaussian Splats product enabled after the image collection is adjusted.
Note:
ArcGIS Pro per-user installation with deep learning libraries is expected to be fixed in patch 3.6.1.
Article ID: 000038918
Get help from ArcGIS experts
Start chatting now