Altus vs OIDN vs OptiX in Redshift (2026): Choosing a Denoiser for Flicker-Free Animation
Use OptiX or OIDN while you work, because they are fast enough for interactive rendering. For final animation frames, render enough samples for an acceptable level of noise first, then denoise; Maxon recommends Altus Single Pass for new Altus users.
- OptiX: very fast, NVIDIA only, but may leave noise and can show flickering splotches in animation.
- OIDN: fast and interactive on any hardware, with the same risk of leftover noise.
- Altus: production-proven, bucket rendering only, takes several seconds per frame.
- Workflow: tune samples first; denoising is a finishing step, not a substitute for samples.
Redshift supports three denoisers: Innobright’s Altus, NVIDIA’s OptiX AI denoiser and Intel’s Open Image Denoise (OIDN). On a still frame they can all look good. In animation, the differences show up as flicker, smeared detail or noise that changes from frame to frame.
This guide compares the denoisers using Maxon’s documentation, explains why animation needs a different approach from stills, and lists the settings that fix the common problems.
Checked against Maxon’s Redshift Denoising and Redshift renderer documentation for Cinema 4D, November 2026.
1. Which Redshift denoiser should you use for animation?
Use OptiX or OIDN for interactive look-dev, and test Altus for final animation frames. Maxon describes Altus as using production-proven algorithms, so results can be more predictable, while OptiX and OIDN are deep-learning denoisers that are fast enough for interactive rendering but can have more trouble cleaning noise.
Redshift denoisers at a glance
What Maxon says about each denoise engine.
| Engine | Strengths | Limits |
|---|---|---|
| OptiX | Very fast; usable while editing the scene | NVIDIA only; may leave noise; can show flickering splotches in animation |
| OIDN | Fast; usable in interactive rendering | Can have more trouble cleaning noise than Altus |
| Altus Single Pass | Production-proven; recommended for new Altus users | Takes several seconds; bucket rendering only |
| Altus Dual Pass | Renders the frame twice to find the noise | Twice the render passes; bucket rendering only |
2. Why does denoising flicker in animation when stills look clean?
Because each frame starts from different noise, and a denoiser that removes most of it can leave different leftovers on every frame. Maxon warns that with AI denoisers, noise in animations might appear as flickering splotches that can be more distracting than the original noise. Its advice is to tune samples for an acceptable level of noise first and then denoise, which it says is particularly important for animation.
In other words, denoising is a finishing step. Cutting samples hard and relying on the denoiser works for stills more often than for moving shots.
The top row is what Maxon warns about: with few samples, an AI denoiser removes most of the noise but leaves splotches that change place every frame, and the eye reads that as flicker. The bottom row follows Maxon’s advice to tune samples first, so each frame has little left to remove and frames stay alike.
How to spot flicker before a client does: watch the test at full speed, not frame by frame. Look at flat or dim areas, soft shadows and slow camera moves, where leftover splotches show most. If one region “boils”, raise samples for that shot before you switch denoisers.
3. How do you set up Altus in Redshift?
Choose Altus Single Pass or Altus Dual Pass as the denoise engine and render in buckets; Maxon notes that Altus does not work in progressive rendering. Single Pass renders the frame once; Dual Pass renders it twice before denoising. Maxon recommends Single Pass for new Altus users.
Altus uses extra AOVs, Diffuse Albedo, World Position and Bumped Normal. With Automatically Create AOVs enabled, Redshift adds them for you. The kc1, kc2, kc4 and kf settings control strength; if bump detail looks too smooth, Maxon suggests lowering kf.
Step 1: Render a short moving test
Pick 20 to 30 frames with camera motion and fine detail; a still frame will not show flicker.
Step 2: Set samples before denoising
Raise sampling until the raw render has an acceptable level of noise, as Maxon recommends for animation.
Step 3: Compare two engines
Render the same frames with OptiX or OIDN, then with Altus Single Pass in bucket mode, and play both back.
Step 4: Tune and render
Keep the engine with the steadier playback, lower kf if Altus smooths bump detail too much, then render the sequence.
Common denoising problems and fixes
- Splotches crawl across flat areas in playback: too few samples for an AI denoiser. Raise samples first, as Maxon recommends for animation.
- Altus does nothing in the Render View: Altus works only in bucket rendering. Use OptiX or OIDN while you work in progressive mode.
- Bump or fine detail looks smeared: lower kf in the Altus settings.
- Altus output looks wrong or unchanged: check that Diffuse Albedo, World Position and Bumped Normal AOVs exist, or enable Automatically Create AOVs.
Source: Maxon: Redshift Denoising.
4. When does a multi-GPU server help with denoised animation?
Rendering more samples before denoising is the reliable fix for flicker, and samples cost GPU time. Redshift renders each frame on all the GPUs in a machine, so a 4- or 8-GPU server lets you keep samples high for a whole sequence instead of cutting them and relying on the denoiser.
A SaaS render farm renders finished jobs with its own setup, which suits shots whose denoise settings are final. An IaaS server is a whole machine you control: you open the scene in Cinema 4D, compare denoisers on a short moving test, and render the sequence as on your workstation.
A test workflow on an iRender server
- Upload the project to iRender Drive before you start the server; uploading is free and does not use rental time.
- Start a server with 2, 4 or 8 RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs. Cinema 4D and Redshift are pre-installed.
- Render a short moving test with OptiX and with Altus Single Pass, and compare the playback.
- Render the sequence with the steadier setup, then shut down; billing is per minute.
Frequently asked questions
1. Which denoisers does Redshift support?
Redshift supports Innobright’s Altus, NVIDIA’s OptiX AI denoiser and Intel’s Open Image Denoise (OIDN). Altus comes in Single Pass and Dual Pass modes.
2. Why does my Redshift animation flicker after denoising?
Each frame has different noise, and AI denoisers can leave flickering splotches in animation. Maxon recommends rendering enough samples for an acceptable level of noise first and then denoising.
3. Is Altus better than OptiX for animation?
Maxon describes Altus as production-proven and more predictable, while OptiX is much faster but may leave noise. Test both on a short moving sequence and keep the one that plays back steadier.
4. Why does Altus not work in the Redshift IPR?
Altus works only in bucket rendering, not in progressive mode, and takes several seconds per frame. Use OptiX or OIDN for interactive work.
5. What is the difference between Altus Single Pass and Dual Pass?
Single Pass renders the frame once and then denoises. Dual Pass renders the frame twice before denoising. Maxon recommends Single Pass for new Altus users.
6. Altus is smoothing my bump detail. What should I change?
Maxon suggests lowering the kf setting when Altus smooths the lighting on bump-mapped detail too much.
7. Can I test Redshift denoisers on an iRender server?
Yes. Cinema 4D and Redshift are pre-installed. Render a short moving test with each denoiser, then render the sequence on 2, 4 or 8 GPUs. Billing is per minute.
Render your Cinema 4D and Redshift projects on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. Your server image is saved between sessions, so your plugins and settings stay installed. Cinema 4D and Redshift are pre-installed on every server.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start a server and render Cinema 4D and Redshift on it:
Two Redshift runs we recorded on our servers: 150 frames at 1080p on 4x RTX 5090 at 40.84 seconds per frame (about 1h 42m), and a 301-frame cloth simulation at 1080p on 1x RTX 5090 at 21.3 seconds per frame:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Cinema 4D and Redshift render farm page or download the iRender GPU app.




