Chain_1

Especially considering that ED is actually working on the DTC, according to the roadmap.

To make it easier on yourself use 3000' at 10 mi (1 deg = 100 ft/mi) since math kills lift. If you look into the 60:1 rule, there's a bunch of things you can mentally figure pretty easily if you round a bit, i.e. 1 NM = 6000' instead of 6076'. It's all close enough. Technique only.

Check out the community keybinds mod, it has slower options for you to bind.

Use the landing light for takeoff/landing, and the taxi light for taxiing.

razo+r is correct, you were looking too low with the radar. A fighter's radar isn't an all seeing eye, for want of a better term, it can only see in a cone. It won't detect anything outside that cone. This tool (https://tawdcs.org/radar-f15/) was made using the F-15's radar, but the principles are the same. Use it to practice locking contacts, and that will help your understanding of the system.

I was looking around yesterday and it looks like it's not a bug.

I just tried it in MT and ST and the NCTR worked as advertised in the training mission. The unknown IFF return did not show in either though. Have you tried a repair?

In the meantime you can also use this: https://www.digitalcombatsimulator.com/en/files/3312680/ You set up your programs under the special options tab so you don't have to mess with the CMDS pages every time.

Brick visibility was the OP's issue, but you are correct in that the terrain was not displayed by default in GMT/Sea pre-patch.

Just tried your replay in MT and both worked as advertised. The issue was needing to turn down the map gain under the data page (like in the Viper, if you have that). The GMT bricks blended in with the terrain until I turned it down.

You also should make the Mav SOI and TMS up on the same object you're looking at through the TGP so that it's locked, then hit BSGT

Negative. The F-15C does it perfectly because it is a lo-fi aircraft. You'll have to manually spin the HSI in the A-10. That said, the waypoints can cycle automatically in the HUD/on the TAD.

It's an intro level vid, but it's up now.

Double check your control axes for any binds. I have the HUD/JHMCS brightness bound to some controller axes, and if i move those controls after a hot start that will cause the HUD or JHMCS to instantly turn off and then back on while the game matches the physical axis position, and it looks like what you described.

Looks like I misremembered. I was thinking of stepping through the missiles, the boresighting works as you say. I just tried it.

If memory serves, this is an ongoing issue. You should only have to boresight each rack, but currently you have to do each individual missile.

Not enough by itself, there would be procedures in the SPINS/ROE that would address such a situation and hopefully prevent friendly fire.

Hope she sees this, bro.

There are certain conditions which will disconnect the autopilot. What were your flight parameters at the time? If you put the gear down or set the air refuel switch to open, for example, it would disengage. I couldn't get it to disconnect just by going to the F10 map.

Closest you can get is to select A-G master mode and use the missile override/dogfight switch to swap back and forth quickly.

A/A Tacan hasn't been corrected yet.

The community keybinds mod has multiple options for antenna elevation with different speeds. Give that a shot.

You need to depress and release the scs first, then quickly scs right.

During. Go into active pause, select dogfight mode, and shoot. You'll see the door open.

Check out the community keybinds mod. The settings you're looking for may be in there.