jaylw314

Are you sure you remembered to turn the EAC switch back on? Apparently, this was added as realistic behavior a minute after touchdown

Other random ideas/reasons laser doesn't turn on or work as expected: laser ran more than ~20 minutes/forgot to turn it off previously forgot to turn laser arm switch on accidentally turned off Laser button latching on TGP TGP laser masks near limits, even if video is still visible. Nothing mirrors your case, obviously, but for sanity checking. Otherwise, I rechecked it a couple nights ago and the laser seemed to work fine

Dammit, man, that would make too much sense

That's probably the best one I've seen yet. Suggestion -- in the coolie hat section, BOLD the long actions, not the SOI actions. At first glance, it makes it look like SOI HUD/HMCS are long actions because they're bolded like the "L"

The gun boresight circle for me is at the very top of the HUD (actually a little bit above it), so I have to lean forwards to see it. I think that's the proper seat position. On the ground, the top of the HUD is just below the horizon. The position of the pipper itself depends entirely on the aircraft attitude and slant range to the ground, so it's not a good description of what you can see

I don't think the curves matter so much, you probably just had something else in your brain that just 'clicked' on Next step is to do it with the AP off! It's not that the AP is doing it for you, but it is doing the counter-corrections for you. Without it, every move needs a counter-move immediately after it it. So if you're low, pitch up a bit then immediately pitch down the same amount, then reassess. Kind of like changing lanes on the highway--you have to turn left, then turn right to change lanes.

I believe that is an issue if you are using the button bindings for up/down. If you set your spring wheel to the radar elevation axis there is no ambiguity and it should read correctly. You may already realize this, but in SimApp Pro, you can change how your throttle reports that axis, either axis, buttons, or both axis and buttons.

Yeah, there's not much in the way of specifics, but it's at least one public mention I could recall. Of note, he does go into at least a little detail around 13:30, noting that without brakes, taxiing might get up to 40-50 knots, but that's not terribly specific either. Still, at least a reasonably good guess that with less than 4000 lbs of fuel and no armament, there should be at least some movement at idle on the ground. LOL, I'm not actually trying to break the record for the most "at least's" in one post

Check EVERY column in the Antenna Elevation up/down button bindings. If you have a centering switch somewhere accidentally bound to Elevation up or down, it'll stay stuck in that direction.

At precisely 11:19, the pilot mentions "at idle you need to stand on the brakes the whole time"

IIRC, the fuze options for those are on some other modules, maybe the Hornet or Viper, I can't for the life of me remember which

That's why it's a good policy to stick with neutral on public forums, even if I do take one side or the other IRL I would definitely love to visit Belgrade and the Balkans, but I'm hampered by having a spouse who would prefer see all the traditional tourist countries so the good news is the museum will probably be open again by the time I make it there!

LOL, nice little slide-in political statement there. IIRC the International Court of Justice called it a lot less flattering things to other parties, so I was generously neutral calling it the "Balkans conflict" That's an enlightening museum piece though. I hadn't realized there was a third mode that would fall back to loitering.

"This conflict..." ? If you're pointing out it was used in the Balkans conflict, I know the ALARM was used, I was just wondering if the loitering mode was ever known to be used

I always thought the idea of ALARM's loitering mode was fantastic for that reason, but I don't know if it was ever used in practice.

I kind of get it for archetypal symbols, though, the kind that are intended to communicate something to everyone, no matter the language or culture. Once people starting seeing it elsewhere in the wrong context, it can culturally dilute out its meaning. Kind of like having a kids' game where you have to eat stuff with biohazard symbols on it, so the air force roundels wouldn't really be a good example. I know that may sound like an excessive Health & Safety take, but that's kind of what I do for a living

The TF-51/P-51 is probably not a beginner-friendly aircraft for those without a clear understanding of how ailerons/bank/turning relate to each other If anything, the A-10 is probably the most conventional aircraft, in terms of learning to fly, among the mainstream modules. Trim, roll/yaw coupling, and stall/spins are all pretty much what you'd see in any basic trainer, and everything is generally pretty docile and noob friendly. I'm not counting the C-101, I've heard that's brilliant too, but not as many have or use it AFAIK

If you select a waypoint that is a "target point" as the current steerpoint on the UFC, it will automatically slave the TPOD to it. Target points are in the format "X." instead of "X" Alternatively, you can press PB17 on the TPOD screen and it will cycle through all the waypoints and point the TPOD to them in turn.

You could use either or both for asymmetric loads, but chances are you'll just use one since it's usually temporary, and the FCS will compensate some for the other axis. For a long sustained flight, I suspect you'd use both to minimize drag from any asymmetry

I'd just drop the gear and flaps all at the same time. That way you have to make a big adjustment just one time, instead of a bunch of big adjustments at every step. Just drop them all, and anticipate the push forwards to keep the FPM on the horizon until speed bleeds off. Then start trimming for AOA and don't move the stick in pitch anymore, because you don't need to make any more big adjustments. FWIW, Case I patterns are easier because you only need to fly the glideslope for 20 seconds I'm kidding, of course, it's still all difficult!

Just to clarify, that statement 45 kN "when firing at its maximum rate" is deceptive. The "firing at its maximum rate" suggests its the sustained recoil force when the trigger is held down. That figure appears to be the maximum instantaneous recoil force, which would be the same whatever the firing rate was (or how many rounds fired). Since the round only applies an impulse to the plane's momentum for a fraction of the time between rounds, it doesn't change the momentum of the plane by 45,000 kg x m/sec every second. Instead, the sustained recoil force can be easily calculated if we assume each round is 0.3 kg, the speed is 670 m/sec, and firing 60 rounds/sec, the sustained force is more like 13.5 kN. That doesn't include some small additional force from gases being blown forwards, but still much less than 40 kN.

Urrrgh, you guys are killing me; you guys are talking momentum, not energy The momentum calculation is the correct approach, and luckily, the units don't really matter if you compare the two, but don't call them ft x lbs or energy! If you lose 1/12 of your momentum, you lose 1/12 of your speed, so that's a drop from 350 knots to 320 knots over 18 seconds (level with engines idle). That's pretty trivial compared to engine power and diving I think. Sorry OP -- waaaaaaaay OT

The MAV page can be a little confusing. If you move the seeker somewhere by slaving it to something else (like the TGP or TAD), the Maverick seeker stays pointing in that direction but is not actually tracking anything. In that case, you need to press TMS Up short to tell it to start tracking something, then you can fire. OTOH, if you move the Maverick seeker with the slew controls, it will start tracking something when you let go immediately. Of course, whether it tracks the correct blip on the screen is the source of much heartburn... @ASAP detailed this in his soliloquy above, it's worth a read again

Uh, so as a sanity check, are you SURE it was uncaged? The video is at night and not possible to see if the cage flag is up

@Rickshaw This is what the red dot should do. Brake pedal up: nullBrake pedal down: FYI, you need to move the pedal, otherwise DCS starts the tuning panel with this until you do: Because it's, well, DCS. Specifically, make sure the two "In" numbers go from -100 to +100 through the pedal range (if your Saturation Y is set to 100, the "Out" should also have the same range). If it doesn't, your hardware is reporting it wrong.