Moody1204

Thanks you for this robust approach and your interesting testing. This proove that was stated before you clarify the topic and put an end to this discussion. Hope this will stop some people from thinking that you can pull as much as you want of the stick without being worried about stalling. Cheers.

Let it go... you are speaking to brick-walls. Thanks to the new "FM", many people can actually fly the jet and so they believe it's the normal behaviour because it's easy. It's reported and being investigated so let's hope the dev will manage to fix the FM.

Nice thanks

Reported and investigated : https://forums.eagle.ru/showthread.php?t=270231 :thumbup:

And yet some people still believe it's a "normal" behaviour... I did a Cobra with a 21, I also went 100km/h, pulled hard, then release pressure and it came back to horizontal flight just like that. Also, you can do barel roll when on final and still land the jet as a RC plane. Yeah, everything is fine some say...

Hi, FM since last update seems wrong especially regarding the AOA. From the Module manual : P.33: 3. The maximum permissible angle of attack in flight and during the performing of any aircraft maneuvers, is +28o by UUA-1 indicator (stall occurs when a +33o angle of attack, as read by the UUA-1 indicator, is exceeded). This is also very similar to the real Mig21 Manual. See attached a track and a tacfile where you can pull as much as you want on the stick and reach the maximum on the AOA indicator without having any issue flying the jet. Even if the AOA indicator is not showing the proper AOA, on the tacview you'll see I pull 33° and nothing happened. It feels like on rail or a FBW jet which is not. No shaking, no buffeting effects, no loss of lift on either wings, nothing. It was fine before the update, thanks for looking at it. Cheers, Tacview-20200418-165652-DCS-Mig21_high_AOA_no_stall.zip Mig21_AOA_no_stall.trk

:thumbup:

If you didn't flew it then just please don't state something that you don't know actually. Yes, I flew it a lot since it was out. Yes the AOA in the cockpit isn't reliable but still you can pull too many AOA (in fact as much as you want). Since last update it's a lot farther from a realistic model than it used to be. Show me graph that indicates the tiny wings of the 21 can provide lift at more than 33 AOA and I might consider your statement, but good luck on that. The FM needs to be revised that's it, and there is no harm in saying so.

Can we get any ETA on the hotfix please ? Because this is really anoying in populated server and missions... Also, TWS seems to show bandits as bandits, the problem tends to be in RWS mode only.

Yes, notice that you can no longer stall the jet even at 33+ AOA and low speed. I guess it is wrong and it need to be fixed because we the 21 is now a FBW 6th jet ! EDIT: Please find enclose a track and tacview files were you'll see you can pull 33° without having any troubles flying the jet.

Well, since last update you can now fly the 21 the way the IA is able to fly it: no restriction in AOA !

I believe the new FM changes are incorrect. The 21 isn't suppose to do fine at 30+ AOA, but since last update it does. You can no longer stall the jet in dogfight while pulling too hard which is I guess wrong.

Have you flown the jet ? and do you have any idea of how it should behave ? You can no longer stall the aircraft: pull 30+ AOA and you'll be fine, this in badly wrong. We have now a broken FM which need to be fix again if you don't want to see the 21 ban on servers.

Nothing to do with gama, others FC3's jets have correct cockpit lights. Problems comes from ED last update with new lightnings improvement, many aircraft have cockpit lights too bright. Please fix it :thumbup:

Yep, same here, radar "missing texture"

Hi guys, I have just play a mission and once again the radar has a wierd behaviour... See the attached pictures : When my elevation antenna is suppose to scan 3 to 21K (picture1) feet, I can still detect a bandit at 26K feet (picture2)... Can someone explain us if the radar is really bug ? or if it is normal. I can lock the target no problem, but my overall comment is that something is wrong with this radar... it behaves weirdly... Thanks !

Hi guys, Even with the new update (2.5.40269) the RWR is still halfcut... Please hot fix it. Cheers

Thanks for your quick response. I just use the repairDCS.exe tool and it is now working. Don't know what happened, probably a conflict with a mod. Thanks anyway

Hi everyone, Since last update I have trouble with the selected altitude autopilot mode. I select the desired alt, engaged the autopilot, she climbs but does not stop at the selected altitude, the button remains yellow (instead of going green). Does anyone have the same issue ? Thanks.

Hi, Concerning the CAS gun mode, I cannot get the gun piper. I followed the right procedure (the one afer the PCA updates) which is also describe in Mirage's Chuck's Guide. Can anyone confirme that the gun piper does not appear on the HUD ?

Dumb (but not so dumb question) : do you use the radar antenna elevation control ? I mean the axis which allows you to increase or decrease the antenna elevation. If you don't use this to match your target altitude you will loose the contact as soon as it gets higher or lower. Also, sometimes, when you turned on the radar the antenna is in a weird position and you need to adjust it. Cheers

Hi everyone, So, I did more test with the radar and I agree that it seems to work correctly. The thing is it seems that the radar needs a lot of attention to find targets and lock them up. I believe the radar must be refreshing the target to lock it up and not showing you last know position (in TWS, mode). You need to be very careful with the settings (especially elevation) to find and lock a target. I wonder if the RCS is now implemented ? because I find hard to lock Low RCS fighter (F16 or Mig21, compare to larger jets).

Hi, I found the radar weaker since last update. I had a mission for training BVR (1 mirage VS 1 F15 50 NM, strait ahead): - before the update I could lock the bandit at 25NM or more, - after the update, I can only lock the bandit 15NM or less... Nothing has changed, and the bandit is not using ECM. Anyone experienced the same ? Cheers.

Hi everyone, Following the last update I tested the "new" radar and noticed a change in the symbology. In PID (TWS) mod, if you lock a target you have an arrow showing a direction : which direction is this ? because it doesn't fit the heading of the target. (See pictures attached). I also attached the current display in PIC (STT) mode with the arrow which indicates the heading of the target (like before the update). Can anyone explain me what is the meaning of the arrow in PID(TWS) mode ? Thanks !

Thanks a lot Blythee for your miz file it worked ! Also, someone else told me another solution a bit more efficient to solve this : "You don't want to turn off the Flag 1. You want a new Flag (2) to turn on, and make Flag 2 Off a requirement for the first trigger. " Switching condition -> unit (Mirage) AGL above 500 AGL AND Flag 2 Off -> Flag on (1) + Activate SAM and QRF units " " Once -> Part of group inside the trigger zone -> Flag 2 On" As long as Flag 2 is off, if they break the altitude barrier, the SAMs will activate. Once they're close enough, Flag 2 is On and even if they break the altitude, it won't trigger the SAMs. If that all makes sense." Thanks to SpikeGondorff from hoggit for sharing this.