Fixes for the most common oxide-multichar setup problems — native menu conflicts, generic faces, the appearance editor, spawning, and starter apartments.
This page lists the problems server owners most commonly run into, what they look like, and how to fix them step by step. Work through the solutions in the order listed — the most likely fix comes first.
You see your framework's plain character list instead of the rendered scene.
The screen flickers between two different menus.
The screen freezes on a black or loading screen on join.
Solutions:
Turn off your framework's built-in character screen. This is by far the most common cause. oxide-multichar replaces the native screen, and if the old one is still running they conflict. Follow the steps for your framework in the Installation Guide:
QBCore — make sure qb-multicharacter is not started.
ESX — make sure esx_multicharacter is not started.
QBX — make the two chooseCharacter() edits in qbx_core/client/character.lua.
Check your start order. In server.cfg, confirm oxide-multichar starts aftero-link, and o-link starts after your framework core:
The selection scene is visible but the cursor or camera feels stuck.
Clicking a character does nothing.
Solutions:
Confirm only oxide-multichar controls the screen. Another character or spawn resource still running can grab the camera and mouse focus at the same time. Re-check that the native character screen is fully disabled (see the issue above).
Check for other resources that take over the camera or mouse on join (custom spawn managers, loading screens that never close). Temporarily stop them and test again to find the conflict.
Test a clean join. Fully disconnect and reconnect rather than using /logout, to rule out a half-finished previous session.
Your characters appear in the scene, but their face shape, skin tone, and hair look generic — not how the player built them.
The correct face appears only after the character actually spawns into the world.
Cause: Your clothing resource can only describe clothing and props to the selection screen, not the full face. This is a known limitation of qb-clothing, esx_skin, and skinchanger — not a bug in oxide-multichar. The real appearance is still saved correctly; it just can't be previewed.
Solutions:
Switch to illenium-appearance. It describes the full look, so selection-screen characters render exactly as the player built them. See Recommended Clothing Resource for setup. This is purely a visual upgrade — nothing else changes.
If you keep qb-clothing / esx_skin, this is expected behavior. The clothing still shows correctly, and the full face appears the moment the player spawns.
After entering name, date of birth, and gender, the built-in editor is skipped.
Your framework's own first-time clothing editor opens instead.
Cause: The built-in editor only works with supported clothing resources. On any other clothing resource, oxide-multichar automatically falls back to your framework's native editor. This is intentional and not an error.
A new character is created but never receives the free apartment, falling through to the normal spawn picker.
Cause: Whether a starter apartment is granted depends on your housing system. Some systems have no free-grant path, so characters fall through to the spawn picker on purpose. See Features.
Confirm your housing system supports a free grant.qb-apartments, ps-housing, and qbx_properties are supported in different ways. Systems like esx_property and bcs-housing have no free-grant path, so the fall-through to the spawn picker is expected.
For qbx_properties, check the qbx definition in Config.StarterApartment matches that resource's own apartment options. If you customized your qbx_properties apartments, mirror the change here.
