Konjure ships a Blender 5.2 extension for importing, exporting and locally synchronizing scene bundles. Download konjure-blender.zip, then in Blender choose Extensions → Install from Disk and select the archive. The extension adds File → Import and File → Export entries plus a Konjure panel in the 3D View sidebar.
Exchange a scene file
Use Export in Kreate or Blender to write a .konjure scene bundle, then
use the other application’s import command. The extension owns its Konjure
collection and leaves the rest of the Blender file alone.
Export transfers evaluated meshes and materials, local parent hierarchy, split
normals, and metre-valued coordinates. Blender’s Z-up coordinates are converted
to Konjure’s Y-up convention. Importing into Kreate creates a main module with
editable transforms, materials and hierarchy, plus generated geometry_N
modules for baked triangle meshes. Positions and normals round once into
Tensor[f32]; transforms retain language Number/f64 values.
The exchange is bounded. Imports reject over-large or unsupported complex meshes
and generated projects instead of dropping geometry. It does not transfer
modifier graphs, texture links, custom shader graphs, animation, or procedural
source. Keep the .blend file and Kreate source project: those are the editable
sources for the information the exchanged scene cannot represent.
The exporter evaluates Blender’s dependency graph before it reads mesh data; that is Blender’s documented evaluated object workflow. The included Suzanne example follows the pinned Khronos Suzanne CC0 asset.
Connect Kreate and Blender locally
Start the local bridge from the repository root:
cargo run -p konjure-tools --bin kj-blenderIt listens on 127.0.0.1:8766 and prints a private pairing token. Open
Blender in Kreate and the Konjure 3D View panel in Blender; enter the
same endpoint and token in both interfaces, then connect.
Use Send to put the current editor’s evaluated scene on the bridge and Pull to create or update the other side. Enable Auto sync only after an initial Send or Pull binds the two working copies. The bridge accepts ordered revisions. A conflict pauses Auto sync and keeps the local draft; resolve the choice deliberately with Pull or Send rather than silently replacing either editor’s work.
The bridge is local by default. It exchanges JSON scene bundles and does not execute Python supplied by a remote peer. Disconnecting stops Auto sync and leaves both current documents unchanged.
Blender sync currently runs in Kreate’s local workspace. Leave a paired device session before importing or syncing from Blender; you can pair the resulting project after the exchange. Phone and tablet browsers can exchange scene files, but the loopback bridge connects editors running on the same computer.