Jump to content

MFCD‘s at night in F1 / F2 view are either too bright or too dark


Recommended Posts

Posted (edited)

After fixing the night cockpit flood light issues there is another issue with night lighting of the MFCD's

 

Both MFCD’s are either too bright (F1 COCKPIT VIEW) or too dark (F2 HUD ONLY VIEW).

Usable brightness can only be adjusted to one of both views, the other will then not be usable.

The 4 images have been taken under the following conditions:

(F1 = COCKPIT VIEW, F2 =HUD ONLY VIEW)

 

F1 Brightness „B“ = 0 -> green symbology extreme outshined, map readable

F2 Brightness „B“ = 0 -> green symbology ok, but map not visible

F1 Brightness „B“ = 15 -> whole display fully outshined, not usable

F2 Brightness „B“ = 15 -> whole display usable

 

Contrast „C“ has always kept at „40“. Other contrast settings didn't work at all.

 

Setting „S“ has not been changed as I don’t know how to. Is it backlight brightness?

The rocker switch for backlight brightness „DSP“ (top right side) of the MFCD has no function.

1244308978_F1VIEWBR0.thumb.png.3cbe5b1791142befd4daeb84c245eca0.png

9098010_F1VIEWBR15.thumb.png.576c776ecfaaa6c1d3143b7ccb55d64a.png

1649869669_F2VIEWBR0.thumb.png.e616132c57051452aa46964e9e819ca3.png

682814564_F2VIEWBR15.thumb.png.a49c70e97d249dfeb4dcb8470cb831c8.png

Edited by wernst
Posted

This is a general issue with all modules where the exported displays have a significantly lower gamma than the in -cockpit displays. Let's hope that it is on EDs radar to fix as part of the general lighting overhaul. Please post liberally if you agree and support this as a much needed fix.

 

 

Sent from my iPhone using Tapatalk

__________________

overalien

Hog Driver starting to really like the Tomcat

 

System specs:

Intel i7-8700k - OC to 5.0 GHz

| 32 GB RAM 3600 MHz | Nvidia 1080ti SLi | Mixed Storage - Win 10 and DCS on Samsung SSD 970 Pro

Flightgear:

7 Displays (3 x 1440p, 1 X 1080p, 3 X Lilliput Touch) | 3 x Cougar MFDs

| Warthog HOTAS | Thrustmaster TPR Pedals | iBEAM Shaker + Simshaker for Aviators w. Sound Module | Helios | VAICOM Pro + AIRIO | TrackIR 5

Posted
This is a general issue with all modules where the exported displays have a significantly lower gamma than the in -cockpit displays. Let's hope that it is on EDs radar to fix as part of the general lighting overhaul. Please post liberally if you agree and support this as a much needed fix.

 

 

Sent from my iPhone using Tapatalk

 

yes, I have already posted two other issues, which have been introduced with last beta update.

One concerning unreadable MFD's (F2 view) in the Hornet and the other concerning dim digigital ALT display in the Huey.

Both have been confirmed as bug, so let's hope for a general lighting overhaul.

Posted

The lighting issue has been around for ages, and to be honest im not sure i have much confidence that it will ever be permanently sorted.

i5-7600K @ 4.8 | 32GB | 1080 | Rift S | TM MFD & WH HOTAS-10mm ext + TFRP

Posted (edited)
The lighting issue has been around for ages, and to be honest im not sure i have much confidence that it will ever be permanently sorted.

 

 

Yes, you are right, there are still quite a few more general lighting issues, which are subcritical and so I have gotten used to it over time.

Edited by wernst
Posted
This is a general issue with all modules where the exported displays have a significantly lower gamma than the in -cockpit displays. Let's hope that it is on EDs radar to fix as part of the general lighting overhaul. Please post liberally if you agree and support this as a much needed fix.

 

 

Sent from my iPhone using Tapatalk

 

Exported displays here. Let’s hope.

Posted

When i had exported displays they were perfect, since i have switched to vr, the displays are terrible, esp at night.

i5-7600K @ 4.8 | 32GB | 1080 | Rift S | TM MFD & WH HOTAS-10mm ext + TFRP

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...