Swift.

It's T UP wherever you are, but obviously on the deck it gets funky because you could be tracking North whilst heading south.

There isnt a 'bar' between the throttles. You just move them together using one hand.

Currently you can only load these two stores separately, however it appears to be quite common that both would be loaded onto a single LAU-105. Would ED be able to add this loadout choice to allow better replication of the real jet?

By JHMQS I assume the OP meant JHMCS, which is the HMCS used by the versions of viper and hornet modelled by DCS. HMCS is a generic term JHMCS is a specific model

From what I have gathered, its independent. You have 4 altitude Alerts: HSI>AC>RALT - 'Altitude Altitude' HSI>AC>BALT - 'Altitude Altitude' Right Knee> Dial - Whoop Whoop UFC>AP>AP - Whoop Whoop They are all independent of each other so you could have the dial set to 40 ( as they often do IRL) and the APx2 one set to 1900 or something.

It does work with flaps in full though... admittedly its a poor, but it 'works'

tbf, the specific details of JDAM are also classified

You're not wrong. ED if curious, ask your SMEs about this

In its current state, I would say that's a fair assessment tbh

Kinda, if you let it settle after it initially chops the power.l, the it almost works it's just a bit slow

I don't recall him saying effort wasnt being put into Viper concurrently. Also, remember that the viper module is a lot lot younger than hornet, you can't expect viper to reach hornets level of completion for another couple of years.

We must be watching different videos then...

That's how it is in the real thing, it would appear.

The proper way to fix something like you describe would be to assign the TDC to the HUD and slew the TD onto the desired target. Unfortunately ED still havent fixed the hornets HUD cursor speed.

The cursor is too slow on the ATTK page and wayyyy too fast on the HUD and HMD.

ROS isnt an issue, its the tacan identifier. Thats expected. The TACAN turning off after a few hours of use is a long running DCS bug. You've correctly found the workaround already.

ROS will be the TACAN identifier set by the mission creator, most like Roosevelt here. The strange large number is probably because of the TACAN bug where it turns off if the mission has been running too long.

Yeah all that SRS needs for this to work is just a cycling text field when you press the button. The actually ciphering of the radio and KY58 operation can remain non functional.

If you assign the TDC to the HUD/HMD with no previous designation, then you will see a dashed circle appear in the HMD. Place this circle over the target and depress TDC to designate that point. Once a designation has been made, everything will automatically slave to that point, so the TPOD will be looking there and when you press the MK button on the HSI it will create a markpoint on the newly created designation.

The fact that the HMD shows a GO on the BIT format is misleading then. If it requires a BIT it should say so.

Most systems in DCS hornet correctly clear their NOT RDY status when power is applied to them, with the exception of: IFF D/L MIDS DMS and potentially: LTDR CLC BCN will remain OFF as the UFC menu for it has yet been integrated, but I'm pretty certain the WPNS DEGD should be more like OFF or NOGO if not PBIT GO. BITs.trk

A pretty fundamental feature that we are currently missing is the ability to choose which of the two ARC-210s the KY58 acts upon. This really really basic logic will have huge impacts onto gameplay whilst using SRS and will be critical for when the ED VOIP system becomes more fleshed out. Basically, when you press the CPHR button on the UFC radio format, it should cycle CPHR > :CPHR > :CPDP Allowing only 1 radio at a time to be the ciphered radio and thus the target of the KY58 encryption. Additionally, should our hornet feature the ARC-210 DCS radio, we should be able to select these options on both radios independently of each other, as the DCS allows embedded voice ciphering without the KY58. My best research into the introduction date of DCS indicates it had been installed by at least 2002, so definitely something in our hornets time frame.

I think this is related to the recent bug where TOO targets aren't being retained by the weapon when you undesignate. I believe we're still trying to convince ED that it's a bug.

Is this question about the differences between the DCS Modded Superhornet and the DCS Hornet. Or between the actual Superhornet and actual Hornet?

Once ED correct the FM, you should looking at 4.2 AOA best range 5.6 AOA best endurance Or roughly 300 and 250 CAS respectively. AOA is the much better method and is the gouge used irl.