skills.rest
Impertio-Studio
Impertio-StudioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

bonsai-errors-common

Diagnose Bonsai import, IFC runtime, schema, geometry, drawing, BCF, clash, and poll errors.

30|4|Updated Mar 5, 2026
Search Tags:#debugging#schema validation#blender#ifcopenshell#bonsai#ifc troubleshooting#operator poll
One-click install
npx skills add https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package --skill bonsai-errors-common-impertio-studio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bonsai-errors-common
Source: https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package/tree/main/skills/bonsai/errors/bonsai-errors-common
Command: npx skills add https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package --skill bonsai-errors-common-impertio-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you debug common Bonsai errors by identifying the true root cause behind IFC schema violations, spatial hierarchy issues, missing contexts, and operator poll failures instead of wasting time on symptoms and downstream breakage.

Core Features & Use Cases

  • Bonsai error decision trees: Quickly map an observed error message (imports, IFC runtime exceptions, schema validation failures, drawing issues, BCF issues, clash detection failures) to the correct fix section.
  • IFC schema & API migration guidance: Resolve frequent production issues such as importing the wrong module paths (blenderbim vs bonsai), deprecated ifcopenshell APIs (void.add_opening → feature.add_feature), and v0.8+ list-parameter breaking changes.
  • Bonsai production guardrails: Apply practical recovery strategies for representation context, IFC placement sync after Blender transforms, cache purging after direct API edits, and prevention of stale entity references.

Quick Start

Use the bonsai-errors-common skill to troubleshoot an error by pasting the full Bonsai/IFC error message and any relevant Blender+Bonsai/IFC version details, then follow the indicated fix section to recover.

Frequently Asked Questions about bonsai-errors-common

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Bonsai IFC workflow fail with operator poll errors in Blender BIM?▼

Bonsai operator poll failures in Blender BIM usually stem from incorrect spatial relationship APIs or missing representation contexts. This diagnostic maps the exact error signature to its root cause and identifies the specific API constraint or missing element triggering the poll failure.

How do I fix ifcopenshell schema validation issues when importing IFC files in Bonsai?▼

To fix ifcopenshell schema validation issues in Bonsai, apply the decision-tree guidance to trace the validation failure back to stale entity references or incorrect bonsai.* module paths, then purge the relevant Bonsai caches to restore schema integrity.

What is the correct way to migrate deprecated ifcopenshell APIs for Bonsai v0.8.x?▼

Migrating ifcopenshell APIs for Bonsai v0.8.x involves replacing deprecated functions like void.add_opening with feature.add_feature, switching to bonsai.* module paths, and passing list parameters for v0.8+ relationship functions to prevent runtime exceptions.

How do I resolve IFC placement sync problems after applying Blender transforms?▼

Resolving IFC placement sync problems after Blender transforms requires guarding IfcStore.get_file() against None and using the correct spatial relationship APIs to ensure the Bonsai geometry updates align with the underlying IFC placement data.

Do I need to purge Bonsai caches after direct ifcopenshell.api edits?▼

Yes, you must purge relevant Bonsai caches after direct ifcopenshell.api edits to prevent stale entity references and downstream breakage. Direct edits bypass internal Blender BIM synchronization, making cache purging a required technical constraint for state consistency.

Can I run Bonsai debugging scripts outside of the Blender Python environment?▼

No, Bonsai debugging scripts cannot run outside Blender Python because they require bpy access for environment and import error diagnosis. You must execute scripts via Blender Python to interact with the IfcStore and apply the necessary bonsai.* module path guardrails.

Related Skills

Explore More Software Engineering Skills→
OpenAEC-FoundationOpenAEC-Foundation
30

blender-core-api

Guide Blender Python API usage for bpy scripts and addons.

Official
Advanced
Impertio-StudioImpertio-Studio
30

aec-core-bim-workflows

Coordinate IFC model creation, enrichment, validation, and geometry workflows across IfcOpenShell, Bonsai, and Blender.

Official
Advanced
OpenAEC-FoundationOpenAEC-Foundation
30

bonsai-errors-common

Diagnose and resolve common Bonsai and IfcOpenShell errors in Blender BIM workflows.

Official
Advanced
Impertio-StudioImpertio-Studio
30

bonsai-impl-project

Configure Bonsai IFC projects with schema, units, and georeferencing.

Official
Advanced