jaylw314

I think I recalled the mission asking you to change the transponder to Norm before takeoff. IRL in the US civilian ops, it's been a thing for transponders to be turned on prior to taxiing, I suspect this is now the case in the military to.

I've actually found that even with the TGP pointing at an object and slaving the MAV to the TGP, it will still occasionally lock onto something nearby when I press TMS up, so there's definitely issues. Whether the issue is realistic or not is up for debate, I suppose.

In the realm of pedantic error-finding, I noticed Biff says HSI stands for "Heading Selector Indicator," instead of the correct "Horizontal Situation Indicator"!

It's a pressure check for the refueling receptacle. After refueling and closing the door, the receptacle is pressurized with bleed air to check for leaks and to push the remaining fuel in the receptacle and lines into the left (I think) internal tank. The light comes on when the system is pressurized for about a minute, then turns off as the system slowly pressures down. If the READY light does not come on, or only stays on for a few seconds, you have a fuel leak or damaged refueling door. I believe this only occurs if you've actually taken fuel, I think it does not occur when you simply cycle the door The same pressure check occurs when you press the LINE CHECK button before refueling. If the READY light fails to come on or stay on for more than a few seconds, you have a fuel leak and is a no-go for AAR

Can confirm missions where A/A TACAN used to work does not work for distance anymore

A specific scenario I can think of would be a defended target (SHORAD and MANPADS) that needed taking out in close vicinity to friendlies or civilians. While you could point your TGP and slave the Maverick, the resolution of the seeker is way too poor at standoff distances to ensure you're hitting the correct target. While I'm sure we've all yeeted AGM-65's when we've gotten the seeker to lock onto SOMETHING at 10 nm, when you can't positively ID what the seeker's locked onto, it doesn't give you a warm and fuzzy feeling when you know there are friendlies 200m away. On the other hand, the TGP and laser ensure you can accurately pick out the correct target even at max standoff distance (admittedly only 8 nm). And you have no other PGM that has such a standoff range. Even better if you have somebody else with the laser, either a JTAC on the ground or an F/A-18C at Angels 30 above the altitude range of the air defenses.

Yes, the TGP camera can track over a much larger range. In particular, elevation is limited to about -15 degrees elevation (below the plane of the wings) off to the sides, although you get up to +20 deg elevation once your azimuth is within 30 deg of the nose. Incidentally, this makes the strategy of turning away from the target impractical at low to medium altitude--you can't fly straight and level without masking the laser, you MUST stay slightly banked away from the target, more so if you're lower, so you'll continue turning away. If the weapon TOF is too long, you'll eventually have to keep turning until it may get masked in the aft blind spot. You also can't turn back into the target for precisely the same reason. Best is to turn only about 60 degrees away from the target immediately to avoid overflying, then stay in a 5-10 degree bank away until the weapon hits. The problem is less with weapons with short TOF (GBU-12) and less with higher altitude. Flashing M (and flashing crosshair) means you're near the laser limit, solid M and solid L means you're masked (and hosed if you were guiding a weapon). The M and L cues are mirrored in the lower left section of the HUD so you don't have to stare at the TGP. Worse yet, POINT track seems to have an even smaller area that I've never quite gotten a good sense of.

The laser only has a range of about 8 nm. At that point, it actually produces a laser spot in the air if it hasn't hit the ground yet. That's why the laser Mav is tracking something, but at the wrong range. It's also why the TGP gets stuck at 8.1 for some distance. At some further distance, the TGP laser ranging does weird stuff, and I think the intention was to have it switch to using GPS slant range past 12 nm of actual slant range, but something got messed up because I've seen the distance run off to 300 nm until you turn the laser off. TLDR, it's a laser ranging issue in DCS, not a AGM-65L issue.

Oh, come on, they did it in Tom Clancy's "Red Storm Rising" That counts as unclassified material, right Actually, now I'm not sure if it was that book specifically, but remembering a Soviet SAM taking out some guided bombs in one of those Tom Clancy books from the 90's...

Make sure force feedback is turned off in the settings menu. I think changing or adding USB devices sometimes seems to trigger this.

The skin is already done? https://www.digitalcombatsimulator.com/en/files/3317479/

Don't forget DCSkneeboardbuilder. It allows you to manage all the various kneeboard images and import PDF documents easily. Incidentally, there are 4 categories of kneeboard that are lumped together in your DCS kneeboard: Global Map-specific Aircraft-specific Mission-specific Each folder is located in a different location, which is annoying but the above app allows you to add and remove images easily to each folder

Late to the thread but here's the wikipedia link: https://en.wikipedia.org/wiki/Nicosia_International_Airport TLDR It was going to be the main, modern international airport for the island before Turkey invaded in 1974. It ended up in the UN Buffer Zone between Cyprus and North Cyprus, so it was abandoned, and Cyprus' main airport is now Lanarca on the south coast. North Cyprus built Ercan as their main airport, but nobody recognizes North Cyprus except Turkey, so only flights from Turkey can land there. Historically, Cyprus is a VERY messy place!

No. The clock is supposed to be controlled by the instrument light dial IRL, but for whatever reason it is not. Not sure about the UHF repeater, but it's reasonable to assume it also is supposed to be controlled by the instrument light dial.

Hah! That's because I got the two functions mixed up, I was actually thinking about markpoint Z nice catch on my booboo For the IFFCC SPI submode, the most obvious use for that is if you're running in with guns or rockets, and want to do a quick visual ID before you brrt, you just set the IFFCC SPI submode, then slave the TGP to SPI. Now you have a quick way to visual ID your target before you get too close. I know it's a strange workflow, since in DCS we've usually got our faces glued to the TGP before running in, but I suppose before we had the HMCS, it could be useful if you found a visual target and didn't have time to slave the TGP to it before running in

Yes. If you spot a target of opportunity in the HUD and fire at it with guns and rockets, you can slave the TGP at it to reattack if you miss, or get the coordinates to relay the location to somebody else if need be.

That has been brought up previously, and so far the answer seems to be that is the view for the typical pilot position IRL. I have to lean forwards a bit to see the boresight circle. I don't mind, since I can see over the nose better. I have no idea if that is correct IRL, though.

For clarity's sake, when you say winds at 223, is that FROM 223 or TO 223?

Many airfields with an ILS have a non-precision Back Course approach based on the localizer. It's reverse-sensing, of course, but with an HSI that's a trivial issue. Alternatively, if the weather allows, many ILS approaches have the option to circle to the opposite runway once you break out of the clouds. Usually the weather to do this needs to be much better than the default ILS approach, though.

IIRC, some of the runways with listed ILS frequencies do not actually have them (annoying). Make sure ILS is selected on the NMSP. Remember, the yellow bars on the ADI are NOT your CDI and glideslope, they are (I think) flight directors. The CDI is on the HSI course needle, and the glideslop is the little arrow to the left of the ADI

Agreed, it's not just your imagination, although I'm unsure if it's specifically an A-10 change or something related to DCS World audio

That doesn't sound great? The A-10C displays waypoint altitude visually on the HUD and HMCS, and if flight waypoints were on the ground, you wouldn't be able to see them when you're at altitude. It also would mean a headache if you wanted to use vertical navigation (not that I ever do)...

I noticed in the dash-1 published in 2012 (Suite 7A), the reference to the button that deletes markpoints has a black bar next to it, which is an indication that part of the manual was changed since the last revision. However, I don't have any previous revisions to compare to

In the Mission Editor, the waypoint altitude is arbitrary and needs to be manually set In the cockpit, creating waypoints always seems to result in the elevation automatically being set to 0 AGL. I've never seen it do otherwise. I can't test it now, but are you entering waypoints before the EGI is aligned and selected? Are you happening to copy waypoint zero (INIT POS) when you are making a new waypoint?

You can use Joystick Gremlin or the like to consolidate multiple USB controllers into one uber device (or at least fewer than four devices) for VA to read