solved AGM-65D WPN page versus TGP > picture in WPN completely blured and unusable

[TOViper]

DCS openbeta 2.8.32235
F-16C Viper
SP
Syria
Single unit on map from ME

Picture of AGM-65D is very unsharp, no matter what I select in setting "Res. of cockpit displays" (currently 1024), while the TGP has super quality image.

Attached my DCS configuration file.
 

options.lua

F-16_Training_AGM-65D.miz

Edited November 16, 2022 by TOViper

[Harker]

I don't see anything wrong. It's supposed to be, the Maverick's seeker is much lower quality (makes sense, since it's supposed to be destroyed).

See these for reference. I would say that DCS's quality is still much better than IRL.

 

Edited November 16, 2022 by Harker

[BIGNEWY]

Hi, 

I am not seeing a bug here, as Harker has pointed out the Mav seeker is much lower quality 

thank you

[TOViper]

So you would you say that it cannot get better than this?

 

 

 

[QuiGon]

8 minutes ago, TOViper said:

So you would you say that it cannot get better than this?

Uhh, that looks definitely not how it looks on my side. The Mav display is way more blurry in your pic than it is on my side. 

Edited November 16, 2022 by QuiGon

[_SteelFalcon_]

What‘s your MFD display resolution? Could that affect it?

Edited November 16, 2022 by _SteelFalcon_

[TOViper]

I get same results with 1024, 512 and 256

Edited November 16, 2022 by TOViper

[Deano87]

I'm not at home so I can't check your mission... Couple of Qs from me though. Is it a hot/airborne spawn or cold and dark? Does it make any difference if you try either? Does it make any dif if the Mavs are boresighted or not?

Edited November 17, 2022 by Deano87

[TOViper]

In this case (for the attached MIZ file and the screenshot above), I spawned HOT in air.
During flying in Buddyspike Syria, I also have the same issues when spawning HOT on ground; there same problem appears.
The funny part of the story is, that WAGS videos show fantastic quality of the WPN page in comparison to his TGP, and on the other hand I have never seen such a nice quality on my rig
@BIGNEWY: Please take a closer look to the picture above, I simply forgot to add it to the original post. Thank you!

Edited November 17, 2022 by TOViper

[BIGNEWY]

On 11/16/2022 at 9:30 PM, TOViper said:

So you would you say that it cannot get better than this?

 

 

 

I can not reproduce this, your image on the left looks wrong for sure. but when I test all is ok. 
Please remove any unofficial mods and run a repair or verify if steam, if you are using shader mods also remove them. 

Delete your fxo and metashader2 folder in dcs folder in saved games, restart DCS and allow time for new shaders to be created

If you still have issues please attach your dcs log and let us know your AMD / NVIDIA settings

thanks

[TOViper]

Wilco & report back, thanks meanwhile!

 

[Deano87]

@TOViper I think I ran into this issue last night. It happened after I powered my mavericks down after boresighting and the powered them back up again. During boresighting they were about as sharp as would be expected, and then after the power down, 20min transit and then powering back up the maverick view was all blurry. No track unfortunately as I was online but Ill try and repro in singly player today. 

[BIGNEWY]

The Maverick picture should not be quality like the TGP, you can clearly see in real world examples the MAV picture is not great. 

If you have short track replay examples please post them. 

thanks

[LieutenantFalcon]

10 hours ago, Blue Giant said:

I think the issue is you (or OP/others) are expecting a bit too much from the IR mavericks. What your TGP sees is a TV image of (I assume) cold tanks, if you switch it to IR they would also hardly show up as they do on the Maverick seeker. The IR mavericks aren't going to be able to target an object that's at ambient temperature effectively, it needs a contrast in terms of temperature. For this use case you would be much better off using the EO/TV Mavericks. 

[_SteelFalcon_]

Did a quick test, air spawn, took screenshot, then powered mav down, powered them back on and took another screenshot.

now guess which is which  

 

I might add: in OPs screeenshot distance shows 3 nm and no WPN cross is anywhere on the MFD. is it possible the mav lost track of the target due to mav seeker limit and was trying constantly to stay on "target"?

Mav_Screen.trk

Edited November 22, 2022 by _SteelFalcon_

[Hobel]

Am 16.11.2022 um 22:30 schrieb TOViper:

So you would you say that it cannot get better than this?

 

 

 

even the typical Mav crosshair is missing here?

you must definitely try to create a track.

[TOViper]

1 hour ago, Hobel said:

even the typical Mav crosshair is missing here?

you must definitely try to create a track.

This is a problem of setting MSAA to OFF.

A track doesn't help, since the rendering of the screen happens on the client which is playing the TRK.
The screenshot is a good representation of what is happening.

Currently I am testing all settings, this will take a while.

Edited November 22, 2022 by TOViper

[TOViper]

What I found out is that:
.) The NVIDIA setting "Antialiasing - Gamma correction" has something to do with it
.) I have to have MSAA set to anything other than OFF (e.g. 2x, 4x) in order to have the crosshairs visible correctly
.) It has something to do with the fxo as well

I will test more when I have the time for, but currently I cannot reproduce it, either the whole thing NOT working nor working (hard to understand, but I got it working, but didn't found out what was causing the issue). Once it got broken by changing the NVIDIA setting, I need to delete the fxo and start from scratch.
This is exhausting.
 

 

Edited November 23, 2022 by TOViper

[TOViper]

@BIGNEWY I found the issue, but it very looks like it is caused by how DCS works (or in that case not correctly works) with fxo's:

.) I did empty the fxo folder and metashaders2 before doing anything
.) Then I start DCS
.) "Display resolution" in the SYSTEM settings was set to 256
.) After reaching the first mission, the fxo's were all created
.) It seems the WPN page is then rendered at that certain resolution (in my case at the "lowest - bad setting" of 256 for a very long time since I fly the F-16, because I struggle with fps since ever especially when I fly with TGP and MAV's and using them in parallel)
.) I then selected 1024 in the SYSTEM settings, but: The fxo's seem not to be updated anymore; I had to delete fxo's for each change of the SYSTEM settings.

Ah, and by the way: I had to use the current OB 2.8.0.33006, since I update a few days ago.
Side story: The problem with the crosshair is gone, I now managed to see the crosshair with MSAA set to OFF.

Hope this helps someone out there, but at least I hope you guys at ED will correct this problem somehow (which drove me crazy).

Thanks,
TOViper

Edited November 23, 2022 by TOViper

[BIGNEWY]

Thank you for letting us know. 

The MSAA issue with the crosshair is reported

 

[silverdevil]

21 hours ago, TOViper said:

.) "Display resolution" in the SYSTEM settings was set to 256

good work and troubleshooting. in any case do you believe those with setting at 1024 are not affected by this issue?

[TOViper]

It doesn't count what I believe, its always better to prove something.
I can say for sure for my rig I was able to solve the issue by doing these steps:

• Have DCS running
• Set resolution to 1024
• Quit DCS (this was important)
• Remove fxo shaders and metashader2
• Start DCS and let the shaders be re-build
• Enjoy WPN page in good resolution (better than some guys above said it should be, because IRL it seems the picture isn't that nice ... *checheche*... )

[silverdevil]

12 hours ago, TOViper said:

It doesn't count what I believe, its always better to prove something.
I can say for sure for my rig I was able to solve the issue by doing these steps:

• Have DCS running
• Set resolution to 1024
• Quit DCS (this was important)
• Remove fxo shaders and metashader2
• Start DCS and let the shaders be re-build
• Enjoy WPN page in good resolution (better than some guys above said it should be, because IRL it seems the picture isn't that nice ... *checheche*... )

thanks for your answer. i suppose my question was not clear. i mean to ask, if a DCS setting is already at 1024 (mine has always been 1024), the shaders would already be compiled to the less blurred textures? or put another way, if a user deletes the contents of the folders each start of DCS, they too would have the less blurred textures?

[TOViper]

Yes, it seems so.

[QuiGon]

19 hours ago, silverdevil said:

thanks for your answer. i suppose my question was not clear. i mean to ask, if a DCS setting is already at 1024 (mine has always been 1024), the shaders would already be compiled to the less blurred textures? or put another way, if a user deletes the contents of the folders each start of DCS, they too would have the less blurred textures?

It should just depend on what setting you have set the displays when new shaders get compiled. If you always have your setting on 1024, then it will always compile it in good quality.
@TOViper's workaround just applies to people that usually play with lower display settings.

Edited November 25, 2022 by QuiGon