jaylw314

Out of curiosity, are the NVG's you used really unable to focus close up? I knew someone who claimed to have worked maintenance on A-10's, and he claimed the NVG's did not really have that limitation

Yeah, I remember a lot of questions about that earlier and didn't realize it was a core change since I never use it

That kind of defeats the purpose of the Easy Comms option?? I mean, realism but sheesh

OK, then the current implementation does look like that--I have enough space to peek under the NVG's. The implementation has changed over the years, there were some times the lenses took up 75% of the width of the FOV, which didn't leave enough room to peek under or around them, but this current one actually seems consistent with your description. However, it seems to be implemented this way with at least one other module, I assume different aircraft would have different configurations

Yikes, I remember there was some sound changes a couple years ago...

Hmm, most VR headsets have an FOV about 80-100 deg or so, so a 40 degree eyepiece would be completely doable in VR. Does the image go away when you are not looking directly at the eyepiece, or can you see the image in your peripheral view when you look away (like binoculars)? The first effect would probably be tough to do in VR but would be neat/annoying

I've heard opposite things about NVG's from two different buddies who worked in maintenance. I just haven't gotten them in the same room at the same time to hash it out FWIW, in VR, the NVG's now seem to subtend an angle of about 50-60 degrees, so if it's a 1" eyepiece, it'd be about 1"-1.5" away from your eye.

The most recent RAZBAM manual still notes the TACAN mode of the autopilot is not implemented yet. I know they've played with the altitude hold gains, but it still does seem a bit off. I've found messing with pitch trim after the autopilot is engaged helps, so I wonder if it has problems when you're not exactly trimmed to 1.0G before engaging it

If you LOAD DSMS instead of LOAD ALL, it takes about 5 seconds vs 15 seconds

IIRC it includes both, but they are downloaded separately, so you have to select both of them from the module manager. I am unsure how it works with DCS Steam version

You'd probably like the Rising Squall campaign for the Hornet, but there really isn't any paid campaign like that for the A-10C. Conceptually, the problem is that the A-10C does not do "excitement" all that well, since getting shot at is generally poor for your health . Your virtual pilot might survive, but you'll have to restart. That being said, many of the early TEW3 missions are pretty slow, but they do pick up the pace later on. With the AI wingman?? That would amount to "lead will engage, 2 will run out of fuel and eject"

I'm going to guess there was some attempt at a max speed run

My understanding is the INS actually drifts some during the drop, so that tells you how quickly it can drift. The GPS isn't used for correcting the INS until about 30 seconds after release, and if GPS is unavailable or jammed, it uses INS the entire way. So that kind of suggests the drift within 30 seconds is within tolerance, but after that it might start to be significant

A lot of the cockpit buttons are nonfunctional during the LOAD delay, at least all the MFCD OSB's IIRC. I think I also recall the NWS button not working.

page 479

Page 402 in the current manual

My understanding is also that if you designate a point with the AG RDR, it will apply the elevation of the sequence point in PB17 of the radar. If it's far off from the designation point, it could have a different enough altitude to be a problem.

A-10CII can't receive NDB's, it only has (or should have) ADF for UHF and VHF-FM.

Stable is still on 2.8 when this issue was reported. It's fixed in 2.9 open beta

Ah, no, I did play the track, but I missed the fact that the player audio was not playing It just reminded me a lot of trying to play TEW 3.0 a couple years ago and suddenly not having the AI JTAC and wingmen respond, but IIRC the player audio was still playing...

Is there a reason to believe the problem is the radios failing vs the AI wingmen and JTAC becoming unresponsive? The latter have both been intermittent bugs I've experienced over the years in past updates, so it's not out of the realm of possibility

It would be interesting to test if LOS for the AI JTAC actually matters, but again, not related to the bug at hand

Not related to the bug, but with a human JTAC, the abort call could also be if the JTAC loses visual on the attacking aircraft (required for Type 1, desired for Type 2). I think in DCS, if you are not heading towards the designated target area, the AI JTAC will also call an abort

Mountains are a good reason to do the airport->outbound on ILS->procedure turn approach. That way you can stay mostly above the ILS path, which, by definition, shouldn't have a lot of obstacles. It's not perfect, but until we get actually useful ATC in DCS, it should work for most airports. No refunds if you happen to find that one little hill next to the ILS during your procedure turn, though

Even if it existed, the A-10C is too slow for it to be an issue