[ALREADY REPORTED]MavF display broken on latest patch

[Stubbies2003]

Sigh. Welp now the MavF using it's own sensor is basically useless as a stand off weapon until fixed. The display at 10 nm is completely black on the ground. If you drive in to less then 5 nm than you can start to see the normal display. Tried messing with both contract and brightness. The only thing contrast seemed to do was to change the DDI text color from green to yellow when turned up. Turning it back down would change the color back to green but no noticeable change in the MavF sensor display what so ever for the ground display. It did change what I was seeing above the ground but at 10nm it is nothing but a sea of black on the ground.

 

This was on a Nevada MP map with overcast weather but clear below 10k feet and obviously I was staying below the clouds.

Edited August 19, 2020 by Stubbies2003

[Swift.]

Sounds like they've made it more representative of the real thing then. ;)

[imacken]

Yep, unusable still. I thought this was going to be fixed in today’s patch.

[Noluck]

What version NUMBER did you see this in?

[VFA41_Lion]

Latest OB, MavF display works fine. Not blacked out at all.

[imacken]

Does this look right to you guys?

Same target, 2 pairs of images.

First 2 are at 10 miles with a change of FOV, and the second pair are at 5 miles with a change of FOV.

[Wizard1393]

My MAVF image is also very very dark now since the Aug 19 OB. Not at all like imacken's screenshots above.

[Stubbies2003]

Imacken those look fine to me. For a time it will bloom after an explosion then get back to a normal look. Now one of those you might be looking at a smoke marker which, for some reason, will also bloom the display badly as well. Doubt that would be realistic but that is what the display does at least in the 18. The color of the smoke changes how badly it blooms too. Like chrisofsweden that is nothing like I am seeing now. Looking at the ground at 10nm is nothing BUT black.

Edited August 20, 2020 by Stubbies2003

[imacken]

Sorry, you guys think that these images are correct? I have to disagree. Image 4, particularly, makes it impossible to use. Can't see any targets or terrain at all!

 

Didn't used to be like this.

[MoCluck]

I'm getting the same issue, the Maverick display used to look similar to the TPod but with worse resolution. Changing from white hot to black hot just changes the colour of the cross hair too.

[Ramsay]

Sorry, you guys think that these images are correct? I have to disagree. Image 4, particularly, makes it impossible to use. Can't see any targets or terrain at all!

 

Didn't used to be like this.

 

For me, DCS's Maverick IR shader has always been like that in 2.5.x (A-10C, AV-8B, etc.).

 

Like the TGP's IR render, setting chimney smoke = 0, clearing the shader cache and/or replaying a IR track before hand, reduced the chance of the IR render "bugging out" but there was always a chance (~1 in 4) the next mission I'd play would have a bugged IR display.

 

AFAIK the latest "patch" has fixed the "overly dark" IR image bug and reverted the TGP/Maverick IR render to the previous (but buggy) image brightness.

 

Those who say the heat "bloom" is realistic, should note the smoke is "cold" and "green" smoke is unaffected.

 

https://forums.eagle.ru/showthread.php?p=4082694#post4082694

 

Changing from white hot to black hot just changes the colour of the cross hair too.

AFAIK that's normal for the F/A-18C (perhaps WIP or a DCS simplification).

Edited August 20, 2020 by Ramsay

[imacken]

My MAVF image is also very very dark now since the Aug 19 OB. Not at all like imacken's screenshots above.

 

Oh I get totally dark as well!

[rob10]

Changing from white hot to black hot just changes the colour of the cross hair too.

 

 

That part is working correctly. The polarity change on the MAV only changes what it is trying to lock onto: hot target (white) or cold target (black). The cross hair colour change is so you know which mode it's in. Unlike the TPOD it doesn't change white hot/black hot polarity (it's always white hot).

[LastRifleRound]

For me, DCS's Maverick IR shader has always been like that in 2.5.x (A-10C, AV-8B, etc.).

 

Like the TGP's IR render, setting chimney smoke = 0, clearing the shader cache and/or replaying a IR track before hand, reduced the chance of the IR render "bugging out" but there was always a chance (~1 in 4) the next mission I'd play would have a bugged IR display.

 

AFAIK the latest "patch" has fixed the "overly dark" IR image bug and reverted the TGP/Maverick IR render to the previous (but buggy) image brightness.

 

Those who say the heat "bloom" is realistic, should note the smoke is "cold" and "green" smoke is unaffected.

 

https://forums.eagle.ru/showthread.php?p=4082694#post4082694

 

 

AFAIK that's normal for the F/A-18C (perhaps WIP or a DCS simplification).

 

This has been exactly my experience as well.

[LordOrion]

No problems here: all seems to wok fine.

[imacken]

Really?

OK, can you post a screenshot of the stock Hornet Maverick Nevada mission just after you activate the Mav display?

Thanks.

[imacken]

To try and highlight the point, here are some screenshots. 2 are from build 49798 and 2 are from the current 53756.

There are pairs, both form the stock ED Hornet missions in Caucasus and Nevada. Same smoke in both Caucasus, different effect.

I'll let you guess which build for me is unusable!

[LordOrion]

Really?

OK, can you post a screenshot of the stock Hornet Maverick Nevada mission just after you activate the Mav display?

Thanks.

 

 

Here is.

I took one screenshot for each map (Caucasus, Gulf and Nevada).

[Drac]

To try and highlight the point, here are some screenshots. 2 are from build 49798 and 2 are from the current 53756.

There are pairs, both form the stock ED Hornet missions in Caucasus and Nevada. Same smoke in both Caucasus, different effect.

I'll let you guess which build for me is unusable!

 

+1...same problem as well.

[imacken]

OK, here are a couple of tracks. I'm not sure how useful they will be, as this is a graphical issue and if you are not seeing it normally, you won't see the issue looking at a track.

 

This has all come from the change in the DDI displays a couple of patches ago, when ED changed them to be very dark and contrasty to answer the complaints about users not being able to see the DDIs when flying with the sun behind. Although that problem was solved, it was solved in a very unrealistic way. The DDIs are way too dark to the extent that the brightness control is useless. Just permanently sits at max. If that could be resolved, then I think the issue I and others are experiencing would also be resolved. Have the current level of brightness as the 50% point, and allow users to choose.

 

The DDIs lack of visibility with the sun at your back was realistic, and didn't need changing. Obviously, in real life, one would put oneself between the light source and the DDI to shade the readings, and it would be ideal if something could be put into DCS to replicate that behaviour.

 

I've put some more screenshots in so you can see what this looks like for me. Sorry that I'm posting so many!

Mav display Nevada.trk

Mav display Cauc.trk

[KLaFaille]

Displays went dark in the July patch, were supposed (I believe) to fixed for the 8/19 patch. It was acknowledged a month ago, so don't see what a track is going to accomplish in this instance.

Edited August 22, 2020 by KLaFaille

[imacken]

Tracks supplied in post #20.

[BIGNEWY]

Hi all,

 

this is already reported

 

thank you

[imacken]

Thanks BN.