GrEaSeLiTeNiN

Seems to me that all our requests to fix the core and AI and bugs are summed up and realised in the development of a good workable DC. That is a monumental task. In 5-10 years maybe. I'd be surprised if any earlier.

I have a standard Warthog hotas. The stick's BTN 19 (thumb) was mapped as the AAR button. It works fine in the sim. But the Saved Games/DCS.openbeta/Config/Input/F-4E-45MC joystick.lua file does not show BTN19 with AAR. In fact BTN19 is simply missing in the lua file (see attached). This is not the case with other modules where any mapping for BTN19 shows up correctly in the joystick lua file. Joystick - HOTAS Warthog {2EF099F0-EFD3-11eb-8002-444553540000}.diff.lua

STOP EXPANDING and START FOCUSING/FIXING, is what ED needs to do.

Pg 261 Chuck's Guide Kh-25ML procedure + some SP testing: Player's Kh-25 will follow any number (1, 2 or 3) that he selects on his laser code selector knob. Didn't seem to matter. But when buddy lasing between BS3s, I presume both players have to have the same laser code number selected as the missile will follow the code set by the one launching the missile.

Yes, I noticed that too. Seems this bug has been around for 5 years already (as reported here with the F-14). But I wonder if it occurs with non Heatblur modules as well (did not test).

I am a bit out of touch with the BS3. So, in MP buddy lasing between two BS3s, am I right to say it does not matter which laser knob selector position is used since you can't select a 'code' for the Kh-25ML anyway?

Easily repeatable. Is this due to the old DCS bug reported here that refuses to be fixed?

I see a bunch of these old "backup.0XX" folders and they mostly contain lua scripts. What are they for and can they be safely deleted?

I'd have to agree. +1 often means the person is experiencing the same bug to show dev it's not an isolated issue, or simply bumping up the issue because it does not seem to be getting attention or acknowledgement. It's a way of ground feedback that saves repeating/rephrasing the issue. One suggestion may be to have a '+1' button on the original post though that button should have the same awareness creating effect to devs (such as 'bumping' up the issue). Sometimes, devs who mostly monitor their Discord only cause this too because they rarely reply to bug reporting here even though a forum was officially created for their module for that very purpose.

No, not in this coming update. Their last update was a small one on 11 Jul and it was the only one after launching on 5 Jun. They could at least have given us some hotfixes in the meantime.

I have pedals with no toe brakes, so I mapped toe brakes to my hotas. For me, the L/R brakes don't seem to have any effect in steering the aircraft when taxiing (the pedal braking animation is there) unlike in the A-4E mod but NWS works fine, so I don't use the L/R brakes.

Ok got it, thanks!

Manual says... Air Refueling Release Button Unique to the front cockpit control stick is the Air Refueling Release (ARR) Button (4) located on the left side of the stick. It is a dual-role control that performs the boom disconnect function its name implies, as well as a number of weapon selection functions. What are these weapon selection functions that the ARR button performs? I could not find info on them. Thanks

Just a wild guess - did you click the watch icon below in the mission editor? (It limits what you can fly based on historical accuracy.)

I hope it can be improved - at the very least the labels of the switch or button being explained should not be in the greyed out area for obvious reasons.

Since such a format was adopted, it's all over the manual, especially in the cockpit instruments sections. Here are just a few examples:

Came across this video that describes the trackfile issue. I am curious to know too.

Looking forward to Chuck's guide too. I dislike the Heatblur manual with all those greyed out photos. Not the best way to reference pit switchology. In some instances, even the text that describes the functions of the switch being taught are in the greyed out part. And if you want to see what's around that switch for context, you can't or won't bother because they are all dimmed out. The manual does not quite match up with the otherwise excellent module IMO.

I have the SA map but not the Kola. Would those who have both say the SA is better at low level than the Kola in its current state? Thks

Hi guys, I have been learning the A-4E. Really nice mod! I have some questions though: 1. What does the AoA Compensation Switch do exactly? 2. I noticed the kneeboard manual says to have the switch ON in all radar modes except for A/G mode. Why is that? Update: From NATOPS manual - "A guarded angle-of-attack switch of the two-position toggle type enables the pilot to remove the angle-of-attack compensation if the airflow sensor becomes inoperative. When the switch is in the OFF position, the zero reference line of antenna elevation is the armament datum line rather than the flight path." My understanding is that the AoA compensation switch is turned OFF in A/G radar mode for ground target ranging purposes. It's otherwise kept ON in SRCH and TC modes so that zero antenna elevation corresponds to the flight path which is right for terrain mapping/avoidance purposes.

Could they not have released some smaller updates like a fix for the MMS screen cut-offs, or the CTDs with hellfires, or even the suspended in mid-air smoke grenades? Are these fixes so intertwined with everything else that they can't be hotfixed?

I actually stopped using my hotas lever with the Gazelle but I still use it for the throttle in the UH-1H, Apache and Ka50. It works with the above axis tuning but Pg Up/Dn (or whatever keys) is probably better. I was just trying to find a use for the hotas lever

I find levers bound to a hotas axis are usable provided your hotas lever works well and is calibrated. My warthog grey throttle lever doesn't go the full range despite calibration and even changes over time. So I've set the axis tuning to 'no slider', 'no curvature', X (50), Y (100), Deadzone (0), so it always ensures 0-100% full range in the sim with adequate buffer (X=50) for when it decides to run off a little. So my lever axis profile ends up looking like a mirrored 'Z'.

The mission brief screen (top right) blocks my comms menu (top right). How do I move the mission screen away?