Gamebridge Pro

Skava in Modeling


GameBridge Pro — Documentation

v1.0.3 · Blender 4.2 LTS and later, Blender 5 included · Unity (Built-in / URP / HDRP) / Unreal 4-5 / Godot 4 · Windows / macOS / Linux

Table of Contents


1. Install

  1. Download the add-on archive (do not unpack).
  2. In Blender: Edit → Preferences → Add-ons, press the arrow button in the top right corner and choose Install from Disk.
  3. Pick the ZIP, then enable GameBridge Pro in the list.
  4. Press N in the 3D Viewport — the GameBridge tab appears.

After installing, press N in the 3D Viewport: a tab named GameBridge appears in the sidebar.

2. Quick Start

  1. Select the objects you want to export. With Selected Only off (Export Settings), every mesh visible in the scene is exported instead; hidden objects stay out. Validation, Enforce Naming (which renames the objects in your scene) and baking run on everything that goes into the file — with Selected Only off, on every visible mesh.
  2. Open Sidebar → GameBridge.
  3. Pick the target engine (Unity / Unreal / Godot) and, for Unity, the render pipeline (Built-in / URP / HDRP).
  4. Set the export folder.
  5. Press Export to Engine.

GameBridge runs validation, applies the engine's naming rules, generates the configured collision meshes, and writes an FBX (Unity / Unreal) or .glb (Godot) with the correct axes and units.

3. Features

  • Engine-specific FBX / GLB export with correct axes, units, and FBX object_types (no stray cameras / lights).
  • Custom properties preserved as FBX user_properties.
  • Naming convention enforcement — PascalCase, illegal-character stripping, prefix application.
  • Collision generation — box, convex hull, triangle mesh; parented to the source and kept in place.
  • Validation — non-manifold, n-gons, flipped normals, missing UVs flagged before export.
  • PBR baking of six separate maps: diffuse, normal, roughness, metallic, AO, emission.

4. Engine targets

Engine Format Axes Notes
Unity Built-in / URP / HDRP FBX Y up / -Z forward The pipeline choice is recorded in the profile name; the export is the same
Unreal Engine 4 / 5 FBX Z up / X forward SM_ / UCX_ prefixes, user properties
Godot 4 GLB Y up (via glTF) snake_case names, Godot suffixes kept

5. Naming convention enforcement

With Enforce Naming on (the default), every exported object is renamed per engine convention before the FBX / GLB is written. The objects in your scene keep the new names.

  • Unreal: static meshes get the SM_ prefix; PascalCase; non-alphanumeric characters stripped.
  • Unity: PascalCase; characters other than letters, digits and underscores stripped.
  • Godot 4: snake_case; Godot suffixes such as -col kept. Only Latin letters and digits survive — non-Latin characters, Cyrillic included, are removed.

6. Collision generation

Choose between Box, Convex Hull, or Triangle Mesh in the Collision panel. Each generated collider:

  • Is parented to the source mesh with matrix_parent_inverse so it stays glued in place when the source moves.
  • Gets the engine-correct name (Unreal: UCX_; Unity: _Collision; Godot: -col).
  • Is automatically included in the FBX / GLB export so the engine picks it up on import.

7. Validation

Before each export, GameBridge runs a pre-flight check:

  • Non-manifold edges and vertices.
  • N-gons (faces with more than 4 vertices).
  • Flipped face normals.
  • Zero-area faces.
  • Missing UV layers.
  • Vertices with more bone influences than Max Bone Influences.

A missing UV layer, or flipped normals on more than a tenth of the faces, stops the export; everything else is listed as a warning and the export continues. Turn off Validate Before Export to skip the check.

8. PBR baking and channel packing

Bake PBR Maps bakes up to six separate maps with Cycles — diffuse, normal, roughness, metallic, AO and emission — at 512 to 4096 px, with an adjustable margin. Roughness and metallic are baked by routing the input through a temporary Emission shader. Version 1.0.3 does not pack channels: a Metallic+Smoothness, Mask Map or ORM texture is not produced.

9. Apply transforms

Version 1.0.3 has no apply-transforms step. If an object carries a rotation or a non-identity scale you do not want in the engine, apply it yourself (Ctrl+A → All Transforms) before exporting.

10. Animations

Version 1.0.3 exports meshes (the selected ones, or every visible one with Selected Only off) and their colliders only; armatures and animation are not written into the file.

11. Custom properties

Blender custom properties on exported objects are written into the FBX as user_properties. Unity does not read these by default — you need a small AssetPostprocessor script in the project. How Unreal uses them depends on your project's import setup.

12. Tips

  • Always apply transforms before export for Unity / Unreal.
  • For Unreal, leave Enforce Naming on to get SM_ prefixes the engine expects.
  • Collision in Unreal: UCX_ meshes are auto-detected as convex hulls on FBX import.

13. Troubleshooting

"Export silently fails / nothing appears" — set the export path; the operator returns early if it's empty.

"Collisions are floating away from the source" — fixed in v1.0.0: collision objects use matrix_parent_inverse so they stay glued.

"FBX contains my camera / light" — fixed in v1.0.0: the FBX exporter is restricted to mesh, armature, and empty types.

"Custom properties don't reach Unity / Unreal" — Unity needs an AssetPostprocessor; for Unreal it depends on your project's import setup.

14. FAQ

Q: How do I install GameBridge Pro?
A: See section 1 above.

Q: Which Blender versions are supported?
A: Blender 4.2 LTS and later.

Q: Why FBX / GLB and not USD?
A: Unity and Unreal still prefer FBX in practice; Godot prefers glTF.

Q: Can I use the result commercially?
A: Yes — without restriction. GPL-3.0 applies to the addon code only; what you export is yours.

15. Limitations

  • Unity needs an AssetPostprocessor to read FBX user properties.
  • USD format not supported (FBX / GLB only).
  • Validation flags issues but does not auto-fix them.

16. Support & License

For questions, bug reports, or feature requests please contact the seller through the marketplace messaging where you bought this add-on.

GPL-3.0. The license applies to the addon code only — what you export is yours to ship in any commercial project.

Changelog

v1.0.3 — Selected Only now works. On: only the selected meshes are exported, as before. Off: every mesh visible in the scene is exported; hidden objects stay out, and collision meshes come with their parent through Include Collision. Validation, Enforce Naming (which renames the objects in your scene) and texture baking run on everything that goes into the file, so with Selected Only off they cover every visible mesh. Before, the setting was not read and the file always held the selection.

v1.0.3 — Your selection and active object are put back after the export.

v1.0.2 — maintenance release. Minimum Blender is now 4.2 LTS. The package ships the full licence text and an updated README. No changes to the tools.

v1.0.1 — Godot export fixed. The modifier switch reached the glTF exporter under the FBX name, so the export call was refused and no file was written; it now uses the name glTF expects. Names keep their Godot suffix and their capitals: a mesh called Wall-col used to be renamed to allcol, losing both the hyphen the engine reads and the first letter. Suffixes -col, -colonly, -convcol, -convcolonly, -navmesh, -occ, -occonly, -rigid, -vehicle, -wheel and -noimp are preserved exactly; a mesh that already has one is not given a second. Checked on Blender 4.2.9, 5.1.0, 5.2.0, 5.2.1 and 5.2.2 by a run that reads the node names back out of the exported file.

v1.0.0 — first release.

$9.99

Have questions about this product?
Login to message

Details
Published 6 months ago
Blender Version 3.1 - 5.1
Extension Type N/A
Render Engine Used Arnold, Blender-Internal, Blender-Game-Engine, Cycles, Eevee, Freestyle, Luxrender, Mental-Ray, Octane, Vray, Yafaray
License Mit