jaylw314

It might have to do with age, control bindings got changed or added over time, and the A-10C is one of the oldest modules

That was the gist of the conversation, that nowadays the manually entered LASTE WIND settings don't seem to significantly move stuff like the CCIP pipper anymore like in those experiments from a couple years ago, so there may have been a subtle change somewhere in the meantime, but I didn't do the testing or remember the details FWIW, the LASTE WIND settings on the CDU are only supposed to be populated if entered manually. The automatic wind data collection by the LASTE all happens under the dashboard and the pilot doesn't have access to them

For the sake of being pedantic, I'd suspect the older LGB's would have more problems with early lasing from low altitudes. From high altitudes, it's gaining energy so quickly by the end that it can afford to do dumb aerodynamic things and still make it to the target. I think the later Paveway III's with their smarter guidance were specifically for low altitude LGB profiles

I swear there was a thread recently that I can't find now, where I recall where people tested out the WIND LASTE settings, and found that entering them made no difference now. It seemed like now the CDU already has the wind data corrected for regardless of whether they did air starts vs cold starts. Hmm, now I'm wondering if I saw it in a discord forum somewhere.

Not in front of DCS, but did you try searching for 'TGP' instead?

As far as I can tell, you're correct, the ASI is a pitot/static instrument, although I'm assuming in DCS that subtle distinction is not simulated, and the difference is just a graphical glitch.

The problem is a lot of runways only have ILS in one direction.

In that screenshot, if anything, the ASI seems to indicate about 5 knots faster than the 205 knots in the HUD. IIRC, the HUD airspeed comes from the CADC, and I can't remember if it defaults to IAS or CAS. The difference would be pretty tiny, but we're talking about a pretty tiny discrepancy.

My understanding is that markpoints are only created by the pilot to drop on locations visually or using sensors--they're not used for anything pre-planned. Those would be the regular waypoints which can be created in the mission editor. FWIW, you can make good use of a USB numpad or half-keyboard for the number entry on coordinates. Letters are used less often in MGRS and you can use the mouse or VoiceAttack for those (or you can use the letter function on the UFC)

If you maneuver outside the MAV seeker limits, I think it loses its lock. The TGP only loses its position if you pull its target through the gimbal lock area between the TVV and the boresight circle. As such, if you're going to maneuver the target through the forward gimbal lock area, try to make a markpoint and make that markpoint SPI (TMS right short, then TMS right long). Then, if either the TGP or MAV wander off, a quick China hat forwards long will reslave both to the markpoint. OTOH, if you're maneuvering with the target off to the side, it's unlikely the TGP will lose its position, so you could just keep the TGP as SPI and hope for the best. Then, if the MAV wanders off, China hat forwards (or aft) long will reslave it to the TGP. In either case, the sequence to quickly reslave and relock would be MAV SOI China hat forwards long TMS up short

FWIW, I recall the Blue Angels need to modify the legacy Hornet's fuel system for sustained inverted flight Edit: Apparently the Super Hornets also needed similar modifications

IIRC, that had more to do with the float carburetor in the Spit (immediate fuel starvation) than the typical fuel tank stuff people are talking about here.

This is just a realism design choice, not a old/new jet thing. All jets need to be told what armament they have unless they support a data link between the ordnance and jet. It's just that most of the other modules automagically do so when you jump in it in DCS.

As a follow up to this, I found a graphical bug I suspect is related to this. With the GBU-54, the HUD also does not display the profile name with the GBU-54 selected. In addition, the DLZ and range graphic and the MAN REL line seemed to be translated upwards intermittently, so that the upper part overlapped with the ARC-210 frequency lines. This appeared to be intermittent--I noticed it when I first selected the GBU-54 profile, then after dropping a couple, it seemed to go away. It was a long flight, so I tried again to catch it on a track but it didn't occur. I'll try again later and put up a track if I see it again

Ask the Google lady. There's a flight manual dated 4/15/93 out there. Note that it is not freely distributable.

No. That's not enough detail to go on either.

It's a reported bug already AFAIK. Designating while tracking seems to temporarily undo the track until you bump the TDC a little

With my mouse device, I am unable to use the mousewheel. It would be nice to have an alternate keybind to do this

My understanding is that the offsets are not for targeting, they are there as relative landmarks for the main target, e.g. you'd put offsets at various buildings or features that should be there while planning. Then you'd take a HRM, and if the target steerpoint is, in fact surrounded by landmarks at the correct locations, you know the INS hasn't drifted.

It helps if you don't use autopilot inbound from your IP

My understanding is that a JFS only does work through turning the shaft. It has to be mechanically hooked up to the engine it is starting, and doesn't do anything else. APU's does other useful stuff, like providing bleed air and electrical power.

Thanks, but I think you will find that some for of head-tracking will do far more for you in the future Good luck!

I mean, sure, it's not really a bug, but it is super annoying

LMAO, what the hell happened there??

You want the Move View Up/down/left/right/forward/back keybinds in the View Cockpit category. I think the defaults are RCtrl+RShift+numpad keys. These shift your view instead of just rotating them. It's also a good way to set your desired default head position, move your 'head' around with those keybinds, then press the keybind for 'Save Cockpit Angles' (typ) in the View Cockpit category to make it your default position