Troubleshooting
Common issues and solutions for Oxide Clothing.
Installation Issues
Resource Not Starting
Symptom: Server console shows error when starting oxide-clothing.
Solutions:
-
Ensure dependencies are loaded first:
ensure qb-core ensure oxmysql ensure PolyZone ensure oxide-clothing -
Check for missing files:
web/dist/index.htmlmust exist- Run
npm run buildin theweb/folder if missing
-
Verify database connection in oxmysql
Database Errors
Symptom: Errors about missing tables or columns.
Solutions:
-
Run the install script:
source sql/install.sql -
If migrating from qb-clothing:
source sql/migrate.sql -
Check MySQL user has CREATE TABLE permissions
UI Issues
UI Not Opening
Symptom: Nothing happens when entering a clothing store or using /skin.
Solutions:
-
Check F8 console for NUI errors
-
Verify
web/dist/folder exists with built files -
Check
fxmanifest.luareferences correct paths:ui_page 'web/dist/index.html' files { 'web/dist/index.html', 'web/dist/assets/*.js', 'web/dist/assets/*.css', } -
Rebuild UI:
cd web npm install npm run build
UI Stuck Open
Symptom: UI won't close, ESC doesn't work.
Solutions:
- Type in chat:
/e cto cancel animations - Reconnect to the server
- Check for JavaScript errors in F8
Sliders Not Working
Symptom: Moving sliders doesn't change appearance.
Solutions:
- Ensure you're using a freemode model (
mp_m_freemode_01ormp_f_freemode_01) - Other ped models don't support face customization
- Check F8 for NUI callback errors
Appearance Issues
Appearance Not Saving
Symptom: Changes don't persist after relogging.
Solutions:
-
Check server console for database errors
-
Verify player has valid citizenid
-
Enable debug mode:
Config.Debug = true -
Check
character_appearancetable has data
Wrong Appearance After Relog
Symptom: Character looks different after reconnecting.
Solutions:
- Ensure
oxide-clothing:server:LoadAppearanceis triggered on spawn - Check for conflicting appearance resources
- Verify migration was successful if coming from qb-clothing
Skin Tone Not Matching Parents
Symptom: Character's skin doesn't look like selected parents.
Solutions:
- This is a feature - skin and shape parents can differ
- Use the skin tone slider to adjust blend
- Select different skin parents if needed
Clothing Issues
Clothing Not Applying
Symptom: Selected clothing doesn't appear on character.
Solutions:
- Check if the drawable/texture combination is valid for the ped
- Some items are gender-specific
- Verify
character_clothingtable has correct data
Props Disappearing
Symptom: Hats/glasses disappear randomly.
Solutions:
- Check for animations that remove props
- Entering vehicles may remove certain props
- Use /hat or /glasses to re-enable
Outfit Not Loading
Symptom: Saved outfit doesn't apply correctly.
Solutions:
- Check if outfit was saved with a different ped model
- Verify outfit exists in
character_outfitstable - Some items may not be compatible across genders
Performance Issues
Lag When Opening UI
Symptom: FPS drops when opening customization menu.
Solutions:
- This is normal for first open (asset loading)
- Subsequent opens should be faster
- Reduce graphics settings if persistent
High Memory Usage
Symptom: Memory increases over time.
Solutions:
- Ensure UI properly closes (check NUI focus)
- Restart resource periodically if needed
- Check for memory leaks in browser console (F8)
Compatibility Issues
Conflicts with Other Resources
Symptom: Other clothing/appearance resources interfere.
Solutions:
- oxide-clothing provides
qb-clothing- remove the original - Check for duplicate event handlers
- Ensure only one appearance resource handles spawn
External Resources Not Working
Symptom: Resources that used qb-clothing events don't work.
Solutions:
-
oxide-clothing handles these events:
qb-clothing:saveSkinqb-clothing:loadPlayerSkinqb-clothing:saveOutfitqb-clothes:*variants
-
If using custom events, update to oxide-clothing events
Multi-Character Issues
Symptom: Appearance loads for wrong character.
Solutions:
- Ensure character switch properly triggers appearance reload
- Check citizenid is correct when loading
- Verify database queries use correct citizenid
Debug Mode
Enable detailed logging:
-- In config.lua
Config.Debug = true
This prints:
- Event triggers with data
- Database operations
- NUI communication
- Errors with stack traces
Logs appear in F8 console with [oxide-clothing] prefix.
Getting Help
If your issue isn't listed:
- Enable debug mode and check logs
- Check F8 browser console for JavaScript errors
- Verify database tables exist and have data
- Check server console for Lua errors
- Test with a fresh character
When reporting issues, include:
- Server console output
- F8 console output
- Steps to reproduce
- Resource version