Graphics Settings in Open Beta

[Sylosis]

NVidia released new drivers, and DCS Open Beta was updated. So I made an additional test.

 

I send two screenshots and let me know what you think. The first one (titled: Untitled2) is from the released version, the other one (Untitled) from the beta. Both have the same graphic settings set.

 

Personally, I find that there is some difference in the rendering, however it is not huge. But you can see some difference still... I personally find that the graphics in the Released version look sharper. What do you think?

 

The remaining issue that I haven't solved is for when I'm on the runway at night time. I still have a super bright cockpit in those instances.

[Goa]

EMH EMG EMH, man the first screen on the left has DEFERRED SHADING off!!!!

[Sylosis]

EMH EMG EMH, man the first screen on the left has DEFERRED SHADING off!!!!

 

Indeed, because it doesn't work in the released version.

 

As for the open beta, I thought it was enforced in 2.5.1, but not anymore in 2.5.2? (you know, since you can't check the option)

[shagrat]

Indeed, because it doesn't work in the released version.

 

As for the open beta, I thought it was enforced in 2.5.1, but not anymore in 2.5.2? (you know, since you can't check the option)

Sorry, but deferred shading works in both Release (2.5.0) and Openbeta (2.5.2).

[Sylosis]

Sorry, but deferred shading works in both Release (2.5.0) and Openbeta (2.5.2).

 

Define work?

 

In 2.5.0, I have, like a lot of other people have posted here on the forum, ugly shading issues. So... It works in the sense of "you can activate it", yes. But "Work" in the sense of "Does it work as intended?" No, I don't think so.

 

Which is why, I assume, this option to activate it was removed from the Open Beta (at least I don't see it anywhere in the options). I thought I read somewhere that it was "enforced activated" in 2.5.1 open beta, and that it 2.5.2 "it was deactivated again". But, maybe this was not accurate. I understand it is still "enforced activated" in 2.5.2?

 

If so, I guess that explains the weird lighting issues I have in the Open Beta on the runway at night. (cockpit being super bright at night due to I don't know what)

 

However, as with regards to this current thread and my most recent post with the 2 attached screenshots. When I said that I was seeing "differences", it wasn't related to the shading, but more to the rendering and sharpness of the textures and shapes, in the cockpit. There are knobs that appear jagged in the Open Beta, while they look better in the Released version. And some of the text on the cockpit, to identify knobs and what not, are more blurred in the Open Beta. I assumed this was not related to shading issues, am I wrong?

 

For example, look at the red handle not far from the nose gear lever in my latest screenshots. That red push/pull lever (sorry I'm not yet so good with the Mig21 and can't name all the levers and knobs... :() looks jagged in the Open Beta screenshot. And, we can't really read whatever is on it, while it is a lot more readable in the released version.

[Art-J]

Yup, DS is enforced in 2.5.2 and looks like it soon will be the same in all subsequent versions, both release and beta.

 

Various smaller and bigger cockpit lighting issues are inherent part of DS and are unfortunately here to stay in my opinion. If ED haven't fixed them for good since 2.1, they won't do it anytime soon. External nav/landing/gear lights illuminating cokpits (escpecially at night) are at least acknowledged as "known issues" affecting all DCS aircraft since release of 2.5.1 OB, so I guess they'll be fixed somewhat sooner.

 

You're right about textures though. Second screen above doesn't look bad, bit the ones you posted on the first page of the thread clearly indicated pit textures not loading properly at all.

 

One more thing, you wrote previously about instruments being messed up after using stable config folders on OB copy. That's a known, temporary glitch happening when switching between custom cockpit language options. You do also have different pit languages set up in both screens above. Try to switch it back to Russian in OB, because I know at least this one should display correctly. While we're at it, do you use any modded, custom pits for A-10 as well?

[shagrat]

Define work?

 

In 2.5.0, I have, like a lot of other people have posted here on the forum, ugly shading issues. So... It works in the sense of "you can activate it", yes. But "Work" in the sense of "Does it work as intended?" No, I don't think so.

 

Which is why, I assume, this option to activate it was removed from the Open Beta (at least I don't see it anywhere in the options). I thought I read somewhere that it was "enforced activated" in 2.5.1 open beta, and that it 2.5.2 "it was deactivated again". But, maybe this was not accurate. I understand it is still "enforced activated" in 2.5.2?

 

If so, I guess that explains the weird lighting issues I have in the Open Beta on the runway at night. (cockpit being super bright at night due to I don't know what)

 

However, as with regards to this current thread and my most recent post with the 2 attached screenshots. When I said that I was seeing "differences", it wasn't related to the shading, but more to the rendering and sharpness of the textures and shapes, in the cockpit. There are knobs that appear jagged in the Open Beta, while they look better in the Released version. And some of the text on the cockpit, to identify knobs and what not, are more blurred in the Open Beta. I assumed this was not related to shading issues, am I wrong?

 

For example, look at the red handle not far from the nose gear lever in my latest screenshots. That red push/pull lever (sorry I'm not yet so good with the Mig21 and can't name all the levers and knobs... :() looks jagged in the Open Beta screenshot. And, we can't really read whatever is on it, while it is a lot more readable in the released version.

 

The option for deferred shading was not removed! It is the only lighting system, since 2.5.1.

 

What requires/had required adaption of textures to the new system from the third parties.

Many " issues" with gamma seem to be based on too high brightness and contrast settings on the monitor...

It helps tremendously to dial down to values around 60% brightness and contrast plus or minus 10 to 15% individual adjustment.

For me this made a gamma value of 2.1 in DCS possible without washing out the environment... You may want to try.

[Sylosis]

Yup, DS is enforced in 2.5.2 and looks like it soon will be the same in all subsequent versions, both release and beta.

 

Various smaller and bigger cockpit lighting issues are inherent part of DS and are unfortunately here to stay in my opinion. If ED haven't fixed them for good since 2.1, they won't do it anytime soon. External nav/landing/gear lights illuminating cokpits (escpecially at night) are at least acknowledged as "known issues" affecting all DCS aircraft since release of 2.5.1 OB, so I guess they'll be fixed somewhat sooner.

 

You're right about textures though. Second screen above doesn't look bad, bit the ones you posted on the first page of the thread clearly indicated pit textures not loading properly at all.

 

One more thing, you wrote previously about instruments being messed up after using stable config folders on OB copy. That's a known, temporary glitch happening when switching between custom cockpit language options. You do also have different pit languages set up in both screens above. Try to switch it back to Russian in OB, because I know at least this one should display correctly. While we're at it, do you use any modded, custom pits for A-10 as well?

 

Funny, I thought I made sure I switched both cockpits to the same "English Metric"... guess I didn't. I'll switch em both to Russian and post back some more screenshots.

 

As for the A-10, no, I don't use any mods or special setting. It's essentially in its default state.

 

Good to know about 2.5.2, I was misinformed. Thanks for clarifying things. So to have the real comparison, I guess I'd have to do my future tests with DS On in the Released version.

 

And, I hope you are wrong about DS issues "being here for long". I mean... I feel this is kinda basic? By basic I don't mean "easy to fix". I mean it's basic in a sense that "it's a major issue that should not be there" at all. You know, to have proper lighting at night is not what I would call "nice to have", but rather "a must have". But anyway, since it's not working so well, at least you would think they would let us the option to leave it off, no? Why force us to use a broken feature? What's the logic in there? I don't get it... :huh:

[Sylosis]

The option for deferred shading was not removed! It is the only lighting system, since 2.5.1.

 

What requires/had required adaption of textures to the new system from the third parties.

Many " issues" with gamma seem to be based on too high brightness and contrast settings on the monitor...

It helps tremendously to dial down to values around 60% brightness and contrast plus or minus 10 to 15% individual adjustment.

For me this made a gamma value of 2.1 in DCS possible without washing out the environment... You may want to try.

 

Sorry if I'm slow to understand. But, I think you meant "deferred shading was not removed", but the OPTION was indeed removed, correct? That's what I understand when you say "It is the only lighting system"

 

As for your point on brightness and contrasts, I can try and see.

 

But I think the nightime runway lighting issue will still remain, no matter what contrast and brightness setting I put.

 

And finally, I made most tests with the Mig21. I'll try all the modules I own, see if the textures/renders/shapes are sharper on other modules.

[nekhron]

I don't get the difference in look between 2.5.0 and 2.5.2 its really weird

 

 

on the left is 2.5.2 beta

 

middle : 2.5.0 : without deferred shading

right : 2.5.0 : with deferred shading

 

 

2.5.2 is lighting up like xmass tree

 

 

My spec are :

 

 

I7-8700

16 gig of ram

gtx 1080 8 gig

Edited June 7, 2018 by nekhron

[nekhron]

Deffered shader dont seems to work quite right

[shagrat]

I don't get the difference in look between 2.5.0 and 2.5.2 its really weird

 

 

on the left is 2.5.2 beta

 

middle : 2.5.0 : without deferred shading

right : 2.5.0 : with deferred shading

 

 

2.5.2 is lighting up like xmass tree

 

 

My spec are :

 

 

I7-8700

16 gig of ram

gtx 1080 8 gig

Ehm, that is probably the light from the truck with the flak light illuminating the runway... and in addition your cockpit.

I had a similar "that looks weird" moment in the UH-1H on a FARP at night. Then I noticed the flood lights on the pad! ;)

 

If that light persists after take off, something is wrong.

 

The night lighting in 2.5.x is still WIP, as far as I am aware.

Especially the taxi and landing lights are too dim, but all night illumination seems to need some tweaking still.

[Sylosis]

Ehm, that is probably the light from the truck with the flak light illuminating the runway... and in addition your cockpit.

I had a similar "that looks weird" moment in the UH-1H on a FARP at night. Then I noticed the flood lights on the pad! ;)

 

If that light persists after take off, something is wrong.

 

The night lighting in 2.5.x is still WIP, as far as I am aware.

Especially the taxi and landing lights are too dim, but all night illumination seems to need some tweaking still.

 

I have the exact same bright cockpit as what is seen in his beta screenshot.

 

And yes, it stays like that for some time after the plane takes off. I haven't had the chance to run all the tests, but it might very well be the known issue of your own landing light going through the airframe and lighting the inside of the cockpit.

 

I'll try to provide additional info tonight.