jaylw314

Is that stable or open beta? Stable is still on 2.7.14.24228 (May 27th), the new IR implementation occurred the next OB update

+1 I also tried injecting the canopy open and close discrete keybinds, but those do not work either. I'm guessing the switch reorientation changed other things under the hood

I was going to suggest moving this to the bug reports subforum, but somebody else just posted it there

I didn't see in the changelog that this previously reported problem had been fixed? You also probably want to move this to the Bug Reports subforum, no? Edit: Oh. I find it hilarious that you made the same mistake in the title before

I VERY vaguely remember having difficulty calling ATC on VHF FM last year, so I wonder if this bug has been around for a while. However, like you, I just mainly ended up using UHF or VHF AM anyway, so I didn't think about it again until just now.

LOL, yes you outpedanticked me (making up a new word there) I had assumed when you mentioned extended and retracted that you were talking about the transition.

At the risk of being pedantic, during landing gear retraction the brakes are applied to stop wheel rotation.

That's never happened to ANYONE before The other gotcha is if you forget to press the EGI button on the NMSP (under the artificial horizon). If you don't, the EAC won't latch on.

If we have the same one, yes. I've been misreading it, it says the wind blows the flap TO 15 degrees, not UP 15 degrees, so that does match what we're seeing

Just to close the loop on this, I tested using the external view, since the info bar displays flap position as 0-100%. 100% is presumably 20 degrees, but I don't know that for sure: Flaps UP - 0% emergency retract - 3% Flaps MVR - 35% emergency retract - 3% Flaps DN - 100% emergency retract - 75% So in DCS it seems the wind blows the flaps from the DN position (20 deg) up to about 15 deg, while in any other position it blows it to nearly fully up.

I had a minute to check it myself in flight, and indeed in the DN position, turning on the emergency flaps retract switch only lifts them about 5 degrees (75% on the external view info bar). I forgot to check how much the flaps lift in the MVR setting. I couldn't find anything on how MUCH the flaps are supposed to lift in the DN setting (I'm not sure where I heard the 4 deg number, but obviously it was wrong), but in the MVR setting they should lift to near 0 deg. If that does not occur, then it's probably a bug

LOL, you're right, I looked at the electrical diagram a little closer, and smack in the middle it says "NOTE" the AC essential bus receives no power from any source when the inverter switch is off. I have to imagine the battery is capable of powering the igniters, otherwise a ground air start wouldn't be possible (not that it is in DCS).

LOL, that would be a funny YT video I also assumed that the essential AC bus that the igniters are on would be powered by the APU generator, but in DCS it seems to require the inverter switch to be on STBY, regardless of whether the APU generator is running or not.

Ah, okay, I'm not able to look at the track file. Were you looking at the external view, the indicator or both? I assume you were in the air flying?

The flaps retract switch basically just disconnects the hydraulic servo from the flaps so it moves freely. While moving, the airflow will push the flaps up from the DN or MVR position to about 4deg down, but no higher. If the flaps are already retracted, though they'll stay fully up. Once you stop moving, the flaps just drop to the full down position.

If you have a track file, you can replay it and the mission end screen will show you who shot who. Conversely, TacView is good for this sort of thing if you have it installed

If you go to Settings -> Special -> A-10CII -> Customized Cockpit and change it to "Factory new", the AAP looks like this:

"Correct" is a relative term . Maybe it's best left "as intended." FWIW, range-only TACAN would be tough to use for rendezvous when you have dumb AI tankers. AFAIK, IRL the tanker would help you out in a variety of ways (hitting waypoints on time, communications, etc.), all of which the AI tankers are incapable of doing. Bearing is actually trickier because you need some kind of directional antenna to broadcast bearing info. Range is pretty easy and just requires to radios "handshake" a signal--one airplane signals the other, the other signals back, and the first airplane times how long it takes to determine slant range. That takes a minimum of equipment and a tiny antenna.

Hmm, now I have a sneaking suspicion it was from updating my joystick firmware, but I don't know how that could be but it still looks ok. All the curves and responses on the axis tuners still look ok, it's very strange. Thanks for the info guys! Update: Yes, it was indeed the joystick firmware update. Recalibration fixed it, even though it looked fine on all the visual scales <shrug>

Yes, I can't recall where, but ED stated that was their intention. The why is controversial and unclear

For reference, both the ILS and TCN knobs on the audio panel default in the down/off position. All the others start out up/on. Doesn't explain why you weren't getting range/bearing. If you were receiving the TCN signal, you'd be getting range/bearing regardless of whether the audio knob is on or off, so there was probably some other step that was missed... Also, FWIW, in DCS, tankers use T/R mode, not AA T/R.

A couple updates ago, I recall the F-16 FLCS got changed, and there were some issues with gains where people complained of the controls being too sensitive, then there was a fix this last update. Somewhere around that time, I think I started noticing that the A-10CII controls became more sensitive as well. Normally, it takes 1/2 to 3/4 back stick to rotate the nose, but recently, I've been almost having tail strikes from the nose snapping up with that kind of input. Likewise, at cruise speed, the controls sometimes feel much more sensitive than I recall in both pitch and roll, and I feel like I've been yanking the plane around lately. I'm wondering if this is somehow connected to the F-16 flight control changes. The problem is, I didn't record or test anything beforehand, so I have no idea if this is all in my head. Has anyone else noticed this?

That's what I thought but I wasn't 100% sure!

Does inputting zero for EL on the waypoint page reset it to ground elevation on the WAYPT page? Or does it bury the waypoint underground?

Just for reference, that should be TMS right long. That will make your most recent mark point SPI.