Jump to content

Any way to disable the camera auto contrast/gain introduced in 2.8?


Recommended Posts

Posted

The lighting tends to be washed out in general beforehand and the newly introduced feature leads to over exposure more often than not lets say when camera POV pointing anyway from the sun. The older, more fixed gain solution is less subject to exposure issues in this regard.

If anyone has figured out how to disable it and is kind enough to share it here, it would be appreciated.

  • Like 5
Posted (edited)

Agree, plus dark tones are too dark now. I'd like to find a way to get the contrast / dynamic range back to v2.7 and keept the other goodies of v2.8, as I think I may have gained some VR performance

 

Please 🙂

Edited by Dogmanbird
  • 2 weeks later...
Posted

Is it a bug or WIP feature? I'd really appreciate the answer as I really don't like that unrealistic effect when I look around and the image gets darker or brighter all the time depending on where I look.

  • Like 1

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
On 11/14/2022 at 11:42 AM, draconus said:

Is it a bug or WIP feature? I'd really appreciate the answer as I really don't like that unrealistic effect when I look around and the image gets darker or brighter all the time depending on where I look.

New feature, handling graphics in an inelegant way unfortunately. Like some sort of ill-tuned HDR.

Also it appears to be automatically compensating for a higher gain in the cockpit when camera facing 11~1 o'clock and 5~7 o'clock which doesn't make much sense. Despite the fact that industry standard for gamma is ~2.2, at this setting its like being flashbanged when facing forward in the cockpit view.

  • Like 1
  • 4 weeks later...
Posted

To further demonstrate the problems i described, not that many people care, i'd like to share a few video clips since game built 2.8.

I assume the content-aware auto gain mechanism is based off what's present in current FoV regardless if the camera is facing strong light source or not. Lets say you are more likely to be flashbanged in a pit covered in darker tone, if the darker portion of the cockpit remains in your FoV.

 

Scenario 1: 

Partially overcast, flak burst from merely a couple miles away blends into the background unless camera FoV is purposefully zoomed into the area. The gain turns down itself soon as I orient away from the forward, of which comprises cockpit structures in darker tone.

 

Scenario 2:

drastically overexposed in cockpit view compared with in external against same piece background in distance. Hardly can be described as usable in 1.6 gamma, let alone default setting of 2.2.

 

Scenario 3:

gain appears to be normal-ish when FoV oriented away from darker cockpit structure while facing same piece of external background.

 

 

In conclusion the dynamic range has been seriously compromised since 2.8, in current form it might appeal more to sunset screenshot enthusiasts who are clueless about how-to's in Adobe Camera Raw / Photoshop. The one in 2.7 at least didn't have quirkiness in this regard. The quicker solution if I would suggest is to revert back to the older lighting or provide an option to turn this new feature off, now that few cares it appears to be a moot point at this moment. One can only wish it could be tuned to somewhere usable someday in the future.

  • Like 2
  • 3 weeks later...
Posted

The brightness of the whole screen seems to change (quite drastically) depending on the color at the center of the screen.

The result is that either the inside cockpit is visible but the outside is too bright, or the outside is good but the cockpit is too dark.

I use opentrack and the transition between the two conditions is frequent and really slow.

Moreover, using headtracking I don't always look at the center of the display, and if by chance the darker canopy bow  is in middle screen, I cannot see outside.

I'm not sure this is DCS, but I tried to solve all Windows issues before, with no result.

  • Recently Browsing   0 members

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