Octane Live Viewer on a Remote GPU Machine: Lock Resolution, Regions and Multi-GPU Settings in Cinema 4D
Octane Live Viewer is the interactive render inside Cinema 4D. When Cinema 4D runs on a remote GPU machine, Live Viewer runs there too.
- Where it renders: on the GPUs of the machine where Cinema 4D is open
- Lock Resolution: renders the render-settings frame; a 0.5 multiplier turns 1920×1080 into 960×540
- Navigation: sub-sampling 2×2 or 4×4 lowers resolution only while the camera moves
- Detail checks: Render Region keeps sampling inside a box you draw
- Final frames: render through the Picture Viewer, not Live Viewer
Most Octane look-dev happens in Live Viewer: you move a light, change a roughness value and watch the frame clean up. On a remote GPU workstation the same window works, but it helps to know which part of the job runs where, and which Live Viewer controls cut the work per update.
This guide covers how Live Viewer behaves on a remote machine, the controls that keep it responsive (Lock Resolution, sub-sampling, Render Region, Film Region, update checks), the Devices tab settings for a multi-GPU server, and when to leave Live Viewer and render through the Picture Viewer.
Checked against OTOY documentation for Octane for Cinema 4D and the OTOY Live Viewer Deep Dive guide (Octane 2023.1.2, Cinema 4D 2024.2), November 2026.
1. What Live Viewer renders, and what it leaves out
Live Viewer is built for fast feedback, not for final output. According to OTOY’s Live Viewer documentation, it does not load assets from disk; it uses what Cinema 4D currently has in memory. Sampling may be reduced to keep updates quick.
The same page warns that anything time-dependent, such as motion blur, MoGraph and simulations, may not display properly in Live Viewer. For frames that match the final look, render through the Render Settings and save passes with the Render AOV Manager.
- Use Live Viewer for: materials, lights, camera framing, noise checks on still frames.
- Use the Picture Viewer for: animation, motion blur, MoGraph, simulations and every frame you deliver.
2. Where Live Viewer runs when Cinema 4D is on a remote machine
On a remote workstation, Cinema 4D and Octane are installed and open on the server. Live Viewer therefore renders on the server GPUs, and the scene sits in the server’s RAM and VRAM. Your own computer sends keyboard and mouse input through the remote desktop and shows the picture that comes back.
Two practical results follow. First, how fast the image cleans up depends on the server GPUs, not on the card in your own computer. Second, if Live Viewer feels slow, check the render load before you blame the connection: a 4K Lock Resolution, a heavy kernel or all update checks firing on every change will slow it down on any machine.
3. Five controls that keep Live Viewer responsive
The OTOY Live Viewer Deep Dive and the Live Viewer commands page describe the controls below. Each one either lowers the number of pixels per update or limits what Octane has to re-render.
- Lock Resolution: renders the frame size from your render settings, 1:1, instead of whatever fits the window. With it on, a multiplier field appears: 0.5 at 1920×1080 renders 960×540, and 2 renders 3840×2160. A second field only zooms the view and does not change what is rendered or saved.
- Sub-sampling: in the Options menu. 2×2 renders every 4th pixel and 4×4 every 16th while the camera moves, then returns to full resolution when you stop.
- Render Region: stops rendering outside a box you draw and keeps adding samples inside it, past the Max Samples value. Useful to judge noise on one area.
- Film Region: blacks out the rest of the frame and renders only the box up to Max Samples. Useful for patches or quick thumbnails.
- Update checks: four toggles (geometry, lights, camera, materials) decide what triggers a re-render. Turn them back on after troubleshooting, or edits will not show.
Pause halts rendering at the current sample and resumes from there. Max Samples is set in the kernel settings, not in Live Viewer, and Live Viewer stops when it reaches that number. The kernel you pick in the Live Viewer Kernel Selector is also the one used for the final render. Live Viewer also has clay modes (see Octane clay render in Cinema 4D) and a focus picker for depth of field (see Octane depth of field and bokeh in Cinema 4D).
4. Multi-GPU settings for Live Viewer on a 2x, 4x or 8x server
Octane uses the GPUs enabled in Octane Settings > Devices. The Devices tab documentation lists four check boxes per GPU: rendering, priority, tone mapping and denoising.
Per-GPU options in the Devices tab
What each check box controls, and how OTOY suggests setting it when every card is the same model.
| Option | What it controls | On a server with identical GPUs |
|---|---|---|
| Render | Whether the GPU renders at all | Tick every card |
| Priority | How much the GPU is used, similar to CPU priority in Task Manager | High on every card (OTOY advice for identical GPUs) |
| Tone mapping | Whether the GPU is used for tone mapping | Not covered by OTOY's multi-GPU advice; keep the default |
| Denoising | Whether the GPU runs the AI Denoiser | Keep VRAM headroom on the card that denoises |
For several GPUs of the same model, OTOY’s advice is to enable all of them at High priority and not to add a weaker card. The same page notes that render speed scales with more GPUs, but VRAM does not add up: the card with the least VRAM limits the scene. The number of GPUs Octane can use at once also depends on your OTOY plan.
Some Octane for Cinema 4D versions also have a Use all GPUs option in the render settings. In an OTOY forum answer, an OTOY moderator explains that leaving it off makes the render use only the GPUs ticked in the Devices tab. Check which behaviour your version has before a long render.
5. Saving from Live Viewer versus rendering final frames
For a single still, Live Viewer can save directly: File > Save Image As writes PNG or EXR. The Deep Dive guide stresses keeping Lock Resolution on when you do this, otherwise the file matches the window size instead of your render settings.
For anything else, use the Picture Viewer or a command-line render. That path loads assets from disk, renders time-dependent effects and writes all passes from the Render AOV Manager. A simple routine on a remote machine:
- Block lighting and materials at Lock Resolution 0.5, with sub-sampling on for camera moves.
- Switch to 1 and draw a Render Region over the area you are judging.
- Render one hero frame through the Picture Viewer and compare it with Live Viewer.
- Send the range once the hero frame is right.
Octane look-dev on a render farm: SaaS or IaaS?
Which farm type fits interactive Octane work
A SaaS farm renders a scene you submit. IaaS gives you the whole machine, so Live Viewer comes with it.
| Situation | Usually a better fit | Why |
|---|---|---|
| Dialling in materials and lights in Live Viewer | IaaS (remote workstation) | Live Viewer needs Cinema 4D open on the GPUs; a submit-only farm has no interactive session |
| Locked scene, only frames left to render | Either | Both can render a finished project; compare price and plugin support |
| Plugins or Octane version not on a farm's list | IaaS | You install what the project needs on the machine |
| Checking a hero frame at final resolution before the range | IaaS | You can judge it in Live Viewer, then render the range in the Picture Viewer |
Rule of thumb: if you still need Live Viewer, you need the machine, not only a render queue.
A test workflow on an iRender server
On iRender you rent a whole Windows workstation with Cinema 4D and OctaneRender installed, and sign in with your own OTOY account:
- Upload the project through iRender Drive (File > Save Project with Assets keeps textures with the scene).
- Start a 1x, 2x, 4x or 8x RTX 5090 server (32 GB per card) and connect to it.
- Open Cinema 4D, sign in to OTOY, then tick every GPU in Octane Settings > Devices.
- Open Live Viewer, turn on Lock Resolution and work at 0.5 until the look is right.
- Switch to 1, check detail with Render Region, then render the range through the Picture Viewer.
- Your image, software and settings stay saved for the next session.
Octane Live Viewer remote checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. Does Octane Live Viewer use every GPU in a multi-GPU machine?
It uses the GPUs enabled in Octane Settings > Devices, up to the number your OTOY plan allows. For identical cards OTOY suggests enabling all of them at High priority. VRAM does not add up, so each card must hold the scene.
2. Why does Live Viewer look different from my final render?
Live Viewer uses what Cinema 4D has in memory and may reduce sampling for speed. Time-dependent effects such as motion blur, MoGraph and simulations may not display properly. Render through the Picture Viewer to see the final result.
3. What does Lock Resolution do in Octane Live Viewer?
It renders the frame size set in your render settings, 1:1. A multiplier field appears: 0.5 renders half width and half height. The second field only zooms the view.
4. What is the difference between Render Region and Film Region?
Render Region keeps sampling inside a box past Max Samples and stops updating outside it. Film Region blacks out the rest of the frame and renders the box only up to Max Samples.
5. Can I save a final image from Live Viewer?
Yes, for a still: File > Save Image As writes PNG or EXR. Keep Lock Resolution on so the file matches your render settings. For animation and passes, render through the Picture Viewer with the Render AOV Manager.
6. Is a slow Live Viewer caused by the remote connection?
Live Viewer renders on the server GPUs and the remote desktop sends back the picture. If the image itself cleans up slowly, the render load is the cause: lower the Lock Resolution multiplier, use sub-sampling or draw a Render Region.
7. Is Octane installed on iRender Cinema 4D servers?
Yes. Cinema 4D and OctaneRender are installed, and you sign in with your own OTOY account, so your license and plan apply on the server.
Render your Cinema 4D and Octane 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 or RTX 5090 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. Cinema 4D and OctaneRender are installed; sign in with your own OTOY account (OTOY’s Studio+ plan has no GPU limit for multi-GPU servers). Your server image is saved between sessions.
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, so they keep their boost clocks. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start Cinema 4D and Octane on an iRender server:
On a 4x RTX 5090 server, a 300-frame Cinema 4D + Octane animation rendered in 1 hour 18 minutes. The second clip runs the same kind of scene on 4x RTX 5090 and 4x RTX 4090:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Octane render farm page, download the iRender GPU app, or read multi-GPU render engines in Cinema 4D.
Sources: OTOY: Anatomy of the Live Viewer, OTOY: Live Viewer commands, OTOY: Options menu, OTOY: Devices tab, OTOY: Live Viewer Deep Dive, OTOY forum: Use all GPUs. Checked November 2026.




