Emmy

The V2 HUD looks vastly superior.

Your OP says you’re trying to refuel from a KC-130 Hercules. You can’t get gas from a Herc in a Hog.

Exactly how would this manifest itself in the sim?

The 161st ARW out of Phoenix often supports Red Flag so how far do we really want to expand the map?

Put it on the knee board a la the Viper

Nothing should be able to stay in control with one whole wing gone (except maybe Israeli Eagles) but I’ve gimped home with as much damage or more as what’s in the second image.

Hog can't refuel from a KC-130... There is no "Boom" ... Only baskets. You need a KC-135 (and not the MPRS version)

I'm good with the kneeboard option, for now...

I'm not able to get to presets 2-5 on FM, or AM. I can get 1, but when trying to spin the notched wheel, it wants to jump straight to preset 6. This is by both mouse clicks and via bound inputs.

I agree. I think the line of the "pilot's" spine needs to be moved back a virtual 6" or so. I did run the seat up a little higher which helped with the heading tape, but as mentioned above, the top row of the MFCDs wasn't able to be seen without leaning forward and down so I had to lower the seat back down a bit and settle for having the heading tape just barely behind the HUD camera.

Feels like the seat was moved 6-8” closer to the instrument panel but I feel like I’m now 6” shorter sitting in the pit. I thought our eyeline was supposed to make the two bolts on the upper right of the HUD align?

Confirming no TTI Countdown in either Auto Lase or Manual Lase... There's only a flashing ZERO next to the "L" where the countdown should be. Track Attached. No GBU TTI Countdown.trk

Just curious but did you try higher with a longer lase time? 10 Seconds is kinda short.

TacView will give you all that data and it’s more reliable than a track replay...

Will this give the Hog MIDS capability?

Simple Solution: Place any SAMs beyond the combat radius of Vipers with only one bag of gas...

I use the time to enter a flightplan.

Like the F-117 and B-2 were. Oh, wait...

Most monitors are natively Way brighter than they need to be. I hardware calibrate mine weekly (photographer OCD) and on a Brightness scale of 1-100, my Spydr Pro wants mine set at about 20 with Gamma at 2.2. DCS looks just fine. Gamma is not an overall luminance adjustment btw...

I've always looked at this 180 degrees the opposite... Take for example A2G Radar: The sim engine knows where the player's jet is located and it also knows everything around the jet. The terrain, the objects, coast lines, rivers, etc. To simply generate a display in the cockpit using all the known 1s and 0s is probably not all that difficult. In my mind, this would be "Emulating" A2G radar where you can present the player with a general picture of what is in front of the jet. Now on top of the above, throw in all the vagaries of period-specific electronics, weather, operator error, false echoes, side lobes, "birdies", etc. and NOW you're starting to get into "Simulating" A2G Radar which includes all the imperfections and limitations of an overall system. I suppose it's just semantics, but that's how I've always approached the concepts of Emulation Vs Simulation. Just to take it to DCS specifics: The A-10C is closer to simulation while the Flaming Cliffs F-15 can only emulate what the Eagle can do.

But that’s “only” range to the original steerpoint.

Makes sense. Thanks...

Noticed there was no range information on either the HUD or the MAV Screen on Wags' second attack run... Correct or did something get overlooked in development?

Sounds like the same issue we’ve seen in the A-10C where the TGP is blinded by something (smoke? heat?)when you slew near a recently destroyed vehicle.

Asked for this myself a while ago, but it never hurts to beard the lion again.