Pheonix0869

If you bind "clickable cockpit" toggle in general keybinds, for each airframe, that should allow you to toggle on/off. Default binding is L or R Ctrl + C... I forget which Ctrl... Sent from my SM-S926U using Tapatalk

This has happened to me, G2 user as well. I think a windows update added a similar function as steam. Check you wmr settings for something about tracking data lost. Not sure how dcs could effect the tracking of the headset, so I assumed it was our overlords at Microsoft.

Ks-19 will do this as well, now!

At some point it was stated that tankers use the same tacan as ground stations and therefore transmit on the X band. Maybe this is now forced regardless of ME selection.

Glad I could help Sent from my SM-S102DL using Tapatalk

From what I understand, you do not want to select A/A for tanker Tacans. They are similar to ground based Tacans. The A/A is reserved for "fighter-fighter" transmission and reception. So try locating the tanker without the A/A option.

+1

Okay so i did test the multiplayer aspect of the yardstick and it is working as expected, so this appears to be an AI only issue. Attached is the Multiplayer track I recorded with a second account, with the yardstick working as expected. Yardstick-20220403-193439.trk

Condition: I noticed this in Ground Pounder Sims newest campaign. Seems like the AI yardstick function is not working. Unaware if this is an MP issue as well. Probable Cause: AI never transmits tacan. Reproduce: Set AI unit in ME to transmit tacan, set tacan number (i.e. 27Y). Attempt to get yardstick information in mission by tuning to a tacan freq. 63 channels above or below the other units tacan. Attached are two tracks, one with the AI 18 set to 27Y and I attempt to tune to 90Y. The other with the F-16, same exercise. F-16 Yardstick.trk F-18 Yardstick.trk

Can confirm this, experiencing the same

Seems like this bug is back with OB 2.7.8.16140. Except the first aircraft collides with the tanker... I'll post a track when I can. Sent from my SM-S102DL using Tapatalk

Patch 2.7.7.14727 OB seems to have fixed this. Sent from my SM-S102DL using Tapatalk

I think its in the data page, lower right hand OSB of your radar DDI

Condition: I was creating a mission where several flights of 4 ship F-16s were required to refuel from a tanker prior to pushing. The F-16 4 ship will fly formation on the tanker's left wing, then the flight lead will take fuel, no problem. When # 2 tries to refuel, the aircraft will close into initial position, and then porpoise to just above the elevator of the KC-135, then collide with the rudder. This behavior is included in the tracks attached, however, I was fortunate enough to run a test where the tanker was not immediately destroyed and witnessed the 3rd AI pilot repeat the same maneuver. I believe this is included in the bl52 track file. This behavior does not occur with the A-10CII. Cause (Best Guess): I noticed that as the 2nd element closes into position with the tanker, the boom does not move / respond like it did with the flight lead. It seems the AI pilot then pulls up to avoid collision , as the boom has not been raised. The AI likes positive G, so up he goes into the KC-135 Rudder. Reproduce: Place a Tanker with a Boom on any map. Place a flight of F-16Cs (any block, CMs as well), and instruct them to refuel. Observe #2 strike the tanker when it is his turn. Repeat the process with A-10C, or any other female plane and they refuel fine. Indicates F-16 Specific Problem. F16_RefuelingBug.trk F16bl52d_RefuelingBug.trk

The post gets updated, it was last edited the end of August. Sent from my SM-S102DL using Tapatalk