Theoretically yes but it's advised against in current Linker version. Because Linker uses Belnders' native FBX import/export under the hood - it falls short due to the same known limitations related to bone orientation ambiguity. Reliable support for rigs and animations is planned for the future Linker releases.

Yes. Linker is designed specifically for that purpose. It works well with Unity, UE and other engines.

Yes. But be caregul with two direction setup when linking files directly from repository. The synchronization is timestamp dependant and arbitrary. The newer file always wins - this behavior can overwrite your local work.

Reload replaces imported object instances. Constraints, drivers, or other data that referenced them may require repair after significant hierarchy changes.

Confirm it belongs to the linked model and shares its model ID. Linker includes viewport-hidden members, hidden collection members, and members in excluded view-layer collections, but it does not export unrelated objects.

Look for **Multiple values**. Reduce the selection to models with one format and a common value or preset selection. Resolve each policy group separately, then select them together again for later batch operations.

Two-way synchronization compares timestamps; it does not merge model data. Use explicit **Save** when Blender is authoritative or **Reload** when disk is authoritative.

Click **Save** for a deterministic export. Automatic dirty tracking depends on Blender dependency-graph notifications and may not observe every third-party add-on change.

Save the `.blend` first. Blender-relative `//` paths require a document location.