docs: Add more output images and remove physical renderer limitation

Signed-off-by: Lagos Gonzales <214008711+gianelli-lagos-aws@users.noreply.github.com>

Author: gianelli-lagos-aws

docs/tile_rendering/images/tile_rendering_multipass_outputs.png

@@ -3,6 +3,7 @@
 *These instructions include a 3x3 tile render as an example.*
 
 Tile rendering divides a single image into smaller sections (tiles) that are rendered separately across multiple workers, then automatically stitched back together into the final image using ffmpeg (a multimedia processing tool). This approach can significantly reduce render times for large or complex scenes by distributing the workload.
+**File Size:** The final stitched image maintains the same dimensions and file size as a normal render - tile rendering doesn't affect the final image quality or size, only the rendering process.
 
 ## Important Notes About Tile Rendering
 
@@ -16,32 +17,41 @@ Tile rendering divides a single image into smaller sections (tiles) that are ren
     * JPG/JPEG (smaller files, lossy compression)
     * TGA, BMP, HDR, DPX (also supported)
 
+### Fleet Type Compatibility
+
+**Service Managed Fleets (SMF):** AWS-managed compute resources where Deadline Cloud automatically handles software installation. Tile rendering works out-of-the-box with automatic ffmpeg installation via the `deadline-cloud` conda channel.
+
+**Customer Managed Fleets (CMF):** Your own compute resources that you manage. CMF can use their own conda channels or package management. For tile rendering to work, ffmpeg must be available on worker nodes either through:
+- Pre-installation on the worker nodes
+- Custom conda channels that include ffmpeg
+- **Important:** If using conda, ensure your existing conda channels either include ffmpeg or don't conflict with it. Conda searches channels in order and will fail if an earlier channel has an incompatible ffmpeg package, even though `conda-forge` is automatically added as a fallback channel.
+
 ### Automatic Configuration
 
 When you enable tile rendering, the submitter automatically:
 * Adds `conda-forge` to the Conda channels (a community-maintained package repository that provides ffmpeg)
 * Adds `ffmpeg` to the Conda packages (a multimedia processing tool required to stitch the individual tiles back into the final image)
 * Sets the frame range in render settings based on your "Tiles per Axis" value (e.g., 3x3 tiles = frames 0-8)
 
+**Note for CMF:** The `conda-forge` channel is added to the end of your channel list. If your existing channels contain an incompatible ffmpeg package, conda will use that instead of the working version from `conda-forge`, potentially causing tile stitching to fail.
+
 ### Current Limitations
 
-* Using a Redshift renderer and camera
 * Adding Render Tokens to the output paths
 
-## Instructions:
+### Renderer Compatibility
 
-### Initial Setup
+* You can use any renderer (Physical, Redshift, or Standard) for your scene
+* **Important:** The reference camera used by the Render Tiles camera must be a Physical camera, regardless of your scene's renderer
 
-#### Configure Render Settings
+## Instructions:
 
-1. Go to "Render Settings" and set "Renderer" to "Physical"
-![Add Physical Renderer](images/physical_renderer.png)
+### Initial Setup
 
 #### Set Up Camera
 
-1. Add a default camera object to your scene
-2. Ensure the camera is using the Physical renderer
-3. Position the camera to properly frame the objects you want to render
+1. Add a default physical camera object to your scene
+2. Position the camera to properly frame the objects you want to render
 
 #### Add Render Tiles Camera
 
@@ -88,8 +98,22 @@ When you enable tile rendering, the submitter automatically:
 ### Access Results
 
 1. Once the job completes, download the output
-2. Open the output folder to find the "stitched_output.tif" file containing your final rendered image
+2. Open the output folder to find your final rendered image(s):
 
-**File Size:** The final stitched image maintains the same dimensions and file size as a normal render - tile rendering doesn't affect the final image quality or size, only the rendering process.
+**If you selected REGULAR IMAGE only:**
+- You'll find `stitched_output.tif` containing your final rendered image
 
 ![Tile rendering outputs](images/tile_rendering_outputs.png)
+
+**If you selected MULTI-PASS IMAGE:**
+- You'll find `stitched_multipass.tif` containing your multi-pass rendered image with all render passes combined
+
+![Multi-pass tile rendering outputs](images/tile_rendering_multipass_outputs.png)
+
+**If you selected both REGULAR IMAGE and MULTI-PASS IMAGE:**
+- You'll find both `stitched_output.tif` and `stitched_multipass.tif` files
+- Each represents the same scene but with different rendering data (standard vs multi-pass)
+
+![Multi-pass tile rendering outputs](images/tile_rendering_regular_and_multipass_outputs.png)
+
+