GrEaSeLiTeNiN

A ratio of 4:6 or 0.66 seems to be the recommended. I try to create kneeboards that don't need zooming in to see the info if possible. Such as the commands for George at 2240x3338 (0.67) 1.5MB - could have been smaller. Some other examples like the popular Case landing procedures for the Hornet by Dmitriy which have very detailed text are at 1358x2048 (0.66) 409KB. Those you'll need to zoom in to read. So it varies and depends. Even if the ratio is not 'correct', the game seems to fit it in but it will be distorted. (Has to be in png format.)

Before the release of the Apache, ED shared a diagram of the AH-64 HOCAS. Is there one for the F-15E, at least for the pilot? Can't seem to find one anywhere.

Like the Apache, one Warthog hotas with one modifier. Hopefully that's enough for the Strike Eagle. Don't intend to WSO if I can help it in SP. It's unlike the Apache where you can fly and fight as CPG with unblocked cockpit view.

Latest Open Beta as of 8 Feb 2023. Can't get triangles to show in HUD with the TGP method as was demonstrated in Wags video here. OA1 is always in the wrong place. Trk included. What am I missing? Similar problem reported here I think but not sure why it was closed? Thks DCS F16 OAP TGP BUG 8Feb2023 Latest OB.trk

They also didn't fix the bugged cargo position indicator when this feature was still available. I think a mod, if doable, is the only way to have a properly working sling feature. But is the sling feature available if you pick the 2011 version of BS3 via the ME?

For my own reference, I have it down as this...

Old thread revisited. ED Manual says: "...This is done by transmitting a coded signal aimed at a specific radar contact or volume of space within the selected radar azimuth and elevation. Transponders in friendly aircraft receive this signal and reply with the correct coded response... The IFF system is not radar dependent so interrogation of contacts is still possible with the radar off. Scan. Press TMS Left short (1 second or less) to interrogate all contacts in the radar scan volume. Line of Sight (LOS). Press TMS Left long (more than 1 second) to interrogate the locked target or immediate area around the radar cursor." Some questions - I found the following after testing latest OB as of today (track attached): 1. IFF SCAN Seems to interrogate whatever is in shown in the radar MFD display including contacts outside the Scan Azimuth setting. Is this not scanning outside the "Radar Scan Volume" which is contrary to what the ED manual says? Or have I misunderstood what "Radar Scan Volume" is? 2. IFF LOS a) What exactly is the "immediate area around the radar cursor" that is to be interrogated? It seems some contacts that are quite 'far' from the cursor are also interrogated. Has this got to do with the way contacts are represented in the FCR where contacts in the radar cone are spread out into the square of the display. b) In fact the radar cursor can be at the bottom of the display and it will interrogate contacts at the top of the display (eg, 40nm) that are in its LOS. This is not the "immediate area around the radar cursor" as the manual describes. Should the manual not add "contacts in the LOS of the cursor" as the name implies? c) Contacts outside the Radar Azimuth gates are also interrogated if they are 'near' enough. Does this mean IFF LOS does not depend on Radar Azimuth settings? 3. Not sure how Radar Azimuth and Scan Volume are involved if IFF does not require radar. Appreciate your feedback. Thanks. UPDATE: Based on Bogey Dope's tutorial, IFF LOS is an "in line" of sight interrogation as opposed to "immediate area around the radar cursor". But it works both ways in the sim including interrogating out of LOS but near cursor contacts. IFF SCAN on the other hand "scans the entire view of the radar" which I suppose means the same as "radar scan volume" because contacts outside the azimuth gates would have dropped off in the display if I had waited longer (see track). So the azimuth setting acts more like a filter in the declutter sense. Although radar is not required for IFF to work, you need it to see the contacts and their response in the radar display. DCS F16 IFF SCAN LOS TEST 4Feb2023 Latest OB.trk

Have a look at this thread here.

There's that option (...) on the right side of the ME page to select your preference. I think if you select Auto and your mission is at night (not sure what the exact hours are), you will get the NVG. When you are already in the mission, only the ground crew can change it for you.

It's for convenience when you are Pilot or CoPilot (nothing to do with rear crew). Currently, if I am Pilot, I have to map a button for unhook (= "External Cargo Pilot Unhook"). When I am CoPilot, I have to map another button for unhook (= "External Cargo CoPilot Unhook" since "External Cargo Pilot Unhook" will not work and vice versa). If they allowed us to map "External Cargo Unhook", then one button would have been enough as unhook with this command works for both Pilot and CoPilot. Not a big deal, just wanted to save buttons on the hotas. I mean it would have been neat to have that option.

The explanation in the OP was missing. Please read OP.

The "External Cargo Unhook" is not mappable to the Hotas. One has to use either "External Cargo Pilot Unhook" or "External Cargo CoPilot Unhook" (aside from auto unhook) depending on where you are seated. This means two key binds or a modifier/switch. "External Cargo Unhook" via keyboard works whether you are in Pilot or CoPilot seat. So it would be great if they allowed this command to also be mappable to the hotas.

Latest ED updates have not fixed this as of 30 Jan 2023 (Open Beta).

My guess is no function. Sometimes the manual will explain it just for knowledge/info though it is not simulated.

the real thing for comparison...

+1

Not a weapon of choice as you end up getting close to your target area

ED has many aspects of the Apache module to model and test. So I suppose if ED tested their model of CMWS as much as an ardent consumer would have, in various surface-to-air scenarios, and feel that getting shot down often by manpads is plausible and that the system is as it should be for DCS World, then that's that. Otherwise, they could perhaps take a second look.

Probably a perception thing - I think when auto hover is done at a higher altitude, it 'feels' more stable (stays in place) then when done near say treetops or buildings as there is a visual reference for actual displacement in the latter.

Not resolved... the pilot gets the golden buzzer though

Title says "fixed" but that is not true to the OP. The cycle switch functions that were there before have still not been put back. Is ED planning to have them permanently removed?

Anyone find the auto hover is not as "magical" as before?

Did a simple batch file to delete those 2 folders @RD /S /Q "C:\Users\username\Saved Games\DCS.openbeta\fxo" @RD /S /Q "C:\Users\username\Saved Games\DCS.openbeta\metashaders2"

The impression one gets in the 2023 vid is that they made an effort to show you what's coming in 2023. Like they kept showing the Corsair and F4. So when the FCR wasn't in (surprisingly), I guess some ppl started wondering. If it comes in 2024 (not saying it will not come in 2023), it will be another year's wait and quite a letdown I'm sure to those who bought the Apache on day one. Come 2025, you'll see a great new year vid of some upcoming modules and then probably wonder when they'll finish up some missing system in the F4 or Corsair. But that's how it is with more and more EAs. Update from their 13 Jan 2023 Newsletter: "The FCR is one of the features that significantly adds lethality compared to the older A model. The FCR will be able to scan for, detect, classify, and cue weapons to both air and ground units. This will be one of our team’s larger tasks for 2023."