Feature Launch: A Faster Offline Render Workflow
Send offline render jobs instantly, name collections on the way out, and track every job with clear statuses.
Offline renders are how you scale from a live viewport to full datasets. But sending one used to mean babysitting the notebook page while the job processed.
Today, we're releasing an overhauled offline render flow: send jobs instantly, name collections as you go, and track exactly where every job stands.
What's New
- Instant sending of offline jobs, no waiting on the notebook page
- Name collections as you send them
- View the exact notebook snapshot behind each offline job
- Clear statuses for every stage of the render pipeline
Send and move on
You no longer have to wait in the notebook page for a job to process. Send the job and keep working: edit the notebook with the live viewport, or leave the page entirely. The platform handles processing in the background.
Name collections on the way out
Give collections descriptive names as you send them. When you're generating dozens of datasets a week, "port-approach-fog-v3" beats scrolling timestamps.
View Notebook Output
Every new offline render keeps a snapshot of the exact notebook used to send it. Open the snapshot to see precisely what produced a dataset, or download it to reuse later. If a job fails, the error shows up here too, so debugging starts from the actual code that ran.
Know exactly where your job stands
Offline renders now report four statuses:
- Dispatching: the platform is processing the notebook offline. You can exit the notebook page or keep working with the live viewport.
- Notebook error: something failed while processing the notebook. Check the error in View Notebook Output, resolve it, and send again.
- Queued: the job processed successfully and is waiting for an available machine.
- Rendering: the job has started rendering frames.
A healthy job runs Dispatching → Queued → Rendering → Completed. If it hits Notebook error instead, fix the issue and resend.
Why it matters
Dataset generation should run in the background, not block your work. With instant sending, named collections, and transparent statuses, you spend your time designing scenarios instead of watching progress bars.
Scale up your renders
Want to see how fast your team can go from scenario to dataset?