AstonMartinDBS

I think UNDESIGNATE should stop the continuous designation update from other sensors (like ATFLIR) while MAV has priority. This could be the solution because it would make the MAV slewable again.

Just tested and no trees here (runnin' current OB, 2.7.8.16140). Maybe the occurrence of the issue depends on whether the DCS session has been going on for a long time or the mission is started immediately after loading DCS. I tested right now immideiately after DCS launch.

Maybe @BIGNEWY or @NineLine can ask the team if the current behaviour with ATFLIR in SCENE or AUTO mode is correct:

Try this: BTW: you're little OT here in the "Controller Questions and Bugs" section

That works great - as long as ATFLIR is in INR mode. But the MAV seeker isn't slewable when the ATFLIR is in SCENE or AUTO mode, because the MAV re-slaves continuously to the ATFLIR designation. It's impossible to brake this constant designation update/re-slave loop with undesignate, while ATFLIR is in SCENE or AUTO mode and sensor priority is on the MAV format page. I don't think, that this is as intended, because I don't see any reason for that behaviour.

Indeed! Same here. Current OB.

[OT] Try this link to find threads started by yourself: https://forums.eagle.ru/discover/content-started/

That would interest me too.

Already tested - no problems here with A-10C II and Kutaisi ATC communications for taxiing/takeoff clearance/approach via VHF AM (134.000 MHz). Current OB.

Every player can transfer from Steam to the DCS Standalone version easily. If you have a problem with DCS via Steam, just transfer.

Maybe there is an issue on your filesystem. Run chkdsk c: /f /r /x in your windows console as admin to check and repair the drive. Replace "c:" with your DCS installation drive letter.

Did you try to repair your DCS installation via Steam?

Take a look:

Yes, sadly some (but not all) of the assigned bindings got lost. I had to re-assign them (for instance: pilot salute, wing sweep, flaps, speed brakes, landing gear).

That's wrong. Space stabilisation works - at least in the current OB. Select any MAV and make sure that the MAV page is your SOI. MAV should be in boresight. Move the hog nose around, the MAV HUD indicator stays centered. Then press & hold down DMS fwd to stabilize the MAV seeker. Moving the plane now doesn't move the MAV seeker, because he's stabilized. Uncage the MAV seeker to try again, if the MAV got a valid lock. Not every single new implemented feature has been announced in the patch notes. A-10C-II-SpaceStabilisationTest.trk

Space stabilisation worked already - at least shortly after implementation. I'm unable to test it now, but I've tested it earlier and it worked as shown in Wags tutorial:

Thanks for providing this cool chopper! I'm excited to see the difference to Jane's AH-64D Longbow

AFAIK: yes. I didn't notice the issue with the drifting A/G target designation by HMD since months.

No problems here with HARM in TOO mode. Already tested with 3 targets. Switching and hand-off worked as usual. Latest OB (2.7.6.13133). Make sure that your HARM display has TDC priority. Maybe you can upload a short trackfile.

Check this out:

Kneeboard v1.3.0 updated: added kneeboard pages with simple, white background to the .zip for better readability (19.09.2021), thx @Desert Fox for suggestion. Just download and open any version of my tables in the first post and look for "SA-5"

Thanks for your feedback. That's a great idea. You can download the updated .zip file including the BW version of the kneeboard pages in the first post.

If you attach your mission, the experts can take a look and find the error.

Well, this little cosmetic issue has been fixed in one of the previous updates. The station identifier does now disappear after turning off TACAN, as well as bearing and range information. Thx @BIGNEWY & Co!

In the following track I tried to demonstrate, that it's impossible to remove an existing AG designation to make the MAF-F seeker proper slewable and get a lock subesquently. FA-18C ATFLIR AGM-65F 05 slew but no lock.trk I cannot estimate if this is a bug or like IRL or just inproper implemented.