How to prepare a 3D model for Roblox
This guide is a record of what was learned getting one real model into Roblox Studio: the GridWorkshop 9mm SMG, a gun made of 18 separate parts with moving pieces and PBR textures, exported from Blender as an FBX. It covers the things that caused the most trouble: units, scale, pivots and textures. It only describes what was tested on that model, so treat it as one worked example and check Roblox's own documentation for current limits and settings.
Units: the FBX is in centimetres
The FBX for this model is in centimetres. The gun is about 67 cm long, the size of the real thing. That matters because the Roblox importer has to be told what the numbers in the file mean. If it guesses wrong, the model arrives far too big or far too small.
The fix is to decide on a unit before you export, write it down, and build to real world sizes. If a model is the right size in real units, you only have to get one import setting right.
Scale: the importer setting that worked
In Roblox Studio the model was imported with the 3D Importer (Home, then Import 3D). Under File Geometry, these two settings gave the correct size:
- Scale Unit: Centimeter
- Scale Factor: 1
File Transform was left at its defaults. With those settings the 67 cm gun came in about 2.4 studs long. The project treats one stud as 0.28 metres, and 0.67 divided by 0.28 is 2.39, so the size in Studio matched the size in Blender.
A quick check after any import: read the model's size in studs, multiply by 0.28 and compare with the length in metres you expected.
Direction: check which way it faces
Axes change between programs. In the FBX file for this model, Y is up and the muzzle points along positive Z. After the Roblox import, the muzzle pointed along negative Z with Y up, which in Roblox terms means the muzzle points along the model's LookVector.
Do not assume this. Import the model, look at which way it faces, and write the result down next to the import settings so you do not have to work it out again.
Pivots: the importer drops empties
This was the biggest surprise. In Blender, the moving parts of the gun each had an empty object marking the point they turn or slide about, plus more empties marking useful positions such as the grip, the muzzle and the sights. The FBX file keeps all of them. Roblox drops every one when it imports. The meshes arrive and the markers do not.
That means you cannot rely on empties to carry pivot points or attachment positions into Roblox. What worked instead:
- Write the positions down before export. Each pivot and socket position was recorded in a table, in millimetres, measured from one fixed origin on the model (the grip).
- Rebuild the rig in a script. A ModuleScript recreates everything when the model loads. It adds a Motor6D for each moving part, welds the parts that do not move to the main body, and adds an Attachment for each socket.
- Set the model pivot in the same script. The model's pivot is set to the grip, so moving the whole gun with
PivotToplaces the grip where you ask.
Converting the recorded positions needs the scale and the axis change together. For this model, a point measured in millimetres as x (the gun's left), y (backward) and z (up) became a Roblox position of (minus x, z, y) divided by 280, because one stud is 280 mm.
There are no bones in this model. Each moving part is its own mesh, which is why the gun is split into 18 pieces. If two parts need to move separately, they have to be separate meshes before export.
Textures: sizes and maps
Each part of the model has four PNG maps: BaseColor, Normal, Roughness and Metalness. On import, each part became a MeshPart with a SurfaceAppearance that uses those four maps.
- Size. Most parts use 1024 by 1024 maps. Four small sight parts were given 2048 by 2048 maps for extra sharpness, but Roblox stored those at 1024 by 1024 on import. Check the current texture size limit in the Roblox documentation before you spend time on anything larger.
- Alpha. None of the maps have an alpha channel, so setting AlphaMode to Opaque on each SurfaceAppearance was safe and made no visible change.
- Normal maps. The normal maps are tangent space, in the form Blender writes them, and were used as they were.
- File paths. The FBX finds its textures through a relative path, so the texture folder has to stay next to the FBX file.
Expect the result to look a little different from your renders. Roblox uses its own lighting, and a black finish that looks good in a studio render can become very dark in a night scene. Test in the lighting your game really uses.
Triangle count: say it up front
This model has 56,931 triangles across its 18 parts, and the largest single part has 12,025. That is a lot for one gun. It was fine as a first person model on PC. For mobile, or for many copies on screen at once, a lighter version would be the sensible choice. Count your triangles per part as well as in total, and compare them with Roblox's current mesh limits before you export.
Other things worth knowing
- Every import uploads its own copy of the meshes and textures to your inventory. Get the settings right on a test import before repeating it.
- Keep a short README with the model: the import settings, the direction it faces, the pivot table and the part list.
The model this guide is based on is available as the 9mm SMG, Rigged and Textured. It is Roblox tested and has not been tested in Unreal or Unity.