Blender Volatile

Volatile knowledge

Everything in this file is tied to the live model catalog, a connector build, or a Blender version. Verify against the live environment before relying on it, and refresh this file when entries stop matching reality.

Local capability and parameter contract

Read blender-scene for the session contract. Check the callable tools and schemas only for the operations this task needs. A name in a skill or cloud source does not establish local availability. Inspect accepted units/fields and returned evidence; do not probe mutations just to test availability. Distinguish a missing tool from a failed connection.

If the typed still-render tool cannot express the required operation, use bl_execute with bpy.ops.render.render(write_still=True), an active camera and a fresh absolute output path. Capture and restore temporary render settings in a finally block; return output_path and verify/view the file. This does not add unsupported parameters to bl_render.

A successful local alternative verifies that operation, not an absent cloud tool. Report unresolved failures with the actual error and retain blocked checks. After an uncertain local mutation, recover via bl_job_status in the same session before further work; a timeout does not imply cancellation.

Model catalog context

The tables below are inherited model-routing hints, not a current catalog or parameter specification. Validate availability, input/output shapes and quality controls against the separately connected provider before choosing a route. Use its advertised schema; request include_schema only when supported. Do not route Blender work through unrelated marketing/preset chains.

Image — the routes this skill consumes

The rest of the live image catalog is not routing knowledge for Blender work — use the connected provider's live catalog when these hints do not fit.

3D

Local render and file boundaries

bl_render requires an absolute .png output_path; use a new path unless replacement is intended. It restores its temporary render overrides and can return an inline preview. If the host cannot view that preview, use an available file-transfer/viewing route. Rerendering to another inaccessible path does not resolve a retrieval failure. Camera renders do not prove desktop viewport state.

Blender 5.x traps

Version-dependent guidance: check the running build and its official API before relying on a property or node name. These notes are not a test report.

• Slotted actions: when the running API uses action slots, access via action.layers[].strips[].channelbags[].fcurves:

  def fcurves_of(ob):
      animation = getattr(ob, "animation_data", None)
      if animation is None or animation.action is None:
          return []
      act = animation.action
      action_slot = getattr(animation, "action_slot", None)
      if action_slot is None:
          return []
      slot = action_slot.handle
      return [fc for layer in act.layers
                 for strip in layer.strips
                 for cb in strip.channelbags
                 if cb.slot_handle == slot
                 for fc in cb.fcurves]
  

  Filter by the owning datablock's slot: an unfiltered shared-action walk can include curves belonging to other objects or object data. This example handles slotted actions; consult the version-matched API for legacy actions rather than treating a missing slot as proof of no animation.

  ob.keyframe_insert(...) still works unchanged — only reading/editing curves (interpolation, easing, handles) needs the new path.

• bmesh op naming: it is bmesh.ops.create_uvsphere (one word), alongside create_icosphere, create_grid, create_cone. Snippets writing create_uv_sphere raise AttributeError — a common hallucinated spelling, not an old API.

• EEVEE engine enum: compare the tool schema with the installed runtime. The local render schema includes BLENDER_EEVEE_NEXT; installed Blender versions may instead expose BLENDER_EEVEE. Read the runtime engine enum before overriding it; do not infer support from either spelling. If the scene already uses the intended engine, omit the optional engine argument. When an engine change is required, use a supported runtime value through the local-operation fallback, then render without overriding it. Do not silently switch to Cycles to conceal an EEVEE failure; report the schema/runtime mismatch.

• Movie output: codec and file-format availability vary by Blender build and GUI/background mode. Prefer bl_render_motion_reference if exposed; otherwise follow blender-greybox and check the actual runtime enums. Do not assume a vendored PyAV/FFmpeg fallback is installed or callable.

• Compositor: inspect whether the runtime uses Scene.node_tree or Scene.compositing_node_group and which output nodes it supports. A composition intended to process the scene render needs a connected Render Layers source; a Group Input alone does not establish that dependency. Inspect links, alpha and render settings when output is unexpectedly blank; render speed alone is not a diagnosis.

• Glare/Lens Distortion: property/socket layouts and enum values vary. Inspect the installed node inputs and RNA enums instead of copying old property names or assuming display labels are accepted identifiers.