Common errors and how to fix them

This page collects the render errors we see most often on our farm and the fixes that work for each one. Of the jobs that fail on our farm, the patterns documented below cover roughly 80% of cases. Asset path issues alone account for over half of the failed jobs we triage, which is why that section comes first.

We've grouped errors by category so you can jump to the right place. The error message strings shown are representative — your DCC and engine may format them slightly differently, but the underlying cause and the fix are the same.

Quick decision tree

Use this to find the right section quickly:

• Your render did not start at all → jump to §Submission and queue errors.
• Your render started but produced wrong output (black frames, missing objects, bad colours) → jump to §Output and render errors. For quality artifacts (noise, fireflies, banding) the dedicated deep-dive is .
• Your render failed mid-job → jump to §Asset and path errors first; if assets check out, then §Plugin and engine errors.
• You got billed unexpectedly or your job won't accept credits → jump to §Account and billing errors.

If none of the patterns below match what you're seeing, the covers a few additional cases, and live chat on knowledge.superrendersfarm.com is the right channel for anything not covered.

Asset and path errors

These are the most common reasons a render job fails on our farm. The vast majority of "my job failed" tickets we see come down to one of the four patterns below — usually because an asset wasn't packaged into the upload, or because a path on your local workstation doesn't exist on a worker node.

Missing texture or "Unable to find file"

Error: Unable to find file <path>
Warning: Missing texture map: <texture-name>

What it means: the render engine tried to load a texture, IES profile, IBL, or other linked asset, and the file wasn't present on the worker node when the frame started rendering.

Common cause: the asset wasn't included in the project upload. This happens most often when textures live outside the project folder (for example, on a personal texture library at D:/Textures/...) and the DCC stored an absolute path rather than a relative one.

How to fix:

• In your DCC, run the project-packaging utility before submitting: 3ds Max "Archive", Maya "File → Archive Scene", Cinema 4D "Save Project With Assets", Blender "File → External Data → Pack Resources", Houdini "File → Package".
• Confirm all texture paths are relative to the project root (no D:/, C:/Users/..., or UNC paths).
• Re-upload the packaged project and resubmit.
• If you submit through the SuperRenders Client App, enable the "Collect missing assets" check in the pre-submission dialog — it surfaces unresolved paths before the job hits the queue.

Still stuck? See for the full asset-packaging walkthrough, or for DCC-specific packaging steps.

Asset path uses an absolute Windows drive letter

Warning: Path "D:/Project/Textures/wood.exr" not found on render node

What it means: your scene file references a file by an absolute drive-letter path that exists on your workstation but doesn't exist on a worker node. Workers run a standardised file layout — D:/ and E:/ on your machine are not the same D:/ and E:/ on the worker.

Common cause: the asset was added to the scene before the project was set up, or someone moved files after-the-fact and the DCC didn't update the references.

How to fix:

• Use the path-relink utility in your DCC: 3ds Max "Asset Tracking" (Shift+T), Maya "File Path Editor", Cinema 4D "Project Asset Inspector", Blender "File → External Data → Find Missing Files", Houdini File Dependency view.
• Re-point absolute paths to the project root, then save the scene.
• Re-package the project (see previous error) and re-upload.

Still stuck? covers the path-relinking workflow per DCC.

Missing scene reference (XRef, linked scene, referenced project)

Error: Cannot resolve XRef <path>
Error: Reference file not found: <scene-name>

What it means: your scene contains a reference to another scene file (XRef in 3ds Max, reference in Maya, XRef in Cinema 4D, linked library in Blender, file SOP in Houdini) and the referenced file wasn't included in the upload.

Common cause: team-shared scene libraries are referenced by network path during local work but not included when the project is packaged.

How to fix:

• Identify referenced scenes through the DCC's reference manager: Maya Reference Editor, 3ds Max XRef Manager, Cinema 4D XRef tag inspector, Blender Library Overrides panel.
• Either import the references into the master scene before submission (the simpler path), or copy the reference files into the project folder and re-link.
• Re-package and re-upload.

Still stuck? Reference handling differs significantly per DCC; the relevant page has DCC-specific notes.

Missing plugin asset (Forest Pack libraries, RailClone presets, XGen descriptions, etc.)

Error: Forest Pack library file not found: <library-name>.maxlib
Error: RailClone preset file not found: <preset-name>.rclib
Error: XGen description files missing

What it means: a scattering plugin or grooming plugin needs library files (geometry libraries, presets, or description files) that live outside the main scene file. These are easy to forget when packaging.

Common cause: plugin library files are stored in a global plugin install directory on your workstation and aren't auto-collected by the DCC's "save with assets" function.

How to fix:

• Check the plugin's asset-collection workflow: Forest Pack has "Library Manager → Pack Library", RailClone has "Style Library Pack", XGen requires manual collection of the xgen/ folder under the project root.
• For Forest Pack and RailClone specifically, our farm has the plugin runtime installed but does not stock customer library files — your custom libraries must travel with the project.
• Verify the packaged project includes the plugin's asset folder before uploading.

Still stuck? We've published deeper guides on plugin handling: and .

Plugin and engine errors

These errors appear when the worker node can't run your render the way your scene expects. Often the cause is a plugin version mismatch or a render engine that doesn't match the fleet you submitted to.

Plugin version mismatch between submission and worker

Error: Plugin <name> version mismatch — scene saved with v<X.Y>, worker has v<A.B>
Warning: Loading scene saved with newer plugin version may produce different results

What it means: the scene was saved with a plugin version newer (or significantly older) than what's installed on the worker, and the plugin refused to load the scene cleanly.

Common cause: a recent plugin update on your workstation that hasn't been mirrored on the farm, or vice versa — the farm received a major version update that broke backward compatibility with older scene files.

How to fix:

• Check the plugin's actual version in your DCC (3ds Max Plugin Manager, Maya Plugin Manager, Cinema 4D Extensions panel) and note it.
• Check our supported plugin matrix at for the relevant DCC — most pages list the major plugin versions installed on the worker fleet.
• If your version is newer than ours, either downgrade locally and re-save the scene, or wait for our farm-side update (we typically follow vendor major releases within 2-4 weeks).
• If your version is older, the worker should still load the scene; if it doesn't, contact support with the exact version numbers.

Still stuck? Live chat is the right channel for plugin-version questions — we keep a current plugin matrix internally that's faster to query than waiting on a doc update.

Render engine not installed for the selected fleet

Error: Render engine "Octane" requires GPU worker; submitted job is CPU-only
Error: V-Ray GPU rendering enabled but worker is CPU

What it means: your scene is configured for a GPU render engine (Octane, Redshift, V-Ray GPU) but the job was submitted to a CPU fleet, or the reverse.

Common cause: the fleet was selected manually at submission time and didn't match what the scene needs, or the scene's render engine was changed after submission.

How to fix:

• Open the render settings in your DCC and confirm which engine and which device (CPU vs GPU) the scene is set to render with.
• At submission, choose the matching fleet: V-Ray, Corona, and Arnold CPU jobs go to the CPU fleet; Redshift, Octane, and V-Ray GPU jobs go to the GPU fleet.
• For ambiguous cases (V-Ray, which has both CPU and GPU modes), check the "Production engine" dropdown in the V-Ray render settings before submitting.

Still stuck? explains the cost difference between fleets, and the relevant page covers engine-specific submission settings.

Plugin licence error on worker

Error: Plugin <name> failed to acquire licence
Error: License server unreachable for <plugin>

What it means: a plugin in your scene requires a per-machine licence at render time, and the worker couldn't acquire one.

Common cause: the plugin is one we don't carry a render-time licence for (some commercial plugins require a separate render-node licence per worker, which adds cost and complexity our standard fleet doesn't cover by default).

How to fix:

• Check our supported plugin list at — if the plugin isn't listed, it's not on the standard worker image.
• If the plugin is critical to your project, contact us before submission. Some plugins can be added to the worker image on request; others can't be supported at all due to vendor licensing terms.
• For common cases (Forest Pack, RailClone, V-Ray, Corona, Redshift, Octane, Anima), licensing is handled on our side through our partnerships with Chaos, Maxon, AXYZ design, and others — you should not see this error for those engines or plugins.

Still stuck? Plugin licensing is the area where farm-by-farm coverage varies the most; live chat with your specific plugin and version in hand resolves these questions quickly.

Unsupported render engine version

Error: Scene saved with V-Ray <X.Y>, worker has V-Ray <A.B>
Warning: Renderer version skew may cause inconsistent results

What it means: the render engine version on the worker is far enough from what your scene was saved with that we can't guarantee identical output.

Common cause: you upgraded V-Ray, Redshift, Octane, or another engine locally and the farm hasn't received the corresponding update yet, or you're rendering an older scene saved with a deprecated engine version.

How to fix:

• Check the engine version installed on workers via the relevant page.
• If your local version is newer, you can either resave the scene with our farm's version (after installing the matching version locally for testing), or wait for our farm-side update.
• For very old scenes, the safer route is to open the scene locally with our farm's engine version, do a small test render, then submit.

Still stuck? Engine-version skew is also a topic for when the symptom is wrong-looking output rather than a hard failure.

Output and render errors

These errors happen after the render starts. Either the job aborts mid-frame, the output looks wrong, or the frame writes to disk fail.

Frame writes failed (output path missing or full)

Error: Cannot write frame to output path <path>
Error: Disk quota exceeded

What it means: the worker rendered the frame but couldn't save it to the output location.

Common cause: the output path in your render settings points to a folder that doesn't exist on the worker filesystem, or your account's render-output storage has filled up.

How to fix:

• Set the render output path to a relative path inside the project, not an absolute drive-letter path. Most DCCs default to <project>/renders/ or similar — keep this convention.
• Check your output storage usage in the SuperRenders Client App or the web dashboard.
• If your storage is full, download finished renders and delete them from our cloud storage, or contact support about a temporary quota increase.

Still stuck? covers the output-storage workflow.

Render aborted mid-frame (out of memory)

Error: Render aborted — out of memory
Error: V-Ray: Could not allocate <N> MB
Error: Redshift: GPU out of memory (insufficient VRAM)

What it means: the render process consumed more memory than the worker had available and the OS killed the process.

Common cause: the scene is heavier than expected — typically very high-resolution textures, dense displacement, large polygon counts in scattered geometry (Forest Pack, particles, hair), or a render setting (e.g., bucket size, GI cache resolution) that allocates more memory than the scene actually needs.

How to fix:

• For CPU OOM: our CPU workers carry 96-256 GB RAM per node. If you're hitting OOM at this level, the scene likely needs optimisation. Try reducing bucket size in V-Ray (smaller buckets = lower peak memory), enabling out-of-core textures if your engine supports it (V-Ray Bitmap pager, Arnold autotile), or proxying heavy meshes (V-Ray Proxy, Redshift Proxy, Alembic).
• For GPU OOM: our GPU workers carry RTX 5090 cards with 32 GB VRAM each. For Redshift, enable "Out-of-Core" in render settings to spill textures and geometry to system RAM. For Octane, reduce texture resolution or enable out-of-core. For V-Ray GPU, try disabling "Use GPU memory only" if your scene exceeds 32 GB.
• For scattered-geometry scenes (Forest Pack, MultiScatter, X-Particles), consider per-instance LODs at render-time — most scattering plugins have a built-in "render-time geometry simplification" mode.
• If the scene legitimately needs more than 32 GB VRAM and out-of-core isn't acceptable, switching to V-Ray CPU on our 256 GB RAM fleet is a practical alternative — covered in detail at .

Still stuck? covers scatter-specific OOM patterns. For general scene-weight reduction, discusses tradeoffs.

Black or blank frames in output

Render completed successfully
Output: black/blank frame written to <path>

What it means: the worker reported the frame as rendered, but the output file is solid black or solid grey or empty.

Common cause: the most frequent reasons we see are: (1) no render camera set in the scene, (2) the active camera's view is locked to viewport (so it renders the viewport position, not the camera), (3) no lights in the scene with a render engine that doesn't have a default light, or (4) all geometry is hidden from rendering.

How to fix:

• Confirm a render camera is selected in the render settings (not "Active Viewport").
• For Maya specifically, check that "Render the current frame from camera" is set to your intended camera, not "Persp" by default.
• For Blender and Cinema 4D, check that the camera object is the active camera (not just selected).
• Confirm at least one light exists in the scene, or that your engine has a default environment light enabled.
• Confirm no scene-wide visibility flag has been toggled (3ds Max "Hide All", Maya "Hide" on the root node, Cinema 4D visibility traffic-light icons set to red).

Still stuck? Black-frame causes are surprisingly varied; is the deep-dive doc for this category.

Render quality artifacts (noise, fireflies, banding, wrong colours)

The render completed without an error message, but the output doesn't look right.

What it means: the render technically succeeded — no fatal error — but something in the output is visually wrong: excessive noise, fireflies (single bright pixels), colour banding, brightness mismatch versus your local preview, missing reflections, or other quality issues.

Common cause: quality artifacts have many causes (sample counts too low, denoiser settings, OCIO config drift, light cache size, GI bounces, etc.) and are out of scope for this page.

How to fix: the dedicated guide is . It walks through brightness mismatches, missing reflections, camera detection issues, and engine-specific quality tuning.

Submission and queue errors

These errors happen before your render starts producing frames — at submission time, in the queue, or during account authentication.

Job stuck in "queued" state

Status: Queued (no estimated start time)

What it means: the job was accepted by the queue but hasn't started rendering. The job is waiting on something — typically a worker to free up, or for the asset upload to finish.

Common cause: in our experience, three patterns cover most stuck-queue cases: (1) the asset upload is still in progress (a large project with many gigabytes of textures takes time to fully transfer), (2) the fleet you targeted is at capacity for the render engine you selected, or (3) a job-validation check is still running in the background.

How to fix:

• Check the upload progress in the SuperRenders Client App or web dashboard. If it shows "uploading" or anything below 100%, wait for it to complete.
• Refresh the queue view after a few minutes — if the fleet was at capacity, jobs typically start within a few minutes during business hours.
• If the job has been queued for over 30 minutes with no movement and your upload shows 100%, contact support.

Still stuck? Queue behaviour is one of those areas that's better answered through live chat than docs — we can see the queue state in real time on our side.

[PHASE 2D: screenshot — "Job queued" status indicator in the SuperRenders dashboard, showing the upload-progress icon]

Job rejected at submission (invalid frame range or missing required field)

Error: Frame range invalid (start frame > end frame)
Error: Required field "Output path" missing
Error: Render settings incomplete

What it means: the submission form's validation found a problem before the job entered the queue. Common: the frame range is empty, end frame is before start frame, output path is blank, or no render engine is selected.

Common cause: the submission was made before the scene's render settings were fully configured, or values were typed manually and a typo slipped through.

How to fix:

• In your DCC, open the render settings panel and verify: start frame, end frame, output path, output filename, file format, and render engine are all set.
• For animations, double-check frame range against your scene's actual animation range — a scene set to 1-100 won't render correctly if you submit frame range 100-1.
• If submitting through the web upload, fill all required fields (marked with *) before clicking submit.

Still stuck? walks through a complete submission with all required fields.

Authentication or login failure

Error: Login failed — invalid credentials
Error: Session expired — please log in again
Error: API key invalid or revoked

What it means: the SuperRenders Client App or your DCC submission plugin couldn't authenticate to our service.

Common cause: session timeout (most common — sessions expire after a period of inactivity), incorrect password after a recent change, or a revoked API key.

How to fix:

• In the SuperRenders Client App, sign out and sign back in.
• For DCC submission plugins, regenerate your API key in the web dashboard and update the plugin's settings with the new key.
• If "invalid credentials" persists with a known-good password, try resetting the password through the standard password-reset flow on superrendersfarm.com.

Still stuck? For account-access issues, live chat is the right channel — we may need to verify identity before resetting a session.

Account and billing errors

These errors prevent a job from starting because of an account state issue rather than a technical render issue.

Insufficient credits to start render

Error: Insufficient credits — estimated cost <X> credits, balance <Y> credits

What it means: the render job's estimated cost exceeds your current credit balance, so the job won't start.

Common cause: the estimated cost is calculated per-job at submission based on render engine, frame count, expected frame duration, and the fleet you're targeting. If your balance can't cover the estimate, the queue won't accept the job.

How to fix:

• Check your current balance on the dashboard.
• Top up credits through the dashboard's billing page. Credits are added immediately on most payment methods.
• If you want a more accurate cost estimate before topping up, use the with your render engine, frame count, and expected per-frame time.
• For longer-term capacity planning, explains how the credit system works and how the per-GHz model translates into credit cost.

Still stuck? shows the current credit packages and any active promotions.

Payment method declined or invoice unpaid

Error: Payment method declined
Warning: Account has unpaid invoice — new submissions blocked

What it means: the most recent attempt to charge your payment method failed, or there's an outstanding invoice that needs to be settled before new jobs can be submitted.

Common cause: card expired, billing address changed, bank declined the transaction, or a regional payment-method restriction.

How to fix:

• Update your payment method in the dashboard's billing settings.
• Pay the outstanding invoice through the billing page — once cleared, new submissions resume immediately.
• For declined cards on first attempt, the most common cause we see is a card not authorised for international transactions. Either contact your bank to enable international payments or use a different card.

Still stuck? Billing issues are usually faster to resolve through live chat or email — we can pull up the exact transaction record on our side and identify which step failed.

When this page doesn't have your answer

The errors above cover the patterns we see most often, but cloud rendering has a long tail of edge cases. Three escalation paths, in order of preference:

• The relevant DCC page — each page (3ds Max, Maya, Cinema 4D, Blender, Houdini, After Effects) has DCC-specific troubleshooting that doesn't fit on this general page.
• The FAQ — covers a few additional patterns that don't fit neatly into "error message" framing.
• Live chat on knowledge.superrendersfarm.com — for anything not covered by the docs, live chat is the right channel; our team replies during business hours and within minutes during peak periods.

For deeper engine-specific reference, vendor documentation is also worth bookmarking: the , , and cover engine-internal errors that are out of scope for this page.

We update this page when we see new error patterns repeating across multiple customers. If you hit something not covered here and the fix turns out to be non-obvious, let us know on chat — recurring patterns get added to the docs.