Set up 3ds Max for cloud rendering on SuperRenders

3ds Max on our farm runs primarily V-Ray and Corona Renderer — the two render engines that account for nearly all archviz, product visualization, and motion design work in 3ds Max pipelines. Arnold for 3ds Max is also supported for studios that have standardized on the Arnold pipeline. This page covers project packaging, per-renderer specifics, EXR output workflows including V-Ray Frame Buffer, the V-Ray animation prepass pattern, XRef scene handling, the submission plugin install path, and 3ds Max-specific troubleshooting.

For the dedicated landing page covering supported versions, hardware fit, and pricing examples, see . For the 2027 release feature coverage, see . The cross-DCC fundamentals (upload, submit, download, account setup) live in and .

Supported versions

3ds Max 2024, 2025, and 2026 are pre-installed on every worker. 2023 is available on request for legacy projects — open a ticket before submission so the worker fleet can be configured. The farm matches your .max file's version automatically; you do not need to specify it manually in submission.

A note on 3ds Max's release rhythm. Autodesk ships annual versions plus point releases. We provision the latest GA release within four to six weeks of public availability. If your project requires a specific point release (e.g., 2026.0.2 because a particular plugin only certifies against it), mention it in the job notes when you submit; the worker fleet maintains the latest point release of each major version as the default.

3ds Max licensing on the farm runs under Autodesk render-node licensing. Your local 3ds Max license stays on your workstation; you do not need to transfer or share it with us.

Packaging your 3ds Max project

A 3ds Max project is the .max scene file plus the project folder structure. The default 3ds Max project layout includes sceneassets/ for textures and bitmap images, proxies/ for V-Ray and Corona proxies, scenes/ for any reference scene files (including XRefs), and additional folders for caches, OpenVDB volumes, and Forest Pack libraries. The farm follows the same conventions.

3ds Max's built-in Archive feature is the recommended packaging tool because it traverses asset references and copies them into a single archive. The workflow:

Set the project folder first. File → Project Folder. The Archive function uses the active project root for path resolution. If the project folder is not set correctly, Archive may miss assets that live outside the inferred root.
Run File → Archive. 3ds Max gathers the active scene, all referenced bitmaps, XRef scenes, V-Ray and Corona proxies, IES profiles, Forest Pack scatter sources, and writes them to a single archive. The default container format is .zip.
Re-pack as .tar, .tar.gz, or .7z. We do not accept .zip uploads. The simplest workflow is to extract the Archive .zip, then re-archive the contents as .tar.gz using 7-Zip on Windows, Keka or tar -czf on macOS, or tar -czf on Linux. The directory structure must be preserved exactly — re-pack from the parent folder so paths inside the archive stay relative to the project root.
Verify the archive on your workstation. Extract the re-packed archive to a fresh directory, open the scene in a clean 3ds Max session, and render a single test frame. Check the Asset Tracking panel (File → Reference → Asset Tracking) for any missing assets shown in red.

A common shortcut that does not work: copying just the .max file. 3ds Max scenes store only references to bitmaps, proxies, and external scene files, never the assets themselves. A .max file in isolation will load on the worker but render with pink "missing texture" placeholders.

For very large projects (above 300 GB), we recommend SFTP upload or the Client App over web upload — the resumable, parallel transfer is safer for long-running uploads. See for the SFTP guide.

What to verify before submission

A short pre-flight checklist, in order of how often each item causes a failed render:

Active renderer is set correctly. Rendering → Render Setup → Common → Assign Renderer determines which renderer the worker uses. Match this to what your scene actually needs (V-Ray, Corona, or Arnold).
Frame range and output path are set in Render Setup. The farm respects whatever Frame Range you specify — Single, Active Time Segment, or a custom range like 0-240.
Output filename uses a sequence pattern. <scene>_<frame>.exr or <scene>_####.exr is a safe default. Avoid absolute paths or paths with workstation-specific drive letters like D:\projects\....
Camera selection. Render Setup → Common → View to Render should explicitly name the camera you want rendered. If the field is set to "Active Viewport," the worker renders whatever camera the saved scene had active when it was last saved — which is not always the camera you intend.
Render Region and Render Border are disabled unless you intentionally want a sub-region. Both options live in Render Setup → Common; either one enabled produces a partial image with the rest of the frame black or missing.
Lighting is present. A common failure mode is a scene with all standard lights turned off and only ambient illumination — the rendered frame comes back nearly black. Verify at least one light source is active and contributing to the scene.
Render Elements / Render Outputs are configured. If you need separate AOV files (Z-depth, beauty, reflection passes, etc.), configure them in the Render Elements panel before submission.
Custom MAXScripts disabled if they reference workstation-specific paths, license servers, or external network resources that won't exist on the worker.
Asset Tracking is clean — no missing assets shown in red, no broken proxies. If anything is missing, locate and re-link before re-archiving.

Submitting from 3ds Max

Three submission channels work for 3ds Max projects:

Submission plugin (recommended). Submit from inside 3ds Max via a dedicated menu after installing the plugin from your account dashboard. The submission plugin packages the scene, uploads it, and queues the job in one workflow — the tightest iteration loop for 3ds Max work. For install steps see .
Web submit via dashboard. Upload the archived project, then submit through the website job-creation form. Works without the plugin installed; useful for first-time submissions or one-off jobs.
Client App. Upload, submit, and auto-download in a single wrapper. Best for studios with recurring 3ds Max jobs or those who want renders automatically pulled back to local storage as frames complete. See .

For the end-to-end upload-submit-download flow that applies across all DCCs, see .

Renderer-specific notes

V-Ray for 3ds Max

V-Ray is the dominant renderer on our 3ds Max worker fleet — most archviz, product visualization, and high-end still rendering pipelines on 3ds Max use V-Ray. V-Ray runs on the CPU worker tier (Dual Intel Xeon E5-2699 V4, up to 256 GB RAM per node) and the GPU tier (RTX 5090, 32 GB VRAM) for V-Ray GPU jobs.

Configuration notes:

Licensing. V-Ray on our farm runs under our Chaos partner license. As an official Chaos partner, we operate licensed V-Ray installations across the worker fleet — you do not need to transfer V-Ray licenses.
GI cache pre-calculation. For archviz still renders, pre-calculating Irradiance Map and Light Cache locally before submission is significantly faster than recalculating GI on each worker. The pre-calculated map files travel inside the project archive and the workers reuse them. The full workflow including UHD Cache patterns is documented in .
V-Ray proxies. Supported. Include .vrmesh files in the project archive. The standard project folder layout puts them in proxies/. The farm resolves proxy paths relative to the scene file at render time.
VRayScene files. Supported as external scene references. Include the .vrscene files in the archive at their expected relative paths.
Render Elements. All V-Ray render elements (VRayLightSelect, VRayDiffuseFilter, VRayReflection, VRayRefraction, VRayZDepth, VRayWireColor, etc.) write correctly on the farm. For multichannel EXR output combining multiple render elements into a single file per frame, see the EXR output section below.
V-Ray Frame Buffer (VFB). Post-render corrections saved as .vccglb files (LUT, white balance, exposure, curves) are applied on the worker when VFB output is enabled. Include the .vccglb file in the archive.

V-Ray version note: the configuration patterns above are current through V-Ray 6.x for 3ds Max. The pattern is stable across V-Ray 5.x and V-Ray 6.x. If you are running V-Ray Next (V-Ray 4.x), the parameter names for the animation prepass mode are slightly different but the workflow is the same — verify against the Chaos documentation for your specific version before relying on the prepass workflow.

Corona Renderer for 3ds Max

Corona Renderer is a common choice for studios that prefer Corona's specific image character and faster setup time over V-Ray's deeper toolset, particularly for archviz and product visualization. Corona on our farm runs on the CPU worker tier.

Configuration notes:

Licensing. Corona is a Chaos product and runs on the farm under our Chaos partner license.
Sampling. Corona uses progressive image sampling. The worker renders to the Time Limit or Pass Limit you set in Render Setup → Performance. Calibrate these values locally on a representative frame before submission so you know what render budget your settings actually consume.
Corona proxies. Supported. Include the proxy .cgeo files in the project archive.
Render elements. Corona's render elements work on the farm. The default multichannel EXR output is supported.
CXR files. Corona's native .cxr format — which embeds render elements and post-processing settings in a single container — is supported. The worker saves CXR alongside any other output formats you specify in Render Setup.

Arnold for 3ds Max

Arnold for 3ds Max is supported on the CPU worker tier. It is less common in archviz pipelines than V-Ray and Corona but is a standard choice for studios that have a unified Arnold pipeline across Maya, Cinema 4D, and 3ds Max.

Configuration notes:

Licensing. Arnold for 3ds Max runs under Autodesk render-node licensing on the farm.
AOVs. Configure Arnold AOVs in the Arnold Renderer panel before submission. The worker writes AOVs as separate files or as a multichannel EXR depending on your output settings.
Sampling. Arnold uses ray-based adaptive sampling. As with Corona, calibrate sample counts locally on a representative frame before submitting a long sequence.
OSL shaders. Standard Arnold shaders work without configuration. Custom OSL shaders that reference external workstation paths will fail at scene load on the worker; bundle any custom shaders inside the project archive.

EXR output formats

EXR is the standard high-quality output for VFX compositing, archviz post-processing, and any pipeline that needs high bit depth or render-element separation. 3ds Max supports several EXR output paths.

Multi-element EXR via Render Elements

The most common pattern for production work: configure all render elements you need in Render Setup → Render Elements, then write each pass as a separate EXR file or as a single multichannel EXR per frame.

To produce a single multichannel EXR per frame:

Configure all render elements in Render Setup → Render Elements (beauty, Z-depth, reflection, etc.).
In the output settings, set the output filename extension to .exr.
In the EXR options dialog (accessed via the small button next to the output path), enable "Save All Layers in Single Format File" to package every render element into one multichannel EXR per frame.
Optionally set bit depth (16-bit half-float is the standard production default; 32-bit full-float is available if your compositing pipeline needs it).

This pattern works in V-Ray, Corona, and Arnold for 3ds Max. The worker writes the multichannel EXR per frame and stores it in the output folder you specified. Compositing applications (Nuke, After Effects with Cryptomatte, Fusion) read the multichannel EXR and expose each render element as a separate stream.

EXR via V-Ray Frame Buffer (VFB)

V-Ray Frame Buffer offers an alternative EXR pipeline that bakes post-render corrections (LUT, white balance, curves, exposure) into the EXR at render time. This is useful when you want a finished-look EXR straight off the farm without a separate post pass — common for archviz stills where the final delivery is a graded EXR.

The workflow:

Enable V-Ray Frame Buffer in V-Ray settings.
Configure your post-render corrections (white balance, exposure, curves, LUT) in VFB on your workstation.
Save the corrections to a .vccglb file: VFB toolbar → "..." menu → Save Corrections.
In Render Setup → Output, set the output to .exr and enable VFB as the output channel.
Include the .vccglb file in your project archive at the path V-Ray expects (typically alongside the scene file or in sceneassets/).

The worker applies the saved VFB corrections during render and writes the corrected EXR to disk. The corrections are baked into the file — they cannot be unbaked downstream. If you want both a graded version and a raw version, render twice (once with VFB corrections, once with corrections disabled) or use the multi-element EXR approach above and grade in compositing.

V-Ray animation workflow (prepass + final)

For V-Ray animation, the recommended workflow uses a separate "prepass" pass to calculate the Irradiance Map across the entire animation sequence, then a "final" rendering pass that reuses the saved map. This pattern produces flicker-free GI animation and is significantly faster overall than recalculating GI per frame.

The workflow:

Configure prepass settings locally. In V-Ray → Global Illumination, set Irradiance Map mode to "Animation (prepass)" with appropriate sample counts (lower than your final render — the prepass is calculating the cached lighting, not the beauty pass).
Render the prepass across the full frame range. Each frame writes a partial Irradiance Map. The farm distributes the prepass across workers, each producing its own partial map file. Make sure the output path is consistent so all partial maps end up in the same folder.
Compile the prepass maps. Use V-Ray's "Multipass Final" tool or the standalone Irradiance Map merge utility to combine the per-frame partial maps into a single map file covering the full animation range.
Configure the final pass. Switch Irradiance Map mode to "Animation (rendering)" and point V-Ray to the compiled map file. Add the same Light Cache settings you used in prepass.
Submit the final pass to the farm. Workers render the final image using the precomputed Irradiance Map. This pass is significantly faster than recalculating GI per frame and produces flicker-free GI across the animation.

For the underlying caching theory (why pre-calculation matters, when UHD Cache replaces Irradiance Map, when to reuse maps across similar shots), see . The animation prepass pattern is documented current through V-Ray 6.x; V-Ray Next (4.x) workflows used slightly different parameter names but the same workflow shape.

XRef scenes

3ds Max XRef scenes — external .max files referenced into a master scene — are supported on the farm, but they require an extra packaging step. The 3ds Max Archive function does not always traverse XRefs cleanly, particularly for nested XRefs or XRefs that point to a separate project folder.

The safer pattern is to merge XRefs into the master scene before archiving:

Open the master scene in 3ds Max.
File → XRef Objects. For each XRef row, right-click → Merge XRef. This converts the XRef into native scene geometry and breaks the live reference link.
Save the master scene with a new name (e.g., master_merged.max) so your original XRef workflow is preserved on your workstation.
Archive the merged scene normally via File → Archive.

For studios that maintain XRef workflows for live editing across multiple artists and want to preserve XRefs across the upload-render-download cycle, the alternative is to include all referenced .max files in the archive at the same relative paths the master scene expects. The worker resolves XRef paths at submission time and will find the referenced scenes if the directory structure matches. This approach is fragile across project relocations — the merge-before-archive pattern is more reliable for one-off farm renders.

V-Ray Distributed Rendering (DR) on the farm

V-Ray's Distributed Rendering feature is designed for splitting a single still frame across multiple workstations connected on a LAN. On our farm, DR is handled at the queue level: when you submit a single-frame V-Ray job, the farm distributes buckets of the frame across multiple workers automatically. You do not need to configure V-Ray DR settings or specify worker hosts.

If your scene has V-Ray DR pre-configured with specific render server IPs from your workstation network, the worker ignores those settings — they reference machines that are not part of the farm topology. The render proceeds using farm-level distribution instead.

For animation, frames are distributed across workers one frame per worker (or batched depending on queue settings) — no per-frame DR configuration is needed.

Submission plugin (overview)

The 3ds Max submission plugin is the recommended submit channel for studios with recurring work. Install steps and license activation are covered in detail in ; the highlights:

Plugin installer is downloaded from your account dashboard after sign-in. Pre-built installers exist for 3ds Max 2024, 2025, and 2026.
Default install location: the 3ds Max version's user plugins/ folder. The installer adds a menu item to the Max toolbar.
License activation uses your account credentials; no separate license key is required.
After install, submit from 3ds Max via the Super Renders Farm menu. The plugin packages the scene, runs Asset Tracking, uploads to the farm, and queues the job in one workflow.

Common install issues (missing plugin in toolbar after install, manual install fallback for restricted Windows environments) are covered in the plugin install doc.

Common issues — quick reference

This is a short list of 3ds Max-specific failures and the typical fix. For general cross-DCC troubleshooting (job stuck in queue, upload failed, output not appearing) see . For render-quality issues (image looks wrong vs local) see .

"Asset missing" at scene load on worker. Open Asset Tracking on your workstation, locate the missing bitmap or proxy, re-link it, and re-archive. Most "missing asset" failures trace back to a path that was changed after the last Archive pass — typically because the artist moved a texture folder or renamed a project subdirectory.
Worker renders the wrong camera. Verify Render Setup → Common → View to Render explicitly names the camera you want. A locked viewport camera at save time can cause the worker to render from a different camera than your last viewport view.
Output image is partial / clipped. Check Render Setup → Common for "Use Region" or "Use Border" — if either is enabled, the worker renders only that region with the rest of the frame black. Disable both for full-frame output.
Render is brighter or darker than the local preview. Most commonly a VFB correction file (.vccglb) that is applied locally but not bundled in the archive, or a different gamma / color management setting between workstation and farm. Verify Customize → Preferences → Gamma and LUT matches between workstation and saved scene, and bundle any .vccglb corrections in the archive.
V-Ray Irradiance Map fails to load on worker. Verify the .vrmap file path in V-Ray settings is relative to the project folder, not an absolute workstation path like D:\maps\scene.vrmap. Re-pack the archive with the map file in a relative location such as sceneassets/maps/scene.vrmap and update the V-Ray Irradiance Map path to match.
Only one node renders / animation runs single-threaded. Check that Frame Range in Render Setup is not set to "Single" when you intended an animation, and that the output filename includes a frame number token (#### or <frame>) so each frame writes to a unique file. A static output filename causes every frame to overwrite the previous.
VRayPattern or third-party plugin missing on worker. Forest Pack, RailClone, and similar common archviz plugins are pre-installed on the 3ds Max worker fleet. Less common plugins may not be — contact support before submission to confirm. As a workaround, bake the scattered geometry to a .vrmesh proxy before archiving; the proxy is self-contained and does not require the source plugin on the worker.
"License not found" error mid-render. Rare on our farm because licensing is server-side. The most common cause is a worker mid-update during your job's execution; re-submitting the job after a few minutes usually resolves it. If the error persists, contact support — there may be a specific plugin license issue worth investigation.
Custom shader or OSL fails at scene load. Standard V-Ray, Corona, and Arnold shaders work without configuration. Custom OSL or third-party shader plugins not pre-installed on the worker fail at scene load. Bundle custom shaders inside the project archive at the path the scene expects, or bake the material to texture before submission.

Cross-references

— account setup, first job overview
— upload, submit, download workflow
— how 3ds Max job costs are calculated
— SFTP guide, archive formats, large transfer guidance
— installing the 3ds Max submission plugin
— auto-download wrapper for recurring jobs
— Irradiance Map, Light Cache, UHD Cache, GI pre-calculation patterns
— cross-DCC job failure patterns
— cross-DCC quality and color issues
— short list of frequent cross-DCC error messages
— frequently asked questions across all DCCs
— landing page with pricing and hardware
— 2027 release coverage
— scattering plugin workflow
— performance analysis for heavy scatter scenes

FAQ

Q: Which 3ds Max versions does the farm support? A: 3ds Max 2024, 2025, and 2026 are pre-installed on every worker. 2023 is available on request for legacy projects — open a support ticket before submission. The farm matches your .max file's version automatically.

Q: Do I need to transfer my 3ds Max license to render on the farm? A: No. We run licensed 3ds Max installations across our worker fleet under Autodesk render-node licensing. Your local 3ds Max license stays with you. The same applies to V-Ray, Corona, and Arnold — all licensing is server-side under our partner licenses.

Q: My scene uses Forest Pack and RailClone for scattering. Will it render on the farm? A: Yes. Forest Pack and RailClone are pre-installed on the 3ds Max worker fleet. For very dense scatters (millions of instances) the covers optimization patterns; for per-frame render time analysis with heavy scatters, see the .

Q: How do I render a V-Ray animation with flicker-free GI? A: Use the "Animation (prepass)" + "Animation (rendering)" two-pass workflow described in the V-Ray animation section above. The prepass calculates the Irradiance Map across the full animation range; the final pass reuses the saved map. This is significantly faster than recalculating GI per frame and eliminates frame-to-frame GI flicker.

Q: My V-Ray scene uses VRayProxy. Are the proxy files automatically included when I archive? A: 3ds Max's Archive function includes them if your proxies/ folder is inside the project folder. Verify by opening the archived scene in a fresh 3ds Max session and checking the Asset Tracking panel for any missing proxies. If any show as missing, manually copy the .vrmesh files into the archive's proxies/ folder before re-packing as .tar.gz.

Q: Can I render Corona and V-Ray scenes in the same submission? A: Each job uses one renderer at a time, determined by Render Setup → Assign Renderer in the saved scene file. If your project mixes Corona and V-Ray scenes, submit them as separate jobs. The farm processes each job independently and there is no cross-renderer dependency.

Q: I want a graded EXR straight off the farm — how do I save my V-Ray Frame Buffer corrections? A: Save the VFB corrections as a .vccglb file (VFB → "..." menu → Save Corrections), include the .vccglb in your project archive, and enable VFB as the output format in Render Setup → Output. The worker applies the corrections during render and writes the corrected EXR to disk. See the EXR via VFB section above.

Q: How does V-Ray Distributed Rendering work with the farm? A: V-Ray DR is designed for LAN-based bucket distribution. On the farm, bucket distribution for single frames is handled at the queue level — you do not configure V-Ray DR settings. Submit the job normally; the farm distributes buckets automatically. Pre-configured DR settings from your workstation network are ignored by the worker.

Q: My render is "brighter or darker than my local render." What changed? A: Most commonly a Customize → Preferences → Gamma and LUT mismatch between workstation and saved scene, or a VFB correction file (.vccglb) applied locally but not bundled in the archive. Verify gamma settings match the saved scene and include any VFB corrections in the project archive.

Q: Are .zip archives accepted for upload? A: No. We accept .tar, .tar.gz, and .7z. The 3ds Max Archive function produces .zip by default — re-pack to .tar.gz using 7-Zip on Windows or tar -czf on macOS/Linux before upload. For files above 300 GB, SFTP or the Client App is recommended over web upload.

---