Karelia Revision: review FBX and OBJ model updates in Blender and keep your finish

Import your original model into an owned baseline collection and finish it in Blender. When a revised source file arrives, stage it, review the differences and apply only the changes you want. The latest apply can be reversed from the Recovery section.

How it works

1. Import the baseline. Bring the original FBX or OBJ into an owned baseline collection and finish your scene in Blender.
2. Stage the revision. Select the revised source file. It is imported in a clean local background Blender process and compared with the baseline.
3. Review and apply. Check the counts and reasons, export the JSON report if you want to discuss it, then apply the changes you intend.

How objects are matched

Karelia Revision matches objects by a stable ID exported with each object. The sidebar and the JSON report count the matches made with a real stable ID and the lower-confidence matches made by exact name, in both the baseline and the revised file.

If the configured ID field is missing, the add-on shows the text and integer property fields that were actually exported. It never silently chooses another field.

Duplicate IDs and detected changes to the identity contract block apply. If both the name and the ID of an object change, no reliable match can be made.

What it keeps, and what it asks you about

• Local modifier stacks and material choices on updated objects, when the mapping requirements below are met.
• Parent relationships you added yourself.
• The current Blender data of source meshes that did not change.
• Placement: the source position is adopted by default, with an option to keep your local position.
• Removals: each one is an individual choice, never part of the select-all action.

Requirements

• Blender 4.5 LTS or newer. The tested combination is Windows with Blender 4.5.14 LTS.
• FBX or OBJ source files with meshes and/or empties.
• Stable, unique exported string or integer IDs for reliable matching. Without them, exact unique names are used only with your consent.
• Unique original source material names and an unchanged local material slot count.
• The installed Blender executable and its bundled FBX importer, because imports run in a clean local background Blender process.

From the Blendkit listing for version 0.3.0. Cross-platform and other Blender-version compatibility have not been validated yet.

Good to know

• This is conservative reconciliation, not a universal CAD merger. It is a beta, so test a copy of your own production files before you use it for client work.
• The incoming source hierarchy is flattened to world-space placement. Cameras, lights, curves, armatures and animated hierarchies are not supported.
• Exporter compatibility is not assumed: Revit and Archicad exports do not all carry usable stable IDs.
• There is no automatic UV or weight transfer across incompatible topology. Shape keys and conflicting local base-mesh edits need manual reconciliation.
• Modifiers remain, but index-dependent modifier results may need adjustment after the source geometry changes.
• No arbitrary custom-attribute transfer, no texture-file change audit and no universal geometry merge.
• Backup materials share shader datablocks, so later shader edits affect both the current object and its backup, and Recovery does not roll them back.
• Recovery works on revisions applied with 0.3. Older 0.2 backups need manual recovery.