Epic's second Fab freebie drop of August closes Tuesday, August 25, 2026. If you claimed the Nordic Fishing Hut interior/exterior kit and your project isn't Unreal Engine, the mesh you get after import is not the mesh Epic shows in the screenshots — Nanite quietly swaps in the lowest LOD the moment you export, and the scale is wrong by a factor of 100 in Unity or Godot. Both are fixable in under ten minutes if you know where to look.
Three free assets, one export headache
The August 11–25 giveaway on Fab includes three Unreal-native assets: Voyager: Cover System (a Blueprint gameplay system, engine-locked, skip it if you're not on UE5), Dynamic Spline FX 2 (a Niagara VFX pack, same problem), and the Nordic Fishing Hut — Coastal Lakeside Cabin, a static-mesh interior/exterior building kit. The Fab Standard license covers all three for "any engine or tool," per Epic's own EULA language, so the cabin kit is the one worth the download even if your project runs in Unity or Godot.
Godot doesn't have native Fab integration yet — Epic has only committed to it as a future item — so your path in is the generic 3D export, not a plugin. That's exactly the path where Nanite and unit scale bite.
What breaks when Nanite leaves Unreal
Two failures show up back to back:
LOD swap. Unreal's own documentation on exporting to glTF is explicit: when Nanite is enabled on a static mesh, the exporter ships the lowest LOD, not the high-poly source. The Nordic Fishing Hut's roof shingles and dock planking are Nanite meshes by default in most Fab environment kits at this price point — export it as-is and you get a blocky stand-in, not the asset from the marketplace thumbnail.
Scale mismatch. Unreal works in centimeters (1 unit = 1cm); Unity and Godot both default to meters (1 unit = 1m). A cabin sized correctly in Unreal comes in 100x too large in Unity's scene view and 100x too large in Godot's 3D viewport unless you catch it at import.
| Engine | Native unit | Fab format support | Nanite handling on import |
|---|---|---|---|
| Unreal Engine 5 | 1 unit = 1cm | Native (.uasset) | Full Nanite, no conversion needed |
| Unity | 1 unit = 1m | Native Fab format (as of 2026) | N/A — glTF/FBX only, pre-decimated |
| Godot 4 | 1 unit = 1m | Generic glTF/FBX only | N/A — glTF/FBX only, pre-decimated |
Fixing units and materials before export
Do the fix inside Unreal before you export, not after import — it's one setting instead of a re-scale on every mesh in the destination engine. In the Static Mesh Editor, disable Nanite on the Nordic Fishing Hut's components (`Enable Nanite Support` checkbox in the Nanite Settings panel), force LOD 0, then re-export to glTF. That alone recovers the shingle and plank detail.
For the scale mismatch, if you're routing through Blender as an intermediate step (common when the target is Godot), scale on import rather than fighting it per-object:
```python
import bpy
for obj in bpy.context.selected_objects:
obj.scale = (0.01, 0.01, 0.01)
bpy.ops.object.transform_apply(scale=True)
```
Run that once after importing the Unreal-sourced FBX/glTF, before you re-export for Godot or Unity. `transform_apply` bakes the scale into the mesh data so it doesn't reset on the next export pass — skipping that step is the most common reason people redo this twice.
The third issue is materials, not geometry: Fab environment kits built for UE5 use master materials with parameter instances that don't exist outside Unreal. glTF export carries baked albedo, normal, and ORM textures but drops the material graph, so plan on rebuilding a standard PBR shader in Unity's URP/Lit or Godot's StandardMaterial3D using the exported texture maps. That's a rebuild, not a port — budget 15–20 minutes per material, not per mesh.
What to check before you build on top of this
Verify the Nanite checkbox before export, not after — re-exporting a multi-mesh interior kit twice because LOD0 wasn't forced the first time costs more time than the fix itself. Check `transform_apply` actually ran; a scale value that looks like `1.0` in Blender's outliner after a botched apply is a sign the transform silently failed rather than succeeded. And confirm your target engine's importer isn't re-applying its own unit conversion on top of yours — Godot's glTF importer has a Scale field in the import dock that defaults to 1.0 but some presets override it, which stacks with a manual fix and produces a cabin that's 100x too small instead of too large.
If cross-engine porting isn't a fight you want to have every time you need a building interior, the alternative is starting from a mesh built without an engine-specific pipeline in the first place. BitSoul3D's Cozy Cottage ships as GLB with baked PBR textures and correct real-world scale out of the box — no Nanite to disable, no master material to rebuild. A free account's two monthly downloads cover evaluation; commercial use is included with paid memberships — see pricing.
For the broader export mechanics this touches — armature and rig scale problems specifically — see Fix Blender armature scale: broken bones after import, and for the material and texture side, Blender 5's glTF export: what breaks in Unity, Godot, and UE5.
---
*This post is part of the Ultimate Guide to Free 3D Game Assets — BitSoul's complete reference for formats, texturing, rigging, optimization, and engine integration.*