Submission plugin: install and troubleshoot per DCC

The SuperRenders submission plugin is a small extension inside your 3D software that adds a "SuperRenders" menu or shelf button, so you can submit a render job to our farm without leaving your DCC. The plugin packages your scene, runs a pre-flight asset and version check, and hands the job to the farm queue in a single step.

Most users do not need to install the plugin by hand. When you install the , the matching plugin is auto-detected and installed into each supported DCC on your workstation. The pages below cover the cases where the auto-install path does not work — fresh DCC version, custom install location, restricted user account — or where you prefer a manual install for reproducibility.

This page covers what the submission plugin does, supported DCCs and engines, manual install steps per DCC, the update procedure, the missing-shelf / missing-menu fix, how to remove the plugin cleanly, and a v1 feature matrix.

For job-submission workflow once the plugin is installed, see and the relevant for renderer-specific notes. For Client App installation, see .

Plugin overview

The submission plugin is the DCC-side companion to the Client App. The Client App handles upload, job tracking, and download on the desktop; the plugin handles "scene → job" inside the DCC.

What the plugin does inside your DCC:

Adds a SuperRenders menu or shelf button so you can launch the submission dialog without leaving the DCC.
Reads the active scene — frame range, output path, render settings, referenced assets — and pre-fills the job form.
Runs a pre-submit asset check to flag missing textures, missing references, and broken file paths before upload starts.
Versions the scene file alongside its assets so the farm renders exactly the scene state you submitted, not a later edit.
Hands the packaged job to the Client App (or directly to the farm queue if the Client App background service is running) for upload.

This page documents plugin v1, the current production plugin shipped with the Client App and the only customer-facing plugin generation today. A future generation may ship alongside the Spaces migration tool (see ); when it does, a separate page will cover the new plugin. The DCCs and engines plugin v1 supports today are listed in the features matrix below.

Before you install

A few things to confirm before running any of the manual install procedures below:

Use the same user account that runs the DCC. The plugin installs into the user's DCC scripts folder, not into the DCC's program-files directory. If you install while logged in as a different user (for example, an administrator account used only for software installs), the plugin will not appear when your normal user opens the DCC. Sign in as the user that actually opens the DCC and rerun the installer.
Run the DCC at least once before installing. Most DCCs create their user-specific scripts folder on first launch. Installing before that folder exists silently fails on some Maya and 3ds Max versions.
Close the DCC during install. The plugin's startup script is read when the DCC loads. If the DCC is running during install, restart it after install so the script is picked up.
Have a SuperRenders account ready. The plugin prompts for sign-in on first launch.

If your studio runs a locked-down workstation image where users cannot write to their own Documents folder, contact support — the plugin requires write access to the standard DCC scripts directory.

Installation per DCC

The first thing to try in every DCC is the auto-install path: install the , open the Plugins panel, and click Scan to update. The Client App detects your installed DCCs and pushes the correct plugin into each one. The manual steps below are the fallback for when scan-to-update does not pick up your DCC, when you want a reproducible install on a fresh machine, or when you want to install the plugin without the Client App service running in the background.

3ds Max (auto-install + manual fallback)

3ds Max plugin v1 is delivered as a single .mzp MAXScript package. The Client App's scan-to-update flow handles install in normal cases. Manual install is a two-step process.

Download the package. Get superrenders.mzp from the SuperRenders static link your account dashboard provides (the Client App also stores a local copy in its plugin cache directory). [RICHARD: cần confirm current public download URL — Crisp source references a legacy S3 path that may be retired]
Run the script inside 3ds Max. Open 3ds Max, then Scripting → Run Script…, locate superrenders.mzp, and confirm. The script registers the plugin and adds a SuperRenders menu to the top-level menu bar.
Restart 3ds Max if the menu does not appear. Some 3ds Max versions only re-read top-level menu definitions on launch.

3ds Max version coverage. Plugin v1's 3ds Max wrapper has been used in production with 3ds Max 2018 through 2024. 3ds Max 2025 and 2026 have not been independently verified by SRF on a fresh install path. [RICHARD: cần confirm plugin v1 install path on 3ds Max 2025 / 2026 — Crisp source dated 2024-01-24, predates these versions.]

A note on PySide / Qt versions in 3ds Max 2026: Autodesk changed Qt versions across recent 3ds Max releases, which has historically affected plugin GUIs. If the SuperRenders menu appears but the submission dialog opens blank or throws a Python error, please file a ticket — we will confirm whether a plugin-side patch is needed.

Maya (auto-install + manual fallback)

Maya plugin v1 is delivered as a zipped script bundle (superrenders_maya_v2xx.zip). The Client App auto-installs this into the Maya scripts folder for each detected Maya version. Manual install is required when the Client App cannot detect a Maya version (typically on a freshly installed Maya release before the Client App's compatibility table is updated).

Manual install, five steps:

Download the bundle. Get superrenders_maya_v240.zip (or the most recent version your account dashboard points at) from the SuperRenders static asset path. [RICHARD: cần confirm current download URL — Crisp source references s3.us-east-1.amazonaws.com/statics.superrendersfarm.com/app/plugins/superrenders_maya_v240.zip, dated 2024-12.]
Extract to Maya's scripts folder. Unzip into Maya's per-version scripts directory: C:\Users\<YourWindowsUser>\Documents\maya\<MayaVersion>\scripts\superrenders For example, on Maya 2023 with the Windows user admin, the path is C:\Users\admin\Documents\maya\2023\scripts\superrenders. On macOS the equivalent path is ~/Library/Preferences/Autodesk/maya/<MayaVersion>/scripts/superrenders.
Edit userSetup.mel. Locate or create userSetup.mel in the parent scripts folder (one level up from superrenders): C:\Users\<YourWindowsUser>\Documents\maya\<MayaVersion>\scripts\userSetup.mel
Append the SuperRenders init block to userSetup.mel: /***superrenders_begin***/ python("import sys"); python("sys.path.append(u'__srfscriptPath__')"); python("import superrenders_runner"); python("superrenders_runner.init()"); /***superrenders_end***/ Replace __srfscriptPath__ with the full forward-slash path to your superrenders folder, for example: C:/Users/admin/Documents/maya/2023/scripts/superrenders Forward slashes are required. Backslashes break the Python sys.path.append call.
Restart Maya. The SuperRenders shelf and menu should appear on next launch.

Maya version coverage. Plugin v1 has been used in production on Maya 2017 through 2023 (per the Crisp-documented feature matrix). Maya 2024, 2025, and 2026 are commonly used today but have not been independently verified by SRF for plugin v1 install. [RICHARD: cần confirm plugin v1 install path on Maya 2024 / 2025 / 2026 — Crisp install doc dated 2024-12, feature matrix dated 2023.]

Cinema 4D (Client App auto-install only)

The Cinema 4D plugin is installed by the Client App's scan-to-update flow. There is no separate manual .mzp-style installer published for Cinema 4D plugin v1 today.

To install:

Install the .
Open the Plugins panel inside the Client App.
Click Scan to update. The Client App detects each installed Cinema 4D version on the workstation and installs the matching plugin into the C4D plugins directory.
Restart Cinema 4D. The SuperRenders submission entry appears in the C4D Extensions menu.

If scan-to-update reports your Cinema 4D version as "not supported," file a ticket with your C4D version and OS. We add Cinema 4D versions to plugin v1 on a rolling cadence as Maxon ships major releases.

Cinema 4D version coverage. The Crisp-documented feature matrix lists Cinema 4D R15 through R25 with engines Advanced Render, Physical, V-Ray, and Corona. [RICHARD: cần confirm plugin v1 support on Cinema 4D 2023, 2024, 2025 (the post-R26 rebrand) — Crisp source matrix has not been refreshed since the C4D version naming change.] Cinema 4D's GPU engines Redshift and Octane are typically supported via the same plugin, but list confirmation lags Maxon's release cadence.

Blender

Blender does not currently have a SuperRenders submission plugin in plugin v1. Submission from Blender goes through the or through the .

Blender users can still preview and configure jobs inside Blender (frame range, output format, engine choice — Cycles or Eevee) and then submit via the Client App without losing scene context. The .blend file's metadata is parsed on upload; the Client App pre-fills most submission fields automatically.

A native Blender add-on is not on the published roadmap today. If Blender plugin support is important to your workflow, please file a feature request — we track demand and will publish a roadmap update when the timing makes sense.

Other DCCs

Plugin v1 covers 3ds Max, Maya, and Cinema 4D natively. For Houdini, After Effects, and other DCCs supported by the farm itself, the submission flow runs through:

the web dashboard () — works for every DCC the farm renders,
the Client App's drag-and-drop upload () — works for every DCC, with the benefits of resumable upload and auto-download,
SFTP () — recommended for very large projects.

For Houdini-specific submission tips see ; for After Effects see . Neither of those DCCs currently has a SuperRenders-branded submission plugin; the per-DCC setup docs cover how to package and submit a scene without one.

Update procedure

The Client App keeps plugin v1 up to date automatically. When SuperRenders ships an update — a new DCC version, a fix to the asset re-linker — the Client App fetches the new plugin and offers to install it on next launch.

To run an update manually:

Close your 3D software. DCCs lock plugin files while running and can silently block the update.
Open the Client App's Plugins panel and click Scan to update. The Client App compares installed plugin versions to the latest and installs newer ones where available.
Wait for each row to show "Up to date."
Restart the DCC. The new plugin version is read on next launch.

If "Scan to update" fails for a specific DCC, the usual causes are: the DCC is still running and holding a file lock; the user account running the Client App lacks write permission to the DCC's scripts folder (run the Client App as the same Windows user that runs the DCC); or a previous failed install left a partial plugin folder (remove it per Removing the plugin and re-scan).

When the Client App is not available, rerun the manual install steps in the per-DCC sections above with the newer plugin package. The plugin is designed to be overwritten in place.

If the plugin installs without errors but the SuperRenders menu or shelf icon never appears, the underlying cause is almost always one of two things: the plugin landed in the wrong directory, or a third-party tool corrupted the DCC's startup preferences.

Cause 1 — Plugin installed in the wrong scripts directory.

The plugin must live in the user-specific scripts folder for the running DCC version. If it lands somewhere else — a different Maya version's folder, or a different Windows user's profile — the DCC will not find it on startup.

Confirm in Maya by opening the Script Editor and running:

text

import superrenders_runner
superrenders_runner.init()

If the SuperRenders submission window opens, the plugin is correctly installed and the shelf issue is a UI problem (Cause 2). If you get ImportError: No module named superrenders_runner, the plugin is not on Maya's Python path. Re-run the manual install steps in Maya install, paying attention to:

The Maya version in the path matches the Maya you launch (e.g., maya/2023/scripts/superrenders for Maya 2023).
The Windows user in the path matches the user who launches Maya.
The path inside userSetup.mel uses forward slashes, not backslashes.

The same logic applies to 3ds Max and Cinema 4D — install path must match the running user account and DCC version.

Cause 2 — Third-party tool corrupted the DCC's shelf preferences.

If the Script Editor confirms superrenders_runner imports but the shelf icon is still missing, the DCC's saved shelf preferences are usually corrupt — typically because another plugin rewrote them.

In Maya:

Quit Maya.
Locate userPrefs.mel: - Windows: C:\Users\<YourWindowsUser>\Documents\maya\<MayaVersion>\prefs\userPrefs.mel - macOS: ~/Library/Preferences/Autodesk/maya/<MayaVersion>/prefs/userPrefs.mel
Rename userPrefs.mel to userPrefs.mel.backup (don't delete — preserve custom shelf layouts in case you want to merge them back).
Restart Maya. Maya regenerates a fresh userPrefs.mel and the SuperRenders shelf should appear.

You will lose custom shelf customizations and recent-file lists; merge them back from the backup if they matter.

In 3ds Max, the equivalent fix is Customize → Revert to Startup UI Layout, then re-run the superrenders.mzp install.

If neither cause matches, file a support ticket with: DCC name and version, OS and user account, the full error text from the script editor / MAXScript Listener, and the contents of userSetup.mel (Maya) or the MAXScript install log (3ds Max).

Removing the plugin

To uninstall plugin v1 — clean reinstall, shared workstation cleanup, or pre-migration prep — the procedure is per-DCC.

Maya:

Quit Maya.
Delete the superrenders folder under Maya's scripts directory: - Windows: C:\Users\<YourWindowsUser>\Documents\maya\<MayaVersion>\scripts\superrenders - macOS: ~/Library/Preferences/Autodesk/maya/<MayaVersion>/scripts/superrenders
Open userSetup.mel and remove the block between /***superrenders_begin***/ and /***superrenders_end***/. Save.
Restart Maya. Repeat for each Maya version on the workstation.

3ds Max:

Close 3ds Max.
Reset the UI to defaults from Customize → Revert to Startup UI Layout on next launch, or delete the SuperRenders macroscript files from C:\Users\<YourWindowsUser>\AppData\Local\Autodesk\3dsMax\<Version>\ENU\usermacros\ (files starting with SuperRenders_).
Restart 3ds Max.

Cinema 4D: close Cinema 4D, delete the SuperRenders plugin folder under the C4D plugins directory for that C4D version, and restart Cinema 4D. The Client App does not currently expose a per-DCC uninstall button.

After removal, the and the still submit jobs without the plugin.

Plugin v1 supported features matrix

The matrix below summarizes plugin v1 capabilities per DCC, drawn from the Crisp-documented feature lists. Items marked [verify] are pending currency confirmation against the most recent DCC release; see the currency note that follows.

| Capability | 3ds Max | Maya | Cinema 4D | Blender | |---|---|---|---|---| | DCC versions covered (Crisp baseline) | 2018–2024 [verify 2025/2026] | 2017–2023 [verify 2024/2025/2026] | R15–R25 [verify post-R26 naming] | (no native plugin) | | Scene packaging on submit | Yes | Yes | Yes | (use Client App upload) | | Pre-submit asset check | Yes | Yes | Yes | — | | Asset re-linker (texture tracker) | Yes | Yes | Yes (C4D texture tracker) | — | | Frame-range / single-frame / range / selected frames submission | Yes | Yes | Yes | — | | Referenced scenes / XRefs | Yes | Yes (binary .mb + ASCII .ma) | Yes (XRefs, file sequences, textures, GI maps) | — | | Render-pass / multi-pass output | Yes | Yes | Yes (main + multi-pass + render elements + AOVs + Corona buffers) | — | | Scene versioning on the farm side | Yes | Yes (full automated integration) | Yes (server-side scene versioning + checking) | — | | Tiled / high-res still rendering | — | — | Yes (C4D tiled camera) | — | | Multiple GI cache modes | — | — | Yes (Irradiance cache, QMC, Light Mapping, Radiosity, UHD Cache, HD Cache, Path Tracing, Light Cache, Brute Force) | — | | Engines supported (Crisp baseline) | V-Ray, Corona [verify Redshift via plugin] | Arnold, V-Ray, Redshift (renderer support is farm-side; plugin packages the scene regardless) | Advanced Render, Physical, V-Ray, Corona [verify Redshift, Octane] | (engine choice on Client App upload) |

The matrix tracks what the plugin v1 wrapper handles inside the DCC. The farm-side engine support — which engines actually render your job — is broader and tracked per the relevant . Plugin v1 packages the scene; the renderer (Arnold, V-Ray, Redshift, etc.) runs farm-side.

Currency note

The matrix is sourced from Crisp KB entries published 2023–2024. Newer DCC releases (3ds Max 2025 / 2026, Maya 2024 / 2025 / 2026, Cinema 4D's post-R26 naming, ongoing Redshift / Octane updates) are highly likely to work — plugin v1 has been incrementally maintained — but SRF has not published a fresh confirmation against each new release. The [verify] rows will be refreshed as part of Phase 2c maintenance once Dev confirms the per-version test matrix. If you hit a plugin issue on a newer DCC, please file a ticket; we treat that as P1.

[RICHARD: cần confirm — full plugin v1 DCC + engine compatibility table refresh from Dev: 3ds Max 2025 / 2026, Maya 2024 / 2025 / 2026, Cinema 4D 2023+ post-rebrand, Redshift / Octane per C4D and Maya. Dev refresh replaces the [verify] rows.]

When the plugin is not the right path

Some workflows are better served without the plugin even when it is installed and working:

One-off submissions where you do not want to install anything in the DCC. Use the .
Locked-down studio workstations where users do not have write access to their own scripts folder. Use the or .
Headless render-prep machines with no GUI to click through the plugin's submission dialog. Use the or SFTP.
DCCs the plugin does not cover (Blender, Houdini, After Effects). Submit via or .

The Client App, web dashboard, and submission plugin are not mutually exclusive — a single project can be uploaded via Client App and submitted via plugin, or uploaded via SFTP and submitted via web dashboard. Pick the path that fits the workstation.

Cross-references

— desktop wrapper for upload, submit, and download
— browser submission flow without the plugin
— browser-based submission details
— alternative upload path for very large projects
— comparison of upload methods
— Maya-specific submission notes
— 3ds Max-specific submission notes
— Cinema 4D-specific submission notes
— Blender submission via Client App / web
— cross-DCC troubleshooting

FAQ

Q: Do I have to install the submission plugin, or can I submit jobs without it? A: The plugin is optional. The and the both submit jobs without a DCC plugin. The plugin is a convenience for users who prefer to submit from inside their 3D software in one click.

Q: Which 3D applications have a SuperRenders submission plugin? A: Plugin v1 covers 3ds Max, Maya, and Cinema 4D. Blender, Houdini, and After Effects do not have a native plugin today; jobs from those DCCs are submitted via the Client App or the web dashboard.

Q: Why doesn't the SuperRenders menu appear after installing? A: Most common causes: the plugin landed in the wrong scripts folder (often because you installed as a different user than the one who runs the DCC), or the DCC's saved shelf preferences are corrupt. See Missing plugin menu or shelf for the full diagnostic flow.

Q: How do I update the plugin? A: Open the Client App's Plugins panel, click "Scan to update," and restart your DCC. Manual updates work too — rerun the per-DCC install steps with the newer plugin package; the new version overwrites the old in place.

Q: Does the plugin work on Maya 2024+, 3ds Max 2025+, or the latest Cinema 4D? A: Plugin v1's documented matrix covers Maya 2017–2023, 3ds Max 2018–2024, and Cinema 4D R15–R25. Newer DCC releases are highly likely to work because plugin v1 has been incrementally maintained, but SRF has not published a fresh per-version confirmation. The matrix flags those rows as [verify] pending Dev refresh. File a ticket if you hit an issue on a newer DCC — P1.

Q: Can I install the plugin without installing the Client App? A: Yes for 3ds Max and Maya — the manual install steps on this page use the standalone plugin package. Cinema 4D's manual-without-Client-App path is not currently published; we recommend installing the Client App for the C4D plugin install.

Q: The plugin opens but submission fails. Where do I look? A: Submission-time errors usually mean the scene packaged correctly but the farm rejected something — a missing asset, a renderer / engine version the farm does not support, or an account billing issue. Check the error text against . If the message isn't listed, file a ticket with the error text and the job ID.

---

Submission plugin: install, update, and troubleshoot per DCC

<!-- Phase 2a §4 D2 coverage check:

Crisp /manually-install-autodesk-maya-submission-plugin-1xbgqks/ (312w C, Dec 2024) → §Maya install (canonical, full MEL block reproduced)
Crisp /manually-install-3ds-max-submission-plugin-z21cll/ (155w D, Jan 2024) → §3ds Max install (canonical)
Crisp /how-to-submit-render-job-from-submission-plugin-utxu9c/ (335w C, Oct 2023) → folded into §Plugin overview + §Update procedure (workflow narrative now in /docs/quick-start-guide; this doc keeps install-focused scope)
Crisp /update-3d-software-submission-plug-in-sh0ak3/ (92w F, Oct 2023) → §Update procedure (canonical)
Crisp /missing-plugin-in-shelf-removing-the-plugin-1bfz5jv/ (350w C) → §Missing plugin menu or shelf + §Removing the plugin (Maya canonical fold) — per Phase 2a §4 D2 + cross-coverage with setting-up-maya per CSV
Crisp /maya-plugin-supported-features-15lyzbe/ (60w F) → §Plugin v1 supported features matrix (Maya row baseline)
Crisp /cinema-4d-plugin-supported-features-1sgapr/ (182w D) → §Plugin v1 supported features matrix (Cinema 4D row baseline)
Zendesk disabled "Submit render job to SuperRenders (by submission plugin)" → folded into §Plugin overview workflow (Crisp utxu9c is canonical; Zendesk disabled fragments add no new install-side content per Phase 2a §4 D2)
Zendesk disabled "How to submit render job from submission plugin" → same as above
Zendesk disabled "Update 3D software submission plug-in" (871c) → §Update procedure (Crisp sh0ak3 is canonical, Zendesk adds no new content)

-->

<!-- Currency verification flag (per task brief — same pattern as tools-client-app):

Plugin v1 install paths sourced from 2023-2024 Crisp content
4 [verify] markers in features matrix + 3 [RICHARD: cần confirm] flags for: (1) current public plugin download URLs (2) plugin v1 install on 3ds Max 2025/2026 (3) plugin v1 install on Maya 2024/2025/2026 + C4D post-R26
These are consolidated for Richard / Dev refresh pass before Phase 2c translation cascade

-->

<!-- Brand voice / glossary check:

"submission plugin" is canonical term (matches Crisp + Zendesk + glossary §Plugins reference)
Thinkbox Deadline NOT mentioned anywhere (per srf-context line 37 INTERNAL — do not mention)
Prohibited phrases (best/fastest/cheapest/etc) — zero matches
No "Try X today" / "Sign up now" / "Get started" / "Don't miss" CTAs
"Plugin v1" used as customer-facing version label per srf-context Spaces migration note + Phase 2a §4 D1 D1=A ratify rationale

-->

<!-- Cross-link prose mentions for Phase 2e atomic deploy resolution:

/docs/tools-client-app (multiple, primary sibling)
/docs/quick-start-guide (web dashboard alternative path)
/docs/setting-up-maya, /docs/setting-up-3dsmax, /docs/setting-up-c4d, /docs/setting-up-blender, /docs/setting-up-houdini, /docs/setting-up-after-effects
/docs/tools-sftp-transfer
/docs/tools-web-submit
/docs/upload-and-download
/docs/common-errors

-->

<!-- Phase 2f redirect note:

301 from /docs/installation-guide → /docs/tools/plugin-installation per task brief Q1 + Phase 2a §3 disposition row 3
Slug on this draft remains FLAT (tools-plugin-installation) per Phase 2e nested URL handling layer

-->

Submission plugin: install, update, and troubleshoot per DCC