Blenderflow Defaults
Every navigation and GPU-first setting Blenderflow configures for you.
Highlights
- Zoom-to-mouse and depth-aware viewport navigation
- Cavity shading enabled with both screen and world-space effects
- Automatic OptiX, CUDA, HIP, oneAPI, or Metal selection
- Cycles GPU Compute and GPU-accelerated denoising
- GPU compositor and compositor denoising
- Optional Eevee ray tracing on supported Blender versions
Blenderflow applies a small set of practical defaults so Blender is ready for fast navigation and GPU rendering as soon as the extension is enabled.
This page is the complete list of those defaults. It will grow as more carefully chosen setup options are added to Blenderflow.
When defaults are applied
- Install or enable — Blenderflow applies the input preferences and configures rendering for every scene in the current file.
- Re-enable — the same setup runs again.
- Open a .blend file — Blenderflow reapplies the render defaults to every scene in that file.
You can still change a setting during your session. Render defaults are applied again the next time a file is opened while Blenderflow is enabled.
Viewport navigation
| Setting | Default | What it changes |
|---|---|---|
| Zoom to Mouse Position | On | Zooms toward the pointer instead of the centre of the 3D view. |
| Auto Depth | On | Uses the depth beneath the pointer to improve viewport pan, rotate, and zoom behaviour. |
These correspond to Blender's use_zoom_to_mouse and use_mouse_depth_navigate input preferences.
Viewport shading
| Setting | Default | What it changes |
|---|---|---|
| Cavity | On | Adds subtle highlights and shadows around ridges and valleys so forms are easier to read. |
| Cavity Type | Both | Combines Blender's screen-space and world-space cavity effects. |
These settings are applied to the 3D Views across every available workspace in the current file.
Cycles compute device
Blenderflow detects the render devices available on the machine and chooses the first supported backend in this order:
- OptiX — preferred for compatible NVIDIA RTX hardware.
- CUDA — used for NVIDIA GPUs when OptiX is unavailable.
- HIP — used for compatible AMD GPUs.
- oneAPI — used for compatible Intel GPUs.
- Metal — used on compatible Apple hardware.
All compatible devices for the selected backend are enabled. The CPU device also remains checked for Blender's supported hybrid rendering, while each scene's main Cycles device is changed from CPU to GPU Compute.
If Blender cannot find a supported GPU backend, Blenderflow leaves Cycles on its available fallback instead of producing an error.
Cycles denoising
| Setting | Default |
|---|---|
| Render denoising | On |
| Viewport denoising | On |
| Render denoising device | GPU when available |
| Viewport denoising device | GPU when available |
| OptiX system | OptiX denoiser |
| Other supported GPU systems | OpenImageDenoise / Automatic |
Compositor
| Setting | Default |
|---|---|
| Compositor execution device | GPU |
| Compositor Denoise node device | GPU |
The compositor denoising-device option is applied only on Blender versions that provide it.
Eevee
Ray Tracing is enabled when the installed Blender version exposes the setting. Older supported versions that do not provide Eevee ray tracing are left unchanged.
Compatibility and fallbacks
Blenderflow checks whether every optional property exists before changing it. Missing version-specific settings, unavailable render backends, and unsupported GPU options are skipped safely so the extension can continue loading on Blender 4.2 and later.