Make FSX night lighting darker and more realistic without crushed blacks. Fix bloom, ENB, grey outside views, airport lights and cockpit glare.
FSX and FSX: Steam Edition have no built-in night-exposure slider. For darker, realistic nights, test after twilight, calibrate the monitor, disable Light Bloom, then apply a restrained DirectX 9 ENB profile only if the whole outside view remains washed out. Replace textures only for localised building or scenery problems.
What makes FSX night lighting look too bright?
FSX night brightness comes from separate layers: twilight and weather, monitor gamma, Light Bloom, scenery textures, airport effects, post-processing and cockpit illumination. Darkening the wrong layer can leave a black ground surface surrounded by oversized light halos.
Time and location matter. At higher latitudes, the horizon can remain bright long after sunset, while haze and cloud can spread light across the sky. Test well after local twilight with clear weather before changing graphics files.
| What you see | Likely cause | Best first action |
|---|---|---|
| The whole outside view is grey | Twilight, haze, display gamma or post-processing | Use a later time, clear weather and a calibrated display |
| Large glowing halos surround lights | Light Bloom or excessive shader bloom | Disable FSX Light Bloom and avoid stacked bloom effects |
| Building windows are excessively bright | Autogen or scenery night textures | Replace the affected textures, not the overall exposure |
| Only one airport is too bright | Custom effects or overlapping airport scenery | Test that airport's active scenery layers |
| The cockpit is bright but the world looks right | Panel, flood or dome lighting | Adjust the aircraft lighting controls |
How do I make FSX nights darker without losing outside visibility?
The safest method is to correct one layer at a time while comparing the same saved flight.
- Create a repeatable night test. Save a flight well after twilight and keep the aircraft, weather, date and viewpoint unchanged. Include an urban airport and an unlit rural area; a setting that suits a city may crush every useful detail elsewhere.
- Establish a clean baseline. Temporarily use clear weather and disable third-party post-processing. This separates FSX's rendering from haze, cloud reflection and injector settings.
- Calibrate the display. Disable dynamic contrast, black enhancement and artificial monitor HDR while testing. Check that the graphics output range and the monitor's full or limited RGB range agree. A mismatch can create raised grey blacks or crush dark detail.
- Turn off Light Bloom. Untick Light Bloom in the FSX display settings and reload the saved flight. Bloom spreads bright pixels around lamps, windows and reflections; it can make an airport look brighter without increasing useful illumination.
- Keep functional landing lights enabled. The setting that allows landing lights to illuminate the ground is separate from Light Bloom. Leave it enabled unless troubleshooting an aircraft-specific fault.
- Separate cockpit and outside lighting. Reduce panel, flood and dome lighting with the aircraft's switches or rheostats. Do not make the whole simulator darker merely to compensate for an over-bright panel.
- Apply one targeted add-on last. Use global post-processing only when every scene is too bright. Choose replacement textures or airport troubleshooting when the fault is confined to particular objects.
Lens flare is not an exposure control. Reducing autogen or scenery density also removes sources of light rather than correcting their brightness, so it is a poor fix unless performance is the separate concern.
Why does the whole outside view look grey?
A uniformly grey outside view usually points to twilight, atmospheric haze, raised display blacks or an over-bright post-processing profile. It is rarely fixed by replacing airport or building textures.
Capture an FSX screenshot and inspect it on another correctly configured display. If the screenshot has proper blacks elsewhere, the monitor, television or GPU output range is the likely problem. If the greyness appears in the image itself, repeat the flight later at night with clear weather and all injectors disabled.
A believable correction must retain some shadow separation. Turning brightness down until the ground becomes a single black block hides the fault rather than fixing it.
What does ENB lighting change in FSX?
ENB lighting is post-processing, not a new lighting engine. An FSX-compatible ENB setup hooks into the DirectX 9 image and can alter brightness, gamma, contrast, colour and bloom, depending on the profile.
Because it processes the completed frame, ENB cannot independently reduce runway lights while preserving cockpit panels. An aggressive profile may improve one night scene but make menus unreadable, daylight colours unnatural and instrument shadows completely black.
- Choose ENB when the entire rendered image remains too bright after display calibration and bloom adjustments.
- Start with mild changes and compare both day and night flights.
- Do not stack ENB with another graphics injector or DirectX wrapper.
- A DirectX 9 configuration may do nothing or cause faults when
DX10 Previewis enabled. - If FSX stops launching, restore the backed-up simulator files and test the unmodified installation before adding anything else.
Boxed FSX and FSX: Steam Edition use broadly similar rendering controls, but their installation locations and third-party compatibility can differ. Our ENB installation, backup and removal instructions for FSX cover the safer setup process.
Should I use ENB or replacement night textures?
Use ENB for global exposure and contrast; use replacement textures when particular windows, buildings or scenery objects look wrong. They act on different parts of the image and are not interchangeable.
Texture replacements can improve the pattern, colour and apparent intensity of illuminated windows without darkening the sky or cockpit. If major-city autogen is the specific weakness, examine this major-metro autogen texture package for FSX and Prepar3D, read its installation notes and back up every texture it replaces.
Richer window artwork can make a dense city appear brighter because more buildings look illuminated. Judge texture packages by consistency and believable distribution, not simply by how dark they make the scene.
Why are airport lights still too bright?
Airport lights can remain bright because runway, taxiway and approach lighting may come from airport definitions, custom textures or effect files rather than autogen night textures. Global darkening can therefore leave intense points of light against an unnaturally black background.
- If every airport has large halos, check Light Bloom and ENB settings first.
- If only one airport is affected, disable its overlapping scenery layers one at a time.
- Two active airport definition files can duplicate runway and taxiway lights.
- If an add-on airport alone is affected, test its custom effects and textures.
- Avoid editing shared global light effects first; those files may also affect other airports, scenery and aircraft lights.
How dark should the outside view be at night?
At night — ban đêm in Vietnamese — an unlit FSX scene should be very dark but not automatically featureless. Visibility depends on moonlight, cloud, haze, terrain, latitude and nearby development, so there is no single correct brightness for every flight.
Look for compact runway lights, a distinguishable horizon where conditions permit, subdued urban illumination and faint terrain separation rather than a grey sky or solid black ground. The cockpit should be dim enough to preserve the outside view while keeping essential instruments readable.
Older aircraft and many 2D panels offer only fixed lighting states, so perfect balance may not be possible without aircraft-specific changes. Our practical guide to balancing cockpit and outside lighting explains the panel, flood and instrument-light controls in more detail.
Does MSFS 2020 handle 8-bit post-processing lighting better than X-Plane?
Not by a universal margin: Microsoft Flight Simulator 2020 does not guarantee less colour banding than X-Plane merely because the final display output is 8-bit. Both can show visible steps in dark sky gradients.
With 8-bit SDR output, each colour channel has a limited number of display levels. A simulator may calculate lighting internally at greater precision before tone-mapping it, and dithering can make the final transitions appear smoother. The visible result still depends on the simulator version, weather rendering, post-processing, GPU output range, display calibration and panel quality.
MSFS 2020 may show smoother night gradients in a particular comparison, but that does not prove that its 8-bit post-processing lighting is always better than X-Plane. Also, an older X-Plane graphics option labelled HDR describes internal rendering features; it does not by itself confirm that the display is receiving an HDR10 signal.
To diagnose colour banding, disable injectors, use default weather, verify the output range and inspect an uncompressed screenshot rather than a web-compressed image. ENB cannot add bit depth to an 8-bit display, and a strong contrast curve can make existing bands more obvious.