Cinema 4D plugin
Cinema 4D 2026. Includes the compiled fast path that keeps heavy meshes from stalling the application.
The problem
Export, import, fix, export again
The loop costs more than the modelling. You export an FBX, import it, fix what the round trip broke, then do all of it again because the shape was wrong by two centimetres. Datasmith re-imports are the same tax with a different name.
Mesh Gate removes the step. The object is already in Unreal while you are shaping it, lit by your real lighting, next to your real level. You stop guessing what it will look like in the engine, because you are looking at it in the engine.
How a change travels
Two applications, one link
Cinema 4D and Blender run the same core and speak the same protocol, so the Unreal side never learns which one is on the other end. Everything stays on your machine, over localhost.
Blender add-on
Blender 5.2 and up, at parity with Cinema 4D for everything except lights and instances sent from Unreal.
Unreal plugin
Unreal Engine 5.8. Place one actor in your level and the link is up; Mesh Gate Lite is the same plugin with the commit side switched off.
Live
It is already in the engine
Everything below happens while you work, with no export step anywhere in it.
Geometry, evaluated
Meshes, primitives, generator and modifier stacks arrive as the finished mesh. A Subdivision Surface over a Volume Mesher over a Bend comes across as one object, because the emitter reads the application's own evaluated result rather than trying to reproduce it.
Deforming meshes update in place — cloth, rope, soft bodies and sculpting send new vertex positions with normals following, and nothing is rebuilt. That is what makes simulation preview worth watching.
Thousands of clones stay light
Cinema 4D Cloners, and Blender's collection instances, Geometry Nodes scatters and particles, travel as instance transforms plus one prototype — never as baked geometry. A thousand clones stay a thousand clones, exactly where you put them.
Per-clone effector data — colour, weight, index, UVW — arrives as per-instance custom data your Unreal materials can read.
The bake bucket, for the heavy things
Most edits stream as you make them. Genuinely heavy operations — big booleans and volumes — are sorted into a bake bucket automatically, so they do not rebuild on every drag of the mouse.
They go when you ask, with Sync bake bucket, or on their own when editing pauses. Everything else keeps streaming while they wait.
Cinema 4D
What you see is what is sent
Switch a generator off and the mesh underneath comes through — not the generated result, and not nothing at all. Switch it back and the generated form returns.
It is the case a cache-reading emitter is most likely to get wrong, because a disabled generator still holds a cache. It is a verified round trip, both directions.
Big meshes, no waiting Cinema 4D
A C++ fast path reads heavy meshes directly. An 810,000-polygon object syncs in a fraction of a second, where it used to freeze Cinema 4D for seconds.
Transforms are free
A move updates the actor and re-runs nothing else. Only what changed is sent.
UVs, up to eight channels
UV0–UV7, per polygon corner, both directions. Seams survive the trip.
Normals and hard edges
Phong angle and hard edges kept, including Blender's own corner normals — smooth, flat, sharp edges and custom normals.
Vertex colours
Travel when something is painted, and every repaint arrives. The round trip is colour-correct, linear and sRGB handled.
Cameras
Real CineCameraActors. Focal length, filmback, f-stop, focus, ISO and shutter as physical quantities, so framing and depth of field match. Redshift cameras arrive intact.
Lights Cinema 4D
Standard lights arrive as real Unreal lights, omni to point and so on, with colour temperature correct.
Cables from splines Cinema 4D
A spline with a cable radius is swept into a tube with UVs in centimetres, so one tiling material reads the same on any length. Follows deformers and rope simulation.
Metadata that acts
User Data and custom properties become keys Unreal acts on — folder, material, tags, collision, shadows, PCG graph. Unknown keys are reported, never silently ignored.
Selection, both ways
Pick an object in Unreal and it is selected back in the application you modelled it in.
Frame-locked rendering
Ask for a frame and block until Unreal matches it. A slow simulation frame costs render time, not accuracy.
Autosync, or one at a time
Stream continuously, or pause and send objects by hand. A paused link never deletes anything in Unreal. The link survives either side restarting.
Materials and textures
Pick them, or let it build them
Pick Unreal materials from a list
Name a content folder, and every object's Mesh Gate tag — the sidebar, in Blender — lists that folder's material instances in a dropdown, one per slot. The pick is stored by path, so adding materials in Unreal never changes what an object uses.
An Unreal material that shares the application's material name binds on its own, with no picking at all.
Several materials on one mesh
One Unreal material slot per source material, the way an FBX export does it. Texture tags on polygon selections are respected, and committing bakes one section per slot.
Build materials in Unreal
Opt in and every texture is imported, each material built as an instance of one Substrate master — Standard and Redshift node materials alike. Hand-made Unreal materials always win.
Commit
When it is right, it becomes a real asset
Live preview is for deciding. Commit is the crossing point: each object becomes a real Static Mesh asset on disk with a persistent actor that owns it. From then on it belongs to Unreal — texture it, light it, ship it.
Real assets, built in the background
Identical geometry is detected and collapses to one asset and one instanced component. Re-commit updates in place and skips unchanged meshes. Optional Nanite and lightmap UVs. The editor never blocks.
Proxies place your own assets
Name a real Unreal asset on an object and Commit places that asset instead, fitted by pivot, scale or both. A Cloner of proxies becomes one HISM.
Skeletal meshes Cinema 4D
A rigged, skinned mesh commits as a real USkeletalMesh and USkeleton, from its bind pose and weights.
Bake Camera
A camera move becomes a Level Sequence — plus a rail rig if it rode a spline — that plays and renders through Movie Render Queue with no modelling application running.
Uncommit
Hand a committed object back to live streaming. Sync re-bakes what was already committed.
SceneMagic keys
Metadata becomes actor tags and asset metadata, in both directions.
Two-way
Bring it back, change it, put it back
Send an Unreal actor to Cinema 4D or Blender and it arrives as an editable stand-in — quads you can still model, with the original hidden rather than deleted. Bake Selected writes the edit back onto the same actor and the same asset.
Edit
Model it properly and bake the new mesh back onto the actor it came from.
Transforms Cinema 4D
Simulate it. A Rigid Body on the stand-in, and only the resulting placement comes back — the mesh is untouched.
Instances Cinema 4D
An ISM or HISM arrives as a Cloner, one clone per instance with its custom data, and returns as instance transforms.
Revert
Put actors back exactly as they were before Mesh Gate first wrote into them — transform, mesh, materials, instances, custom data and tags — in one undo step.
Scripting and pipelines
Every button has a call
Each call names what it acts on and returns data, which makes it usable by a pipeline or by an AI assistant driving the applications over MCP. Every call takes an optional job id, so one piece of work can be followed through every tool, and an editor name that is recorded as the asset's origin.
- Unreal Python
unreal.MeshGateScripting— status, send to the application, bake back, commit, revert.- Cinema 4D Python
import meshgate— status, autosync, sync, commit, proxies, cables.- Blender Python
import meshgate— status, autosync, sync, commit.- Headless
- Cinema 4D without its interface drives a headless Unreal end to end — thirty cable runs built, synced and committed, with nobody watching.
The scripting API is part of the full edition. Mesh Gate Lite answers status().
When it goes wrong
You are told, not left guessing
Heartbeat
The application beats from its main thread. If it freezes with the socket still open, Unreal says so within seconds — and keeps saying it until it is back.
Log files
Written for both applications, in %LOCALAPPDATA%\MeshGate\logs, so a
problem can be read after the fact.
Reports a producer can read
Every send, arrival, commit and bake as JSON lines — started, step, done, error — with checkable evidence: asset paths, counts, and whether the application was still alive afterwards.
Editions
Mesh Gate, and Mesh Gate Lite
There is no trial. Lite is the trial — the same plugin with the commit side switched off, free and with no time limit. Upgrading means installing the full Unreal plugin in its place; the Cinema 4D plugin and Blender add-on are identical for both.
| Feature | Mesh Gate | Lite free |
|---|---|---|
| Live streaming from Cinema 4D and Blender | Yes | Yes, up to 25 objects |
| Materials, lights, cameras, instances while streaming | Yes | Yes |
| Commit, Bake Selected, Uncommit, Revert | Yes | No |
| Unreal to the application, and back | Yes | No |
| Bake Camera | Yes | No |
| Unreal script API | Everything | status() only |
Lite shows the full edition's buttons greyed out rather than hiding them, so you can see what you would be getting. Mesh Gate is $149.99 at launch on Fab.
Requirements and honest limits
What it needs, and where it stops
Listed because a tool you can trust is one that tells you where it stops.
Requirements
- Windows 10 or 11.
- Unreal Engine 5.8.
- Cinema 4D 2026, or Blender 5.2 and up.
- Both applications on one machine — the link is localhost TCP, port 8412.
Not supported
- macOS and Linux.
- Unreal versions other than 5.8.
- One application per port at a time — Cinema 4D or Blender, not both at once.
- Editor only. Nothing streams into a packaged game; committed assets ship like any others.
Known gaps
- Cinema 4D sends nothing mid-drag — a move arrives when you let go, because Cinema 4D does not notify plugins during one.
- Blender has no lights, and does not build instances sent from Unreal. Edit mode works.
- Redshift's own lights are not translated.
- Skeletal animation clips are not baked. A skinned mesh merged from several objects is refused rather than baked wrongly.
- Committed objects stop updating until re-committed.
- Live previews opt out of Lumen; committed geometry lights normally.
- One active document at a time.
- The socket is unauthenticated — right for a workstation, not for a network.
Questions
Before you install it
- Do I need to know Unreal?
- You need an Unreal 5.8 project and to place one actor, the Mesh Gate Bridge. Everything after that happens in the application you already model in.
- Is it free?
- Mesh Gate Lite is free — up to 25 live objects, without Commit. Mesh Gate is paid, on Fab. The Cinema 4D plugin and Blender add-on are free either way.
- Cinema 4D or Blender?
- Both, into the same Unreal plugin. One at a time per port.
- Does it replace FBX and Datasmith?
- For iteration, yes — there is no export step. Commit makes real assets when you are done, and those behave like any other asset.
- Will it work on a Mac?
- Not yet. Windows only.
- Which Unreal versions?
- 5.8.
- Can my pipeline or my AI tools drive it?
- Yes. There is a Python API in all three applications in the full edition, built for MCP-driven workflows.
- Can it stream into a packaged game?
- No — it is an editor tool. Commit bakes real assets, and those ship normally.
Downloads
Get it
Cinema 4D plugin
For Cinema 4D 2026, including the compiled fast path. Needed whichever Unreal edition you run.
DownloadBlender add-on
For Blender 5.2 and up, as an installable extension. The user guide comes with it.
DownloadMesh Gate Soon
The full Unreal plugin: commit, two-way editing, Bake Camera and the complete script API.
Coming to FabMesh Gate Lite Soon
Live streaming up to 25 objects, with no time limit. The Blender add-on comes with the Fab download.
Coming to FabEvery control is documented in the user guide.