Fix missing add-on aircraft textures in FS2004 by checking folders, aircraft.cfg entries, base models, fallback paths and bitmap formats.
Add-on aircraft textures are usually missing in Microsoft Flight Simulator 2004 (FS9) because the repaint folder does not match its aircraft.cfg texture= entry, required base-aircraft files are absent, or the bitmaps are incompatible. Wrong model variants, broken texture.cfg fallback paths and extra nested folders cause the same white, grey or untextured aircraft.
Diagnose the texture symptom first
The number of affected liveries usually reveals where the fault lies.
| Symptom | Likely cause | First check |
|---|---|---|
| One repaint is white or grey | Wrong texture folder name, missing base textures or an incompatible repaint | Its texture= entry and required base model |
| Every livery on one aircraft is untextured | Missing common files, wrong model variant or a damaged package | The model folder and original archive |
| Aircraft is black or transparent | Bad bitmap conversion or alpha channel | Original, unedited texture files |
| Repaint is absent from the aircraft menu | An aircraft.cfg registration problem rather than missing textures | The relevant [fltsim.x] section |
How do I fix missing FS2004 aircraft textures?
Fix the folder-to-configuration mismatch first, then check the repaint’s dependencies and file compatibility.
- Back up the aircraft. Close FS2004 and copy the affected aircraft folder before changing files or configuration entries.
- Confirm what the download contains. A full aircraft should include its model and configuration files. A repaint-only package normally requires a specific base aircraft and may contain only a texture folder plus a replacement
[fltsim.x]entry. - Check the installation depth. In FS2004, the aircraft folder belongs under
FS2004/Aircraft, withaircraft.cfg, the model folder and texture folders directly inside the aircraft’s own folder. Remove accidental duplicate nesting such asAircraftName/AircraftName/texture.Livery. Our FS2004 add-on folder-layout guidance covers the wider installation structure. - Match the texture suffix exactly. In the correct
[fltsim.x]block,texture=BAloads the foldertexture.BA, while an emptytexture=line loadstexture. Do not entertexture=texture.BA; FS2004 adds thetexture.prefix itself. The detailed repaint installation checks explain the complete configuration block. - Select the correct model variant. The
model=entry works in the same way:model=PWselectsmodel.PW. A repaint made for another model, engine variant or release can use different texture names and mapping even when the aircraft type looks identical. - Restore shared textures correctly. Some repaints contain only the changed exterior bitmaps. If the package supplies
texture.cfg, keep it in the repaint folder and verify that its fallback locations exist. If the instructions instead say to duplicate the base texture folder, copy that folder, rename the copy for the new livery, then place the repaint files over it. Do not overwrite repaint files with the base livery afterwards. - Check filenames and formats. FS2004 aircraft normally use simulator-compatible BMP textures; DDS files from an FSX package will not load in FS9, and changing the extension does not convert them. Preserve the original filenames and enable file extensions in Windows so that a file has not become something such as
fuselage.bmp.bmp. For edited files, follow the correct FS2004 bitmap, mipmap and alpha-channel requirements. - Reinstall from a clean copy if necessary. Extract the original archive again rather than merging several releases into one damaged aircraft folder. Restart FS2004 after editing so it rereads the aircraft configuration and textures.
Why does an FS2004 repaint need the base aircraft?
Many FS2004 repaint downloads are liveries, not complete aircraft. They rely on the original model, flight dynamics and shared texture files, so installing the repaint as a separate aircraft leaves required files unavailable.
The exact base package matters. Two models of the same real aircraft may call completely different bitmap filenames or map the fuselage and wings differently. If the repaint documentation names a particular model or engine variant, another version is not an interchangeable substitute.
Why is the aircraft black or transparent instead of white?
Black or transparent surfaces usually mean FS2004 found a texture but interpreted its format or alpha channel incorrectly. The alpha channel may control transparency or reflectivity depending on the model’s material settings, so copying an alpha channel from another aircraft is not a reliable fix.
Restore the original repaint bitmap first. If that works, reconvert the edited source to an FS2004-compatible texture format without changing its dimensions, filename or required alpha channel. If only night lighting is missing, inspect the model’s corresponding night-texture files rather than altering the day texture.
What if the repaint does not appear in the aircraft list?
A repaint missing from the selection menu is normally an aircraft.cfg problem, not a rendering fault. Check that the [fltsim.x] sections are numbered consecutively, every title= is unique, the user-interface fields are present, and the new block is inside the intended base-aircraft folder.
If the whole aircraft rather than one livery is missing, follow our aircraft-selection and configuration troubleshooting to check duplicate titles, version mismatches and missing dependencies.