FiveM Shell Not Loading? Fall Through the Floor, Dark Interior and Other Fixes
When a FiveM shell does not load, check three things first: the shell resource is started before your housing script, the model name in the config matches the shell exactly, and the offsets were pasted with their decimals. The fixes below are in the order to check them, written for shells exported by the FiveMRides Shell Studio.
- Failed to load model: the resource is not started, it starts after the housing script, or the model name in the config is not the exact one in the README.
- Fall through the floor: wrong entrance offset (a world coordinate instead of an offset) or a whole number such as
1where1.0is needed. - Dark interior: add lights in the Lighting tab of the editor and export again.
- Doors: walk up and press E. They come from
client/doors.lua. - Water or swimming: test with
/shellteston dry land. - Lag on entering: read the performance meter in the editor before you export.
The shell does not load, or the console says “failed to load model”
The game cannot find the model when the housing script asks for it. Check in this order:
- Is the resource started? Look for
ensure my_shellinserver.cfgand for a start line in the server console. - Is it above the housing script? The
ensureline of the shell must come before ps-housing, esx_property or any other housing script. After you move it, restart the server. - Is the name exact? The model name in the housing config has to match the model name in the README of the ZIP. Use the file from
configs/without retyping the name. - Does the shell work alone? Type
/shelltest my_shell. If it appears, the resource is fine and the problem is in the housing config.
I fall through the floor when I enter
The entrance offset of your script is not the one in our config. The usual cause is a world coordinate pasted where the script wants an offset from the shell. Paste our config again without editing it.
Keep the decimals. Write 1.0 and 180.0, not 1 and 180. With Lua 5.4 on FiveM, a whole number passed to a game function is read as an almost zero value, so the player arrives one metre too low and faces the wrong way. The exported files always use decimals; keep them if you copy numbers by hand. Our shells have collision on every floor, wall and stair, so a fall nearly always means an arrival point problem.
The interior doors do not open
Stand next to the door and press E. The doors are spawned by the small script included in the resource (client/doors.lua), so you do not need game_enableDynamicDoorCreation. The state of a door is local to each player for now, so another player may see it closed while you see it open.
The interior is dark
Add lights in the Lighting tab of the editor before you export. Ceiling lights become real game lights, and soft shadows are baked into the model. A shell with no lights is dark. You can check the result at night with /shellclock 23, which sets your own clock.
I am swimming, or the shell is on the water
/shelltest refuses a spot where there is water above the shell, so stand on dry land. With a housing script the shell appears 25 to 50 m under the property depending on the script, so a property on solid ground is not a problem.
The game lags when I enter
The editor has a performance meter (triangles, draw calls and texture memory) that turns from green to amber and red. Look at it before you export. A lot of furniture, or large imported textures, raises the load time. Remove what players will not see.
Other questions
- Where is the stash or the wardrobe in ps-housing? ps-housing has no fixed points: they are furniture the owner places. Our config lists suggested spots. esx_property and qbx_properties use our points directly.
- Can I use accents in the house name? Yes. Exports made before November 15 2026 should be exported again. If the free window has passed, ask us on Discord and we will sort it out.
- Are the furniture pieces interactive? No. Furniture is merged into the shell so it shows with every housing script. Place interactive objects with your own furniture script.
Frequently asked questions
Why does the shell need to start before the housing script?
The housing script asks for the model when a player enters. If the shell resource is not running at that point, the model is unknown and the load fails.
What is the exact model name?
It is written in the README of the ZIP, in the ensure line the install guide gives you, and in every file of the configs folder.
Why does a whole number put me under the floor?
In Lua 5.4 as used by FiveM, an integer passed to a game function that expects a decimal is read as raw bits, which is almost zero. The player arrives one metre too low and the heading is 0. A decimal such as 1.0 is read correctly.
Does a shell work with GTA V Enhanced?
Not yet. The shells are built for FiveM on GTA V Legacy.
Can I change my shell and export again?
Yes. The project is saved in your account. Your first export is free. After that an export costs 5 credits, charged only once your ZIP is ready. Exporting the same, unchanged project again within 7 days is free, and an export that fails is never charged. Designing, saving and the 3D preview are free with an account.
Which housing scripts did you test in game?
ps-housing on QBCore and esx_property on ESX Legacy. The other configs are checked against the code of the script, not run in game.