DocsRendering on the GPU
Rendering on the GPU
Since 1.0.2, Cycles renders on your graphics card by default, also when the agent or a script starts the render. Your own choice of device always wins.
What changed#
In Blender, Cycles starts on the CPU, and a render started by a script stays on the CPU until you open the Cycles devices in Preferences. Angelo sets your graphics card up about a second after it starts, and a scene's Device defaults to GPU Compute.
Angelo uses the first of these your computer has: OptiX, CUDA, HIP, Metal, oneAPI, with every card of that kind.
- New scenes, and scenes that never chose a device, render on the GPU.
- A scene saved with Device set to CPU stays on the CPU.
- A compute backend you set in Preferences ▸ System ▸ Cycles Render Devices, including None, or brought over from Blender, is left alone.
- Without a graphics card Cycles supports, Cycles renders on the CPU as before.
Going back to the CPU#
| For | Do this |
|---|---|
| One file | Properties ▸ Render ▸ Device: CPU. It is saved with the file. |
| Everything | Preferences ▸ System ▸ Cycles Render Devices: None. Angelo counts this as your choice and won't change it back. |
Renders the agent runs#
Ask the agent to render a still or an animation, bake textures, physics or a simulation, or export USD or Alembic, and it runs the job as Blender's own background job. Starting one always asks first.
- A card in the chat shows the job's progress, the frames and the time left, with Cancel. Frames already finished are kept.
- When it's done, Open opens what it wrote, and Details lists the files. The status bar shows the running job too (in Director, the top bar).
- Output goes next to your saved .blend file, or to Angelo's own folder for the chat while the file is unsaved. A new render never overwrites an earlier file; it takes the next free name.
- One job runs at a time and up to four wait their turn. Quitting Angelo or opening another file stops a running job.
Your own F12 renders, bakes and exports are plain Blender, as always.