Pavlin_33

Well acording to the flight performance of that turn, 13+G seems about right. IRL Flanker is rated as an 8G platform, and in DCS it desintegrates if you go over 12G for even a micro-second (150% limit), so there is definitely something off here in terms of consistency. 150% of 7.3G is 10.95G; compare that to 13G

Been doing a bit of dog fighting in a Fulcrum A against the Tiger and I was surprised that I could not keep up with it in a turn, only to review the TacView and see that it can pull 13.4G, without breaking a part! Should it not be rated for a max of 7.3G? 13.4G is almost double that. Also shouldn't the onset of 13G in a span of 3seconds black out the driver?

When locking a target via "Shlem" using EOS and then turning the radar on, only the EOS indication in the upper left corner of the HUD is shown. Radar indication right next to it, is missing.

As the title says, R-27 just turns into a dud when the Horned starts releasing decoys. Short scenario: 1. F/A-18 gets locked 2. R-27 launched 3. Hornet starts releasing decoys 4. R-27 goes "dumb" Here is the TacView recording of the incident: https://i.imgur.com/H07UDic.mp4 Radar lock was kept throughout the engagement. I am not really sure what the decoys should do once the lock is established, but the Alamos should either go for the target or the decoys - instead they go no where. Decoys practically represent an invincibility cloak at the moment.

I did already here:

Sooo... is ED working on a fix for this bug or Deka? I am not sure, who took ownership.

Dear ED, Please remove "flying bricks" beyond certain range, like 15km (insert correct number here). Soviet vertical scan mode limits radar lock-ups to 10km, since they expected this mode to be used within visual range. In DCS we have dots that are visible at 40km+, so now aircraft with sensors almost have no advantage over ones without. This is highly unrealistic, and might give advantage to players with certain software configurations. Thank you in advance.

Is it better in ST?

Are you running multi-threaded version?

I've had exactly the same issue. I just wasn't aware that my DCS was starting in MT every time.

Just to add here: to start ST do not use DCS created shortcut. Create your own or start ST manually. Took me a while to figure this one out.

For what it's worth, in my case the issue was MT. I thought I was running ST, but I was wrong - default desktop icon always starts MT.

I meant in RL

Ok, so the stutter is gone. I am not sure if I should feel embarrassed or mad at ED: issue was that the desktop icon was launching multi-threaded version even though the icon's path was explicitly calling single-threaded EXE file. Only after running DCS manually/directly from single-threaded executable (not using DCS-created icon) did it start in ST. TLDR; In my case it was MT version causing stutter and long texture loads.

What does this have to do with the original issue we are discussing here? BTW, I agree with what you wrote above, but that's besides the point.

You have a good point, but this is also a great opportunity to discuss this issue. If it turns out that other missiles/radars should behave the same then they should also not give a warning for sake of logic, instead of just "fixing" this and forgetting about it. Bottom line is that RWR needs to detect something different between lock and launch, what ever that something might be. Otherwise it has no way of telling when the missile has been launched. If it turns that 21 does not emmit anything different after launch, then it's not a bug and other platforms with the same behaviour should be revised. Otherwise this is a valid bug report.

If there is radio guidance, yes it can be detected, sure. If there is not, it can't be detected, 'cause there's nothing to detect. Not sure what you consider wrong with that. Does a SARH without guidance exist? No idea, but if it does there's no way you can pick up a launch with an RWR.

As @Northstar98 mentioned, and I tried to explain in a very poor manner, if the 21's radar does not change any mode when firing a SARH, there's no way for an RWR to figure out when the missile launch occurred. This should be true for any radar, not just MiG-21's. We're kind of spoiled a bit in DCS, 'cause we are used to getting launch-warnings consistently and reliably, no matter the system that is firing at us. I think (not 100% sure) that in real life, pilots consider a lock tone as a missile already fired or at least about to be fired, but for us in DCS it's just reminder that someone is perhaps about to shoot.

Chaff in DCS are nothing more than "flares" for active or semi-active homing missiles. Some missiles are less prone to chaff and some of them are more.

Flanker's cook-book only mentions to release the chute (тормозной парашот) after the landing roll or on command. It comes before the paragraph that says what to do after leaving the runway, so I assume it can be dropped on the runway? Looks like it might be operator-specific after all.

Yes, that's why I've mentioned the aircraft type I doubt it's country-specific in this case, but I will have to cross-check with Flanker's cookbook.

Ok so the "cookbook" says that the chute on the 29 should be jettisoned after leaving the runway and in a "specific place". Now I have no idea what is meant by "specific place", but I guess in DCS it could be the taxiway. Real fields probably have designated areas where it's safe to discard the chute, but this is pure speculation on my side. On thing is sure though: NOT on the runway!

I will check the manual again for details...

Also who would use a JF-17 to strafe at ground targets?

MiG-29 manual says never to jett. landing chute on the runway as it might pose a hazard.