Swift.

Best bet would just be to leave FD alone I think

In my experience it works alright for level med to high altitude delivery. There was an odd thing with climbing deliveries, where the LAR was changing shape but not accurately representing the actual capabilities but I can't quite remember the bug. Additionally it's possible (I wish) that the low altitude LAR inaccuracies have been modelled properly

Can we have some single action bindings for the Parking Brake and Emergency Brake? So that instead of for example: CCW and Pull. We can just bind Parking Brake ON, or Parking Brake ON else OFF, or similar? Would be super helpful to those with physical cockpits built up, who don't have the complicated Parking Brake handle mech that the real hornet has.

Is that LUU-2 or LUU-19 that will be detected by a heat seeker? LUU-19 should also be carried by our hornet, but would require a bit more 3d art work, than the LUU-2.

That'll be because FD mode (not yet implemented) can be used with the AP via the same CPL. Does it return to normal when you select MAN or AUTO?

Related aswell

Your stick has to be perfectly centred for it to engage. I've been asking ED for an option to loosen this engagement zone, but what we have is what we have.

Alright thanks for trying, maybe the root cause will be eventually be uncovered organically anyway. Its not like its a major impact on the day to day.

I had a little bit more trouble reproducing it today, took more than 2 attempts for it to fail. See 1:13 in the video for the failure mode. I'm fairly confident its not my undesignate button as the pressing of that button will remove the TGT symbology from all displays other than the HSI. If the button was broken I'd expect it to do nothing. The track still works and shows the error state after 2 attempts.

I'll create an accompanying video tonight, to help demonstrate things. Thanks

And not just that, but whether or not the pod drifts is dependent on whether the pilot attempts to slew before pressing TDC. This is not a report for an inaccuracy in the modelling, but simply a report of a breakdown of logic. Having the behaviour change due to unrelated inputs prior to a sequence of events is a good and proper bug in the code.

That is correct, what I'm seeing is it staying as TGT

How fast are you when you are trying to trim? If you try to trim onspeed at 200 kts, you are going to nose up to the moon

It must be, considering how all the SMEs are saying the rotor doesnt have enough inertia

When engaging LST from VVLSV, the pod LOS will remain fixed at the point the VV was facing at the time of LST activation. Deactivating the LST will make the pod display the video pointing at that location, but will continue to show VVLSV symbology in the display. 1. VVLSV the pod2 2. Enter LST 3. Move the jet 4. Exit LST: Observe the Pods orientation relative to the VV VVSLV LST.trk

ATFLIR will enter INR SCENE erroneously. EDs manual defines INR SCENE as: INR SCENE. The ATFLIR enters this mode when the pod is slewed while in SCENE mode. The ATFLIR will enter SCENE mode again once slewing is complete. However in DCS it will be shown when in normal INR mode and attempting a slew. 1. Designate with TPOD 2. Go to SCENE mode 3. Undesignate: TPOD goes to INR mode 4. Slew: TPOD goes to INR SCENE, despite it not attempting to acquire a SCENE track. INR SCENE.trk

ATFLIR will drift when you slew before depressing the TDC to 'unlock' the pod from the waypoint. However, if you dont slew before TDC depress, it wont drift. 1. Designate WP 2. Slew 3. Depress TDC 4. Slew and release: Notice the pod drifts as if in snowplough 5. Redesignate WP 6. Depress TDC 7. Slew and release: Notice the pod stays fixed as it should Drifting.trk

ATFLIR will continue to show the Designation reticule (diamond) despite there not existing a current designation. 1. Designate using the TPOD 2. Go to SCENE mode 3. Undesignate: notice the reticule reverts to the designation reticule, not the INR crosshair DesnotINR.trk

With ATFLIR, the second undesignate action will not remove the TGT indications from the HSI. 1. Designate WPYT 2. Undesignate 3. Designate WYPT 4. Undesignate: note the HSI still shows TGT rather than WYPT on PB11 2nd Undes.trk

Less than a degree perhaps, but 25% aswell... Having tested this extensively in DCS, I can confidently say that the relation between speed, fuel burn, and AOA is not correct in DCS. How far out it is and what the correct path to fixing it is still TBD. So whilst yes, it might be that its more like 3.9-4.5 IRL (which I doubt but anyway), there are no numbers that can be used in DCS to fly range or endurance profiles as a ROT. Because it varies so much.

I saw that we got the special option to negate the trigger guard, allowing us to use a single button for the trigger function. Which is great! It would be similarly super to have that option apply to all the covered switches on the HOCAS: Chop, Jettison

You can turn it off, the options is called 'PEDALS WITHOUT SPRINGS AND FFB'

The flats and slats are not driven randomly, it's a known scheduling that can be accounted for and is accounted for when NATOPS tells you to fly at 4.2 for max range and 5.6 for endurance.

Unfortunately not in DCS. Its not a fixed relation atm, you'll see range at about 3.2 to 4.0 ish, depending on weight. Tnd endurance about 5.6 to 6.5 ish, again depending on weight.

The fuse could be set to OFF aswell