Chain_1

Boresight mode in the acm modes. As an example, move the dogfight switch to dogfight and press tms forward to enter boresight mode, then look around (make sure the HMCS is powered on).

It can be, remember that the speed of sound will change with temperature. As an example, for a standard day, the temperature at sea level is 15 C. At sea level .82 Mach equates to a little over 542 knots. If we climb up to 25,000 feet, the standard day temperature is -51.6 C, and .82 Mach is a little over 475 knots, so you've lost 67 knots. If you check out the bug thread, you can download some tracks. Stay high and try different speeds. the faster you go, the longer you'll see the release cue. I don't know if the max toss symbology cuts out in the real jet to show the release cue, but this is at least a workaround.

It will if you're flying fast enough. There's a post in the bug report subforum on it. The release cue won't show until after the max toss symbology has completely played, so if you're too slow you may not see it.

It looks like the release cue doesn't appear until after the max toss symbology is complete. If you're too slow, you may not see it at all. With plenty of speed (450 knots in your track) i saw the release cue come down completely, but if i was slower (350 knots-ish) the max toss symbology doesn't disappear quickly enough, though the bomb drops when it should. Whether or not that's how it is supposed to be, I can't say, though someone more knowledgeable like @Frederf may know.

Just tried this: after manually reducing the range, use the pinky switch to expand into back dbs2. The radar was still looking at where I was before adjusting the range and the image is scaled in as one would expect.

The gun purge door animation from Wags' vid was in today's patch notes, but it isn't animating for me. Did a full repair and still no luck. Is this happening for anyone else? Track attached. If this is already in an internal hotfix, mods can feel free to delete. gundoor.trk

You are correct in that the a/a channels should be 63 apart, e.g. lead sets 29Y and two sets 92Y with both in a/a t/r mode. You should at least get distance with this set up, but it depends on the aircraft if you get bearing. I think there's an ongoing issue with a/a tacan across all airframes, because I couldn't get it to work this weekend in the A-10.

You need to keep the azimuth steering line in the circular part of the flight path marker. Every time you do that it drops. If the ASL is outside that circle, there's no drop. I guess you're too far off course at that point.

Not every plane needs it. The air required for engine start is provided by the A-10's APU.

For ours, at least, you need an external ecm pod. I also find it odd that the switches are defaulted that way, especially when no pod is loaded.

160 may be good, and it may not be. Rotation speed will depend on aircraft gross weight and weather conditions. Power setting and pitch angle also play a factor.

The issue in this track is that you have the mavericks in vis mode. If you want to use the mavericks with the tgp they need to be in pre mode. You can cycle through the mav modes by pressing the crusor enable button, or the appropriate osb on the mav display. In vis mode you have to aim and lock the maverick manually. Edit: Another issue is that your mavericks aren't boresighted. I boresighted them on a small house in one of the villages, and after doing that it works as advertised.

I'd need to see a track, then.

Make sure you're in Auto handoff mode on the TGP. The checklist you posted doesn't specify it, but you need that if you want the mavericks to lock automatically. If you're in Manual handoff mode, you'll have to make the mav soi and lock the targets yourself.

@BIGNEWY I can PM you a checklist excerpt showing we use air-to-air tacan for refueling or a pic of our HSI showing the indications we get (i.e. distance but no bearing) with a/a t/r if you'd like.

Yes, everything goes through that radio. Our other radios are used for things like ATC & C2. Even if the ARC-164 failed for some reason, the frequency would still be the briefed uniform frequency. Some jets, like the F-16, have "boom interphone" after a contact condition is established, but that would be pointless in DCS unless/until they make a boom operator minigame.

My thought is that the mission is not designed accurately (in that respect, at least). I think the same thing when people use victor for air refueling frequencies. Our a/r radio is an ARC-164, it's UHF only.

Don't look at the numbers since they may change with altitude. Instead go to external view (active pause on) and look for the fire glow in the engine; that's the beginning of afterburner. I have my throttle set up (not wingwing but the principles are the same) to where afterburner kicks in right after I push past my detent. This corresponds to the sound of the in cockpit detent being pushed through. Note that you may have to select user defined when adjusting your throttle axis in DCS and tweak it to get it exactly where you want it.

That's for the ARC-210s, not MIDS A/B. You're correct that if you are in P you will get only static from someone who is in C, since your radio isn't set up to decrypt the transmission until you also are in C. The C stands for "cipher" if you were wondering.

Current 135 guy here. It hasn't changed. We still use a/a t/r on our tacan and still only give dme. If people want bearing they need a KC-10 or KC-46 now.

You're correct on the meaning of chicks in tow, but the meaning is that OP is cleared to 1 mile trail. If the left wing is clear, though, he could go there (though not while F-16s are being refueled due to the speed difference, (200 KIAS vs 315 KIAS)). This call is somewhat ambiguous, though. Hopefully tanker comms get a rework in the future.

Same for me. The completely coupled approach I got worked fine re: pitchdown, but if I'm using autothrottle without acls the jet drops like a rock and prangs on. Sometimes the hook catches and sometimes it doesn't.

Same here, can't get it in to mode 1 on the datalink. I have good indications up until then, other than the verbal hold dme and the link 4 pointer not really aligning, i.e. told to hold at 23, but link 4 points further out into the 30s.

That's a workaround for now, yes, but the issue remains that we should be in in a/a t/r, and that currently doesn't function correctly. We'll see what the next patch notes say. Edit: Looks like this has not been corrected in this patch. @BIGNEWY what can I, or any other tanker bros, do to help convince the team to get this back to the previous correct implementation?

That's because that post is about the F-18, hence its location in the F-18 forum.