reported F-16 Agm-65 Maverick crosshair disappearing with 0x MSAA

[Stilgar]

Hi, i have this problem, someone found a solution?

[TOViper]

1 hour ago, Stilgar said:

problem, someone foun

yes:

1. in DCS, select the "Display resolution" of your desire (256, 512, 1024)
2. Quit DCS
3. Clear *.fxo cache from user profile
4. Restart DCS and *pray* that it works

Post result ...

[OldFlyer]

I also had this issue recently, I fixed it by running a repair

[Stilgar]

1 hour ago, TOViper said:

yes:

1. in DCS, select the "Display resolution" of your desire (256, 512, 1024)
2. Quit DCS
3. Clear *.fxo cache from user profile
4. Restart DCS and *pray* that it works

Post result ...

This operations worked well!

Thanks

[TOViper]

De nada!

[SONIC301]

Hi! since last patch (hotfix) i dont get to see the lock on croshair anymore with the mavericks. Allready did a repair / cleanup.

[razo+r]

 

Try changing your graphics settings

[Lord Vader]

Hi @SONIC301I can't find that issue while operating missiles in VIS mode.

Do you have MSAA or other anti-aliasing filters turned off? Have you tried turning it back on?

[SONIC301]

Deleting the metashader2 and fxo file + putting MSAA to x2 or x4 and cockpit display at 512 or higher fixed it for me. thanks

[bill2502]

On 8/9/2023 at 2:06 PM, Stilgar said:

Hi, i have this problem, someone found a solution?

Yes, delete the fxo and metashaders folder in your user saved games directory, and restart DCS.

[Buzz313th]

• DCS 2.9 Open Beta
• 12900k RTX4080 64gigs ram
• Quest 3 Open XR Forced under shortcut running at 4800x2600
• No Mods
• Cleaned install 5 minutes prior to this post
• Re-install of F16 5 minutes prior to post

Summary:

I do not have maverick crosshairs, nor FOV markers on the maverick wpn display unless I...

• Set cockpit displays to 512 or greater and turn on MSA at 2x or greater and restart DCS after erasing all shader files.

Once I do that, I get crosshairs.  As soon as I turn off MSA and set cockpit displays to 256, then the next mission the maverick WPN display is bugged again with no crosshairs or FOV markers.

I am not in a position to to leave MSA on, or cockpit display resolution to anything greater than 256.  In VR under the resolution I have chosen, I gain nothing from a higher cockpit display resolution and actually lose quite a bit of performance with induced stuttering if I raise it above 256.  I also gain nothing by enabling MSA as it just causes distant objects to become less sharp and blurry with a loss of performance through induced stutters.

I have searched the forums for this issue and have found numerous posts dating back to 2020 describing the same exact issue I am facing.  The solution that the forum users have discovered, is to turn on MSA  and raise cockpit display resolutions then recompile shaders.  What if the user chooses not to use MSA and chooses to run cockpit displays at a res of 256, then they are stuck with this bug, not acceptable IMHO.

Can ED please find the time to look in to this issue and have a go at fixing it?  The problem will persist unless effort is made.

Past posts that have referenced this bug ....

 

Thank you.

 

Cheers

dcs.log MaverickWPNDisplayNoXhairs.trk

Edited November 13, 2023 by Buzz313th

[BIGNEWY]

threads merged, 

we will take another look but we have not been able to reproduce. 

thanks

[Buzz313th]

7 hours ago, BIGNEWY said:

threads merged, 

we will take another look but we have not been able to reproduce. 

thanks

The bug appears and disappears on my end like clockwork.  I am able to reproduce by following my op.  If you guys are still having problems reproducing, please reach out and I can help.  A couple more tidbits of info to hopefully help you guys find this...  

When the bug is active, or in other words, when the maverick crosshairs are not there and should be, a successful maverick lock shows the crosshairs and the FOV markers.  Once the maverick is fired and the display steps to the next missile, the crosshairs are gone again.   So this is obviously not just a shader or graphics only issue.  There is code that is causing this bug to manifest itself or fix itself.

Edited November 13, 2023 by Buzz313th

[antiload]

I'm also having this issue with Maverick D in pre mode. The crosshair is inconsistent in appearing.  When I do get a lock the missile is off target by several meters. I will re-test and see if I can reproduce the issue. 

Edited November 14, 2023 by antiload

[Buzz313th]

On 11/13/2023 at 12:00 AM, BIGNEWY said:

threads merged, 

we will take another look but we have not been able to reproduce. 

thanks

@BIGNEWY

I have reported a bug that feels like it may be related to this one, as the cockpit display resolution setting is causing unexpected and illogical results on the kneeboard maps..

Link below to the newfound bug.

 

[antiload]

On 11/14/2023 at 8:21 PM, antiload said:

I'm also having this issue with Maverick D in pre mode. The crosshair is inconsistent in appearing.  When I do get a lock the missile is off target by several meters. I will re-test and see if I can reproduce the issue. 

 

Apologies, my issue was not a bug. It was impatience and not knowing the weapons system on my part. I re-tested and realised that just because one is within the firing range (as indicated on the HUD), it seems that it doesn't mean the maverick D seeker can lock the target. It will only attempt a handover. 

 

[SpeedDemonAdam]

I am also experiencing this issue since. 2.9.0.47168. Shader reset. Repair, DDU, msaa on/off. 

Ryzen 5800X3D

Rtx2080Ti Driver:546.17

64GB GSkill Trident Z 3400mhz

 

Edited November 24, 2023 by SpeedDemonAdam

[SpeedDemonAdam]

I fixed this issue by changing the cockpit screen resolution from 256 to 1028.

[Buzz313th]

9 hours ago, SpeedDemonAdam said:

I fixed this issue by changing the cockpit screen resolution from 256 to 1028.

So did I, but in VR the is a large frame hit at the higher resolutions.   Why can't ED address this issue so the Mav WPN display works in all DCS cockpit screen resolutions?

@BIGNEWY, I can only assume the devs are busy with bigger fish, but have you had any response?

[TOViper]

On 11/26/2023 at 8:28 PM, Buzz313th said:

So did I, but in VR the is a large frame hit at the higher resolutions.   Why can't ED address this issue so the Mav WPN display works in all DCS cockpit screen resolutions?

@BIGNEWY, I can only assume the devs are busy with bigger fish, but have you had any response?

You can go at 256 or 512 in VR, thats not a big problem, but you have to choose this selection, then quit DCS, then remove the fxo's and let them re-build when re-starting DCS. Did you do that?
The point is, every time you change settings, you "must" clean the fxo's.
I tell you this, because for my rig, there is no other way around currently.

Edited December 7, 2023 by TOViper

[Buzz313th]

5 hours ago, TOViper said:

You can go at 256 or 512 in VR, thats not a big problem, but you have to choose this selection, then quit DCS, then remove the fxo's and let them re-build when re-starting DCS. Did you do that?
The point is, every time you change settings, you "must" clean the fxo's.
I tell you this, because for my rig, there is no other way around currently.

Not true, at least for me.  Unless I maintain 512 or higher, then the next time I boot up DCS I lose the mav MFD symbology.

So I just accepted the fact that I have to maintain 512, or switch to 256 after starting DCS and switch back to 512 before shutting it off, or I have to switch and clear shaders and restart.  All a simple workaround for a development bug that at some point hopefully will be looked at.  I don't mind jumping through hoops. 

So to be clear..  If I switch to 256, clear shaders and start DCS..  Only the first time I restart do I get good mav mfd's.  If I leave it at 256, the next time I start DCS it's borked.

Edited December 7, 2023 by Buzz313th

[NineLine]

3 hours ago, Buzz313th said:

Not true, at least for me.  Unless I maintain 512 or higher, then the next time I boot up DCS I lose the mav MFD symbology.

So I just accepted the fact that I have to maintain 512, or switch to 256 after starting DCS and switch back to 512 before shutting it off, or I have to switch and clear shaders and restart.  All a simple workaround for a development bug that at some point hopefully will be looked at.  I don't mind jumping through hoops. 

So to be clear..  If I switch to 256, clear shaders and start DCS..  Only the first time I restart do I get good mav mfd's.  If I leave it at 256, the next time I start DCS it's borked.

 

Good info, I will check this out. Thanks.

[Buzz313th]

3 minutes ago, NineLine said:

Good info, I will check this out. Thanks.

Thank you.

[TOViper]

3 hours ago, Buzz313th said:

Not true, at least for me.  Unless I maintain 512 or higher, then the next time I boot up DCS I lose the mav MFD symbology.

So I just accepted the fact that I have to maintain 512, or switch to 256 after starting DCS and switch back to 512 before shutting it off, or I have to switch and clear shaders and restart.  All a simple workaround for a development bug that at some point hopefully will be looked at.  I don't mind jumping through hoops. 

So to be clear..  If I switch to 256, clear shaders and start DCS..  Only the first time I restart do I get good mav mfd's.  If I leave it at 256, the next time I start DCS it's borked.

 

Ah, damnit, I didn't have this exact situation I think.
I finally switched to 512 or even higher, so I did not have the exact same situation than you.
Anyway, Nineline took notice ... which is good!

[Buzz313th]

7 minutes ago, TOViper said:

Ah, damnit, I didn't have this exact situation I think.
I finally switched to 512 or even higher, so I did not have the exact same situation than you.
Anyway, Nineline took notice ... which is good!

All good.

yeah, at my HMD resolution I gain nothing at 512 or higher.  It just puts more load on the render thread when using optical displays.  But to keep from having to overcomplicate my shutdown and startup, I just bit the bullet and stay at 512 now.