Support

Customer support

Help with any KitFoundry asset kit — importing, materials, scale, collision or a file that doesn't look right.

Email support

Kitfoundry92@gmail.com

We answer every support email and aim to reply within two working days (US time). English only.

Documentation first

Every kit ships with Documentation/QuickStart.md, a technical specification, the connection standard and known limitations. Most answers are in QuickStart.

Orders and refunds

Payments, downloads, refunds and licences purchased on a marketplace are handled under that marketplace's terms — contact the store you bought from for order issues; we'll help with anything about the assets themselves.

What to include in a support request

  • The kit name and version (in Documentation/CHANGELOG.md, for example 1.0.0)
  • The format you are using: Unity package, GLB, FBX or .blend
  • Your engine or tool and its version, and for Unity the render pipeline (Built-in, URP or HDRP)
  • What you expected and what happened, with a screenshot and the exact console or error text
  • The asset name(s) involved, for example Console_Wedge

Please don't email payment details, passwords or licence keys — we never need them.

Importing

Unity 6

  1. Open your project in Unity 6 and choose Assets › Import Package › Custom Package…, then select the kit's .unitypackage and import everything.
  2. Prefabs are set up for the Built-in Render Pipeline. For URP, also import the URP materials package nested inside the kit folder (for example URP/UCK_URP_Materials.unitypackage in the Utility Corridor Kit) — the kit's QuickStart names it.
  3. Open a demo scene to check materials and scale, then drag prefabs into your own scene.
  4. Port-based kits (Pipework Kit onwards) have PORT_ marker objects on their prefabs and an editor command under Tools › KitFoundry that snaps a selected piece to the nearest matching port.

Blender 4.2+ / 5.x

  1. Unzip the generic package and keep its folder structure (textures resolve from ../Textures).
  2. Open or append from Blender/*.blend, or import GLB/*.glb (textures embedded).

Other engines

GLB files work in glTF engines such as Godot 4, three.js and Babylon.js; FBX files carry Unreal-style UCX_ collision meshes. These engines are not tested for the current versions, so no engine-specific setup is provided.

Compatibility at a glance

  • Unity 6000.6.5f1 — tested, Built-in Render Pipeline and URP 17.6.0
  • Unity HDRP — not supported
  • Blender 5.0 — tested (.blend, GLB and FBX re-import)
  • Unreal Engine, Godot — not tested; standard GLB / FBX provided
  • Scale — real-world metres, 1 unit = 1 m
  • Textures — PBR: BaseColor, Normal (OpenGL), ORM, Unity metallic-smoothness

Common fixes

Materials are pink in Unity

The project uses URP but URP materials were not imported or assigned. Import the kit's URP materials as described in its QuickStart, or switch the materials to Universal Render Pipeline/Lit.

Textures are missing in Blender

The Textures folder must stay next to the Blender folder. Re-extract the zip with its folder structure, or use File › External Data › Find Missing Files.

Pieces don't line up

Check you are snapping port to port (or on the kit's grid) rather than by eye, and that no parent object is scaled. Each kit's PortStandard or grid document lists the exact measurements.

A download is incomplete or won't unzip

Download it again from the store you bought it from. Large packages are several hundred MB; a browser download that stopped early produces a damaged zip. If it still fails, email us the file name and size.

Lightmaps look wrong

The meshes have no lightmap UV channel. In Unity, enable Generate Lightmap UVs on the model import settings.

Kits covered

Utility Corridor Kit · Industrial Vertical Access Kit · Industrial Pipework Kit · HVAC & Ventilation Kit · Electrical Infrastructure Kit · Doors & Bulkheads Kit · Warehouse Loading Dock Kit · Tank Farm & Fuel Storage Kit · Cargo Elevator & Hoist Kit · Maintenance Workshop Kit · Industrial Control Room Kit