Frederf

4 tested, 4 success with blue ownship and red SA-19 Ka50 SA19 Hidden.trk AH64 SA19 Hidden.trk F18 SA19 Hidden.trk F16 SA19 Hidden.trk

There is a NACA paper about correction values of local AOA of fuselage mounted sensor (and other locations). It is not negligible. There is a reason they use super long temporary booms on flight aero testing to get as close to free stream data as possible. Btw DUA signal is transmitted electroniclly. It would be easy for a multiplier circuit to adjust the scaling of the value of the sensor electrically. When you are grabbing gauges out of the Soviet parts bin you might desire an expanded display without fractional values.

You don't just hit enter twice, well the coordinate element is a two stage process. You enter DD°MM'SS'' and then in the second entry window is for the .SS'' fraction. By hitting enter twice you are essentially entering DDD°MM'SS.00'' and not a more precise location. Try for example to enter N 34°12'55.76''.

Man Rev has changed through the history of DCS:A-10C. Originally it worked on a muscle-limited standard control scheme then it changed to a relative axis scheme. The first one was almost indistinguishable from PFCS because the pilot kept the stick in the commanded pitch position with up to 50lbs or more of force exactly until this force was exceeded. Despite it being difficult and cumbersome to fly in reality, this "perfect match up to max pilot muscle" masked the quality of man rev flying, that it was difficult and required maximum attention and minimum maneuvering. Then it was changed to be relative controls so that X% forward stick would slowly increase pitch stick forever. This made it hard and cumbersome to use but was entirely unrealistic from a mechanical point of view.

LAlt+Y

LASTE wind is for weapons solutions only. The TVV (and thus pitch scale) on the HUD always use the INS current velocity vector.

The MiG-21 has historically not had the DUA sensor on the fuselage. That was added at some point I think slightly before the bis variant. I'm gathering the assertion is that UUA-1 is in degrees wherein a "20" on the gauge indicates a rotation of the fuselage vane of 20/360ths of a circle, yes? Limit of UUA-1 is not wing lift but controllability. If curious I did experiment to find UUA/true AOA relationship in... 2016. Correlation was high confidence. It's not 0=0 and 2x the slope simply. If you expect higher CL from more AOA then you will be disappointed. Maybe AOA/UUA-1 relationship is wrong but CL relationship is not that far off. Performance won't change but body angle would.

There is a graph of stick force vs output fraction I'd you want it. It's not entirely linear.

Air bunches up. The pressure wave from a leading edge of a wing can influence areas farther forward just like a wave in front of a ship's bow. The actual CL graph can be extracted from DCS by experiment and compared to known CL curves from the real life aerofoil.

All IP/RP/OAP ELEV are absolute elevations. All bearings for IP/RP/OAP are true bearings. Since IP/RP/OAPs are relatively displacements from a steerpoint their relative position must not change by INS drift. Any drift of steerpoint will cause both to drift by the same amount (discounting any tilt effects). CZ removes the slews in the bucket that you're currently in. IP/RP/OAP displacements are not cursor slews and must not be affected by CZ.

It's not that it loses connection, it's that the radar can't be sure the new target and old target are the same. You have a good 13 seconds of track coasting. If it picks up within that coast time then guidance continues. If not then new track is new target.

Your RTX 3060 supports DP++ dual mode so a passive adapter should work.

The TGP is current in CCD (TV) mode. Even in an IIR to IIR direct comparison I would expect the $3,000,000 TGP to have better image quality than a $90,000 missile.

It depends on which action you did first. Since it's doing a toggle when both press and release events occur there's no absolute command and there's always a chance that the events and the switch state are out of phase. The only way to ensure absolute agreement is to have an explicit on and off command which we don't have. The initial state of the sim variable would depend on ramp or flying start and if sync controls was set it might get an extra flop in on initialize. This is the best you can do. Pause/alt-tab the game and flip your joystick switch once to get them back in sync. That or make a keyboard bind so you can flip the sim switch without the joystick switch to get them in sync.

The RF switch is pretty complicated. Despite the wording, there are allowed transmissions in quiet/silent but they require specific pilot action. E.g. in radar quiet you should be able to get a dogfight lock, AG radar mapping sweep, etc. From memory in DCS it largely does what it should. Does it do all the very specific, odd logic exceptions? Possibly not.

I just did a spot check after experimenting on Vaziani to know that they vary. I feel like there were a few overall templates like 3 or 4. I didn't exhaustively map every airport. One was enough. It also gets hard because wind is defined at different elevations and airports are between the wind definition layers. I drew the diagram.

The transition between dry and augmented thrust appears to happen at exactly 75% axis input.

It's been how it's worked for ages. There have been a few requests for radio landing aids to have a different logic such that non-conflicting aids remain on (e.g. when the opposite runway has no aids). An interesting detail is that (last I checked) there were small edge cases where ATC could assign verbally a different runway than the radio aids were configured for. The wind rules for radio aid selection depend on particular airports. Some are diehard always one runway. Some take a very strong tailwind to change and some are nearly 50/50. I did an experiment in 2018 and found the boundaries of Vaziani's ILS selection and ATC selection. They are based on different rules as the picture should show.

Can you extend the range of the S200 by placing the search unit closer to the target?

As suspected, try removing the button 14 bind on the third line. As long as your WINWING F16EX Throttle provides constant output of buttons 13/15 in the DGFT/MO positions of the switch, that's what you want to do in any case. It was designed that for such switches the center command would be implicit when the other commands are released. The release of the non-centered position plus another explicit center command happening at essentially the same time must be confusing the system.

There are area navigation NDBs (e.g. DA near Gali) and there are landing aids part of the 2NDB runway approach system. The area NDBs operate all the time. The 2NDB aids are associated with a particular runway and turn on and off based on the weather similar to ILSs. Indeed the T and KT beacons are associated with the 07 runway at Kobuleti. If the wind is blowing from the west strong enough the system will change to runway 25. Then T and KT will go offline and any NDBs associated with 25 will come on (there are none). A zero wind new mission will use runway 07 as that's the calm wind runway and those beacons will be operating.

As far as I can tell there is only one command, iCommandPowerOnOff. All the other commands iCommandPowerOn, iCommandPowerOff, iCommandPower don't exist. This worked for me. I was using Quaggles lua injector but it should work fine manually placed into the original lua file as well. {down = iCommandPowerOnOff, up = iCommandPowerOnOff, name = _('Power OnOff (OnOff)'), category = _('Custom')}, Obviously change the category and name labels as desired.

Are you using the red commands or the green ones? A lot of the track data comes from TrackIR/VR type head movement. If you fly diagnostic flights without smooth head motion control the file size is much smaller.

Is your switch programmed to make deliberate inputs on all three positions or are you using the two commands for dogfight/missile which fall back to center when either is released?

That's strange. When I put an F-5E-3 on parking 36 at Tibilisi I can converse with ground but taking over your track I can't. I see your unit is country USA but I can't tell if USA is in the BLUE coalition. I made a copy of the mission and loaded it as a .miz. USA is blue. Red coalition is empty but that doesn't matter. If I run the mission from editor I get normal comms. I feel there must something about that track specifically.