General_Av8or Posted May 16 Posted May 16 (edited) I have noticed recently that the weapons page while employing the AGM-65D Maverick does not show the full vertical and horizontal lines (Tracking Gate?) used for targeting while slewing the seeker head to a target. If you press TMS Forward to "lock" a target the vertical and horizontal lines appear and are locked on the target, only if you place the target in the center of where the cross should be while scanning for a target. It has become difficult to lock targets without the cue on the weapons page indicating where the lockable point on the MFD is on the weapon page. It used to be the case, while slewing the weapons page you would have the full + in the screen to indicate where the seeker head was "looking" and then you center the target in the + and TMS FWD. Now that + is not present you have to get lucky to lock something, then you will see the + like a normal lock. I have tried clicking on every option on the weapons page. I have tried to align the maverick to the tpod using an aircraft in the air flying at a constant speed in front of me, but could not get any indication when pressing BSGT that it had any operation to that button (tried this to see if this would "fix" the + not being there; note: I have not aligned my mavericks with the tpod in a while so this alignments problem could be user error) I have noticed this behavior in both multiplayer and single player missions. Attached Track, and video is from FIWOS Campaign Mission 03, but have noticed this behavior in my created missions, as well as in multiplayer. I have also noticed this behavior for all modes: PRE, VIS, BORE. I have not tested other maverick models (only D model) if I can replicate these. Log: https://drive.google.com/file/d/1nboPVRZ6M5ntk86UQBXrPH4BUkq1ixaT/view?usp=drive_link Track: https://drive.google.com/file/d/1yzpJQ_FoN_QZd4s72wTOsbVeaFrgsswL/view?usp=drive_link Video: https://youtu.be/P4NTAbdiWsE The following are from a created mission as you may need a un scripted mission for testing. Log, Track, .miz files: https://drive.google.com/file/d/12buYRimwbKaA6CEfV_lo-PvGKLkgO6Os/view?usp=drive_link Video: https://www.youtube.com/watch?v=8rUJvSxDbME Edited May 16 by General_Av8or
ED Team BIGNEWY Posted May 28 ED Team Posted May 28 Hi @General_Av8or we have checked and symbology is correct, if you have any public evidence it is wrong please DM me. thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Solution General_Av8or Posted May 31 Author Solution Posted May 31 Dug deep and found this thread on the issue 5 years ago: going through it and still no luck, will keep looking and trying different things. Thanks for the time.
General_Av8or Posted May 31 Author Posted May 31 (edited) Going through this old thread, it was a bug that ended up getting reported after a lot of back and forth. I changed my cockpit display res to 512 deleted the fxo and metashaders2 after changing the cockpit display from 256 to 512. Just changing the cockpit res is not good enough, you MUST delete the two folders after making the change for the problem to get resolved. Got the crosses just fine now. Maybe the bug that was reported earlier showed back up? Edited May 31 by General_Av8or 1 3
Recommended Posts