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

[mlb406]

Hi,

 

Jumped in the viper after the update to test out the new maverick logic only to find that my mavericks aren't showing their aiming crosshairs correctly. 

You can see on the right hand MFD it's almost like its showing the break lock symbology, but that is brand new from a hot air start going into AG mode and putting the WPN display on. I haven't tried to lock on to anything, or even changed maverick mode.

 

This applies to all maverick variants, including on the LAU-88 and the LAU-117, and I think it applies in PRE, VIS and BORE modes.

 

I have included a track file, although there is little configuration done, it is literally just spawning in from an air start, selecting A-G mode, displaying the WPN page, and the mavericks have no crosshairs. When a target is locked through the HUD SPI or the TGP in PRE mode, the closed crosshairs display again.

 

Thanks!

F-16_MAVNoCrosshairs.trk

[Deano87]

Have you read this thread and tried the fixes that worked for other ppl?

[mlb406]

8 hours ago, Deano87 said:

Have you read this thread and tried the fixes that worked for other ppl?

I have yes, and it does not solve my problem. 

 

I feel this is a new bug, as it only started happening after the most recent update.

[BIGNEWY]

Not seeing any problem in the track replay.

 

Please try the latest open beta, if you are not getting cross hairs you are in break lock

[mlb406]

Hi BN,

 

Do you mean that you can see the crosshairs on my track? Then that is fun 

If so then it's probably a graphics problem on my end, I'll have another play around when I get time!

 

Thanks

Max

[Deano87]

1 hour ago, mlb406 said:

If so then it's probably a graphics problem on my end, I'll have another play around when I get time!

You have tried renaming your saved games DCS folder and that had no effect?

[Bog9y]

Hi guys, I had this exact problem and have just figured out exactly what's causing it. As Deano87 suggested, removing the options.lua file fixes the problem. But, as soon as I set my settings back to where they were I lost the crosshairs again.  

 

After lots of testing I found out it is the MSAA setting.  If you have MSAA set to OFF, the crosshairs are not displayed.  Setting it to 2x or 4x makes them appear again.  

 

I have no idea how this is linked  but there you go...setting it to 2x fixed it for me.

[ishuikh]

Hi everyone when ED show us the new system of the maverick since that be4 1month i cant get the cross at WPN page D and H the same issue i tried all mods (VIS,PER,BORE) and its so hard to lock any target so i need help with that ^__^  

[Deano87]

Take a look at this thread, some people managed to fix their issues by following some of my steps.

 

 

[StandingCow]

I hit bignewy up in discord and he is gonna check it out today.  I don't believe this to be a break lock issue at all since that still displays half xhairs and can be corrected by just doing a TMS down or relocking IIRC.  Plus the only way one of my buddies was able to get his xhairs back is Deno87's fix of deleting options.lua... so there is a def a bug. 

 

Hopefully BN gets it on ED's radar to fix.

[BIGNEWY]

Hi all, 

 

I have taken another look, but all seems ok for me, I have tested with MSAA off and on also. 

 

if you are using shader mods try removing them, do a cleanup and repair or verify for steam 

 

delete your metashader2 and fxo folders in your dcs folder in saved games location

 

restart DCS and test again, please add short track replays showing the issues you are having I am happy to take a look.

 

thanks

[normanleto]

I think I had this issue as well, but I resolved it by setting in-cockpit display resolution to 1024 every frame. On 256, the resolution is too small to cover thin lines.

I am not sure if it helps in similar cases, in my case it worked. I fly in 4k resolution.

 

thanks,

 

[viper1]

Confirm!

I had MSAA off in VR only turning on 2x or 4x MSAA fixed problem.

[cAshewTheAce]

[cAshewTheAce]

Well since it decided to delete the whole long report... Here is the tldr

Maverick crosshair is bugged, the image shows it untouched (only put as SOI). It is not in the break lock mode (tws down just makes it not soi again). Regardless of mode this behaviour is roughly the same. What "fixes" this is setting the MSAA to 2x, as i had it on 0x. I also experimented with putting cockpit displays to 1024 and changing AF to 2x, but to no effect.

PC specs are as follows
Ryzen 3 2200g

GTX 1060 3GB

16 GB ddr4 2777mhz

DCS is installed on a 230gb nvme m.2 ssd

I will send the DCS settings in a separate screenshot.

[Deano87]

I run 0 MSAA and don't have this issue.

Have you tried clearing the fxo and metashaders folders from your DCS directory in your Users Saved Games folder?

Cheers

D

[cAshewTheAce]

9 hours ago, Deano87 said:

I run 0 MSAA and don't have this issue.

Have you tried clearing the fxo and metashaders folders from your DCS directory in your Users Saved Games folder?

Cheers

D

Indeed that did fix the issue, atleast temporarily. What are the fxo and metashader folders for?

[Deano87]

3 hours ago, cAshewTheAce said:

Indeed that did fix the issue, atleast temporarily. What are the fxo and metashader folders for?

Great to hear it working for you. Those files are shader cache files which reduce loading times on subsequent loads after the first one, I recommend clearing them out with every sim update. If any of the previously cached files have changed it can cause conflicts with the new files and weird issues here and there.

Cheers

D

Edited November 13, 2021 by Deano87

[slidem]

Problem got fixed for me too.

I had MSAA off. I did set it to x2 and now Maverick cross is there and working. Cheers

[TOViper]

I still have this problem in OB 2.7.17.29493

What I did in the 1^st step:
.) Installed new graphic driver NVIDIA 516.94 (GameReady), performed clean installation
.) Deleted fxo and metashaders 2
.) Kept only F-16 and Caucasus Mods in the game folder
.) Removed all user mods from userprofile (A-4)
.) Used default NVIDIA settings with no success
.) Used my usual NVIDIA settings with no success

2^nd step:

.) DCS Repair with Check all files > slow and check for extra files (removed any if they were present)
.) Deleted fxo and metashaders again

Still no luck.

Attached find:

.) Screenshots of NVIDIA settings (3 pages)
.) Screenshot of cockpit situation
.) config.lua
.) dcs.log

What else can I do. I am out of any ideas ...
Thank you!
 

options.lua dcs.log

Edited September 4, 2022 by TOViper

[OldFlyer]

Hi,

I haven't flown the F16 for a couple of months now, but I now can't seem to boresight the Mavericks.

Perhaps I'm doing something wrong, so I've attached a track file where I've shown my steps fairly slowly and deliberately.

1) The TGP won't snowplow. I've seen this mentioned elsewhere on the forum but the fact it doesn't look straight out in front of the plane now makes things annoyingly cumbersome. So I set a mark point out near the front of the plane for the TGP to look at. Surely this is a bug?

2) Then once I've got the TGP looking at something, the crosshairs on the Maverick seem to have disappeared and have been replaced by 2 horizontal lines and a cross. I'm sure they didn't used to look like this, and cross-checking against some videos on YouTube suggests the same.

Have I done something wrong in either of these steps? Or are they bugs?

Thanks

F16_TGP.trk

[OldFlyer]

OK, so if anyone is experiencing the Maverick losing its crosshairs issue, I spent a couple of hours trying to fix it and ultimately what did it was performing a repair. Went back into the game and tried again and the crosshairs were back

Obviously the repair didn't fix the TGP snowplow issue!

[Lord Vader]

Hi @OldFlyer

I was going to suggest a repair for the Maverick issue. Good thing you did it and solved your problem.

Regarding the snowplow feature, you said it yourself that you haven't flown the F-16 for some time.

The Snowplow logic was updated and improved. Some of the TPOD functions still require some additional system logics that are still being worked on incrementally. But we are confident this is working much closer to the logics of available documentation. 

Take a look at my comment here, it should help you understand how it works now:

 

[OldFlyer]

Ok great thanks!

[Stilgar]

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