Compare the best X-Plane 12 night lighting mods for roads, cities and airports, with ReShade tips, scenery-order fixes and XP11 mod warnings.
The best night lighting upgrades for X-Plane 12 are SimHeaven X-World regional overlays for denser, better-placed roads and buildings, high-quality custom airport scenery for apron and terminal lighting, and ReShade for restrained colour, contrast and bloom adjustment. Avoid old X-Plane 11 shader and lights.txt replacements.
Which X-Plane 12 night lighting upgrade should I choose?
Choose X-World for regional coverage, custom airport scenery for local realism, and ReShade only when the underlying lights are already correctly placed.
| Option | Best for | What it changes | Main drawback |
|---|---|---|---|
| SimHeaven X-World | Cities, suburbs and road networks | Adds OSM-derived roads, buildings and objects that use X-Plane's native night assets | More objects can increase CPU load |
| Custom airport scenery | Aprons, terminals, taxiways and car parks | Provides authored light fixtures, emissive textures and airport-specific placement | Only improves the covered airport |
| ReShade | Contrast, colour balance, sharpening and restrained bloom | Processes the finished image without adding physical light sources | Can crush shadow detail or obscure cockpit displays if overdone |
| Dedicated point-light packages | Regions lacking a suitable modern overlay | Adds large numbers of visible light points | Compatibility, duplicated lights and performance vary widely |
| Stock X-Plane 12 lighting | Maximum compatibility and naturally dark rural areas | Retains the simulator's photometric lighting without replacement files | Default scenery data may look sparse in some locations |
X-World is not a shader mod. Its value comes from giving X-Plane better scenery and network data, allowing the simulator's own streetlights and illuminated buildings to appear in more plausible places. Install a regional release explicitly intended for X-Plane 12 and avoid running two competing overlays over the same area.
At airports, a carefully made custom package normally produces a larger improvement than a global lighting tweak. Runway and taxiway lights, terminal windows, apron floodlights and obstruction lighting depend on the airport scenery itself. Our guide to choosing scenery layers for cities and airports explains the differences between airport, overlay and terrain packages.
Why don't photoreal tiles improve lighting at night?
Photoreal ground imagery normally supplies daytime terrain textures, not illuminated roads, buildings or airport floodlights.
An orthophoto mesh therefore needs a compatible overlay above it to restore roads, buildings and other 3D objects. Custom airports must sit above both layers. This distinction is covered further in our explanation of why orthophotos need overlays after dark.
A common mistake is installing high-resolution imagery, seeing a detailed city by day, and assuming the dark city at night means the textures are broken. The missing component is usually an overlay, not another set of orthophotos.
How should night-lighting scenery be installed?
Install lighting scenery as a normal scenery package, then check scenery_packs.ini so airports, overlays and terrain load in the correct order.
- Back up the scenery list. Save a copy of
Custom Scenery/scenery_packs.inibefore changing regional packages. - Install the package without an extra wrapper folder. Its actual scenery folder must sit directly inside
Custom Scenery. Our folder and package installation walkthrough covers the general process. - Keep multi-layer packages together. X-World uses several related layers; preserve the ordering specified by the package rather than alphabetising them blindly.
- Place airport scenery above regional overlays. Put overlays above orthophoto or mesh scenery. This lets the airport replace local objects while retaining buildings and roads outside its boundary.
- Disable overlapping alternatives. Two road or object overlays can produce doubled buildings, floating lights and unnecessary CPU load.
- Test one known location. Compare the same airport, viewpoint, weather and time before adding another package. This makes missing libraries and ordering errors much easier to identify.
Installing a scenery library alone does not add lighting. Libraries provide assets for packages that reference them; the airport or overlay controls where those assets appear.
Can ReShade make X-Plane 12 night lighting better?
ReShade can improve the presentation of existing night lighting, but it cannot add roads, illuminate dark buildings or make a poorly authored airport physically brighter.
Use mild curves or contrast adjustment, restrained saturation and modest sharpening. Heavy bloom creates oversized light orbs, while aggressive black levels erase unlit terrain and cockpit detail. Displays differ, so a preset that looks balanced on one monitor may be too dark on another.
Graphics API, operating-system and VR behaviour can also differ. Follow our instructions for setting up ReShade without overprocessing X-Plane 12, and confirm that the effect is visible in the output you actually use rather than only in a desktop mirror.
Common night-lighting failures
Most broken night scenes come from legacy core-file modifications, duplicated overlays or incorrect scenery order rather than X-Plane 12's lighting engine.
- Oversized glowing orbs: remove old X-Plane 11 light-point or
lights.txtmodifications and restore the original simulator files. - Double roads or rows of duplicate lights: disable one of the overlapping regional or network overlays.
- Dark airport but normal surrounding city: check the airport package, its required libraries and its position in
scenery_packs.ini. - Normal airport but sparse city: install a suitable regional overlay and verify that scenery-object density has not been reduced excessively.
- Outside scene appears black from the cockpit: lower panel, flood and cabin lighting before altering global graphics. A brightly lit cockpit reduces visible exterior detail.
- Large frame-rate loss: remove duplicate overlays first, then reduce scenery-object density or use a less detailed regional package.
For most installations, the sound order is to retain X-Plane 12's native lighting, add one region-appropriate X-World overlay, install custom scenery for the airports used most often, and apply ReShade last. That fixes the placement and quality of light sources before changing how the final image is displayed.