m4ti140

I just checked and it works in OB. I get permission from Nalchik tower and I can start the engine no problem. What exactly are you doing, step by step? Do you have easy comms on perhaps? (it shouldn't matter though, I checked and it works even with easy comms)

What are you talking about? How many years ago have you last flown the module? New RWR has been integrated into core module for something like a year now. The "Experimental Features" option is a dead option, it doesn't do anything anymore.

Dolphin is the MiG-21 pilot, not Rudel.

No, my point is that you're plain wrong about the FM. The new FM and new RWR are like the only two things that are perfectly fine about the module. Focus your attention on things that actually need work.

Old FM literally ended where the wing rock is now. It only simulated in-envelope behaviour, the moment you stepped out it turned into a literal brick.

Woooot.... of all the things to complain about in this module you chose the one that is pretty good... Also I like how after "reading some reviews" you think you know better than the actual MiG-21bis pilot who made the FM. The radar is all wrong. The gunsight is all wrong. The navigation system is all wrong. Weapons are all wrong. Nope, you choose the one thing that is pretty much on point and have no legitimate arguments to back it. Dolphin flew this aircraft for over a decade before he wrote the FM.

Doesn't spawning them uncontrolled and then activating them one by one 1-2 min before their take off time do the trick? The same way player's wingman is delayed until player does a radio check? Or does the taxi order get messed up compared to when they just spawn and spool up immediately?

Every single system needs work. Read RL documentation for the MiG-21bis and compare to game. The only system that is on point is the RWR, which has already been reworked relatively recently. Electrical system, navigation, radar, gunsight, everything needs the same treatment to be accurate.

Anyone who actually flies the MiG-21 and sees the state it is in. It was never "redone". It shouldn't be weird that more people are going to be passionate about a combat aircraft than an aerobatic aircraft in a combat flight sim.

What do you mean "lower discrepancy"? The discrepancy is by a factor of 2, just like in MiG-21bis! The zero point is just moved. It's not the same aircraft, the way it's mounted can be different even. And at this discrepancy you would still already be dangerously close to a tailstrike if you followed the real takeoff procedure. Please show me a piece of documentation showing the real critical AoA is higher. The flight characteristics book for the 21 refers to loss of conventional lift as a stall, because aircraft would tumble at this point, vortex lift regime is not even mentioned there. I don't know why the aircraft becomes uncontrollable by this point (and couldn't find anything in documentation), but it does. In DCS it doesn't actually even stall at all at this point, if you can keep wings level and pitch further keep flying like that. In fact you can keep flying way past reasonable angles of attack into region when the aircraft would surely tumble due to vortex shedding.

1. And the effect from a massive barrel going through the air is non existent? 2. I don't see how higher speeds make it better 3. The wing is not the problem with the 21 sensor 4. It's not. The error becomes 0 around 4 degrees, it's higher both below and above that value. Also the errors for a vane mounted the side of the forward fuselage will be completely different than in wing upwash region. 5. Follow the exact take-off procedure in the real flight manual and use info bar instead of UUA. Your tailpipe will hit the ground. 6. For the last time, it's a different mounting point. It was meant to illustrate the fact that the flow around the aircraft is completely different than free stream.

This too. If something's modelled wrong, it is that if you can get past that initial wing rock effect, it's possible to reach AoA as high as 50-60 degrees (according to "F2" obviously, because UUA doesn't even go there) and keep it there, even though at this point you should get vortex shedding. I'd look for errors there, not at 15 degrees.

It is a perfectly reasonable assumption, and the reason why in F-14 for instance they didn't bother and the AoA indicator is scaled in arbitrary units. Here's a NASA paper where they were evaluating a calibration method for AoA sensors. The AoA vane was installed on a boom, one chord length in front of the wing tip. The aircraft is Piper Saratoga, whose maximum speed is close to MiG-21s stall speed, so we don't even need to worry about mach number in this case. On page 10, Table 2, you get the final conversion formulas they obtained with various methods. The measurement errors were above 30%, with zero completely off. And if you look at the raw results, you can see the relationship isn't exactly linear. https://ntrs.nasa.gov/api/citations/20140002449/downloads/20140002449.pdf And for the last time - MiG-21 is 50s design. Why do you expect it to get even close to angles of attack modern deltas don't let you fly at?

He didn't say it's "true" AoA, he called it "local" AoA. That's exactly what it is. By "relative pitch angle" he means that the angle shown in F2 view is arbitrary based on how body axes are defined in DCS, with no direct correspondence to how they're defined in documentation for the real aircraft. I don't know how he coded the FM but from what he says, he isn't using that value as reference for calculations. Note the he's not a native English speaker. The documents for MiG-21 you're referring to use UUA indications as reference, not the real AoA. They explicitly say it's in reference to UUA. And you have all those critical angles marked on UUA-1 gauge itself. Just because delta wing aircraft can technically go to higher AoA doesn't mean one of the first delta wing designs will be able to go there. Mirage 2000 is limtted to ~30 IIRC despite having vortex generators to delay wing rock. 21 has other issues with it aerodynamics that limit usable AoA.

Go read an aerodynamics handbook, you'll see for yourself. Or learn Russian and read the original 21 manuals. I've explained to you how an AoA vane works and what the UUA-1 displays. That's what Dolphin referred to as "local angle of attack" - it's the angle of attack relative to airstream at the point it was measured, not in the free stream. If you think I'm lying, go read the original sources. You're saying "you're not advocating on anything" but your accusatory tone suggests otherwise.

It seems most people here have a misconception about what angle of attack is and how it's measured. The angle of attack of the aircraft is defined as an angle between free-stream flow vector projected to the vertical reference plane (usually the plane of symmetry) and the longitudinal axis of the aircraft. This axis can be technically arbitrary and is up to the designers of the aircraft to define, but usually it's often (but not always - and in fact it's up to devs how it's gonna be defined in DCS and shown on the info panel) either parallel to chord line at some point along the wingspan (which one is, again, arbitrary but usually it will be the root chord or mean aerodynamic chord) or defined in such a way that the lift coefficient at 0° AoA is 0 (this is called a "zero-lift axis"). In order to measure aircraft's angle of attack, you have to measure the component of free stream vector parallel to symmetry plane. Problem is, that IRL it's impossible to obtain directly it in flight. Unless you use optical methods (which are only practical in wind tunnels) the very presence of the instrument (the aoa vane) as well as the aircraft itself will deflect the flow not just around the aircraft but even some distance in front of it. This is why the DUAS probe is mounted where it is, as it attempts to obtain AoA and sideslip as close to free stream as possible. But that's not what the UUA uses. UUA uses the AoA vane to the left of the inlet - well within the "disturbed" airflow. And it's the only indication available to the pilot, which is why most documentation that is easily, publicly accessible for the MiG-21bis uses UUA indications as reference, unless stated otherwise (or unless it's wind tunnel testing - which I'm yet to find for the 21bis), and not the "real" AoA. So yes, the info panel AoA is the more accurate AoA measurement, because it's taken directly from the simulated state vector. Problem is that it's useless. And any characteristics you will find for the aircraft use the "wrong" AoA as reference because IRL the pilot can't press F2 and/or ctrl-y to see the info bar. As to why F-18 shows you "real" AoA - it's because there's usually an approximate mathematical relationship between measured and real AoA that can be obtained for each aircraft, and the computer can calculate it for you. The UUA on the other hand shows you the angle of deflection of the AoA vane rather than your angle of attack, it's not an electronic system. Think of its indications in same categories as the AoA indicator in the F-14. There's in fact a formula somewhere in MiG-21 manual (or flight characteristics, can't remember) that tells you how to calculate your approximate "real" AoA from the UUA indication.

The carrier in Mission 2 doesn't have ACLS set up despite Case 3 recovery.

You have a generous definition of what a fact is. You can see that there's a dispute to their accuracy, so you don't need to be rude nor is it warranted in any way.

You need to bind Petrovich AI Helper - SHOW/HIDE in both Pilot and Petrovich layers. The way I have it mapped is I have all directions on my "Petrovich hat" (same I have bound in Petrovich layer to select options) bound to it in Pilot layer, and then in Petrovich layer I have ICS trigger first stage mapped to it. So to bring it up I just move the hat in any direction (this way double press immediately selects the option when targetting cross was hidden) and then I tap the first stage of trigger (intercom PTT) to hide it. The inputs won't overlap cause they're in separate layers.

For me the issue is partially solved. When trying to optimize my FPS I noticed that I get lower FPS with terrain object shadows OFF than with terrain object shadows set to FLAT. Which is weird. Even more bizarrely, the FPS drops when disabling terrain object shadows even with shadows otherwise completely OFF. I wanted to have only the cockpit shadows and flat vehicle shadows enabled, but this issue prevents me from doing so. This is in current stable.

Two Weeks, Be Sure /s

Maybe give them a "dummy" waypoint right before the one they're supposed to switch to? Assuming it is consistent and it's always one waypoint prior? Or do they choose the waypoint at random?

Another relatively small one. During RTB in Mission 8, after AAR Olive doesn't seem to rejoin (not sure cause I somehow die in the track ofc) and after kiss off she flies off back to Romeo 1 before going home. Track, not sure how useful: https://1drv.ms/u/s!ArMDWm49dN3CguAJdRUTREUVBwyQjA?e=7gfCDU

That wouldn't be fair to MiG-21 players due to its RSBN implementation being static and disconnected from actual RSBN implementation in core game. You have TACAN at Kutaisi. Just use the F10 ruler and subtract 5 for magnetic deviation. Almost Every Georgian airfield has a TACAN, so you have full coverage, and as long as you have a station in range you can arrive precisely at any point you want.

Two issues with this mission, one minor, one major 1. Mother doesn't arrive at WP4 on time, they're around 0.75 to 1 minute late. Using TOT to arrive at WP4 at exactly 08:00 causes the whole sequence to play out a minute too early. 2. The rescue helicopter hovers on the approach path, sometimes almost exactly at the glideslope and course. Although the mission itself is not of "strategic" importance this is a bit of a serious issue, as it causes AI to go around, sometimes several times, and the chopper might cut the player off too. I imagine this mission was created before the ground follow function for helicopters was introduced - this is a good place to apply this enhancement I suppose. Track: https://1drv.ms/u/s!ArMDWm49dN3Cgt9DcYwCKXtaM6MUJQ?e=XtNJGL