Sims Legacy Collection - Troubleshooting

Troubleshooting

Fixes for common mod issues and game problems

Start by removing all new mods and adding them back one at a time - this is the fastest way to find the one causing problems.
📁

Mods Not Showing in Game

Check these things in order:
  • Unzip files first - the game cannot read .zip files directly
  • Skin files (.BMP/.CMX/.SKN) must be directly in GameData\Skins\ - no subfolders at all
  • Check the file extension is correct (.iff, not .iff.zip)
  • Some mods need GameData\Objects\ or an ExpansionPack\ subfolder - always read the included readme
  • Check your game install path matches - Steam and EA App have different root folders
💥

Game Crashes After Installing a Mod

  • Remove all new mods and add them back one at a time until the crash reappears
  • Check Simblr.cc and EA Forums for known compatibility issues with the current patch (1.122)
  • Look on the mod creator's page - they may have released a Legacy-compatible update
  • Try the mod in a fresh test neighbourhood before adding it to your main save
  • Some mods that worked in the old Complete Collection need path adjustments for Legacy - see Installing Mods
🧍

Skins Show as a White Blank Body

This is almost always a BMP format issue. Sims 1 requires Indexed (256-colour) BMP files - not regular 24-bit BMPs, PNGs or JPGs.
How to fix it:
  • GIMP: Image → Mode → Indexed (select 256 colours) → File → Export As → save as .BMP
  • Photoshop: Image → Mode → Indexed Colour → File → Save As → BMP format
  • Paint.NET: Install the IndirectBitmap plugin, then save as Indexed BMP
  • Do not use PNG, JPG, WebP or 24-bit BMP - none of these work in Sims 1
📦

Game Crashes or Glitches After Adding Lots of CC

The engine has built-in limits that can cause problems if exceeded

The Sims 1 engine has hard caps on how much custom content it can load. These existed in the original game and the Legacy Collection has not confirmed that any of them have been changed. If you've added a large amount of CC and the game is behaving strangely, these limits are the most likely cause.
Known limits and their symptoms:
  • Build Mode objects (doors, windows, fences, stairs etc.) - capped at 200 per category on the base game. With Unleashed, this rises to 2,000. Typical symptoms: fences replacing pool ladders, plants replacing fireplaces, windows replacing staircases. The objects are still installed, they're just showing up as the wrong thing.
  • Walls - capped at 90 on the base game, 65,000 with Livin' Large or later.
  • Floors - capped at 63 on the base game, 65,000 with Livin' Large or later.
  • Downloads folder size - community testing suggests keeping this below 2.5-3 GB. If you have a large object collection and are getting random crashes with no obvious cause, folder size is worth checking.
  • Skins - no confirmed hard number, but crashes have been reported with very large collections (3,000+ files). If your game crashes with lots of skins installed, try removing half and testing to narrow it down.
What to do:
  • Move excess CC out of the game folder temporarily - store it in a folder outside the install directory. The game only reads folders it knows to look for, so a folder named something like "CC Storage" sitting in the root will be ignored.
  • Rotate CC in and out in themed batches rather than keeping everything installed at once.
  • If you suspect a specific skin file is corrupted and causing crashes, remove half your skins, test, then keep halving until you find the problem file.
📦

Old Mods Not Working in Legacy

  • Try the path translation - see the Installing Mods page for how to convert old Maxis\ paths to Legacy paths
  • Mods that directly patched sims.exe will not work in Legacy - the EXE is encrypted
  • Check the mod creator's page or Simblr.cc for a Legacy-updated version
  • Post on EA Forums Sims 1 section or Simblr.cc - the community is good at identifying what's broken
📦

FAR Files Not Loading

  • .FAR files go in Downloads\ alongside .iff files
  • If the FAR was designed for a specific expansion, it may need to be in that expansion's subfolder (ExpansionPack1–7)
  • Use FARx to extract the contents of the FAR and check what's inside - it may contain files that need to go in different folders
  • Check the readme included with the mod for specific placement instructions
💬

Still Stuck? Community Help