jojo

It’s also a matter of time frame. DCS goes from WW2 to jets with L16, JHMCS + AIM-9X & Fox 3. In the middle we have Fox 1 shooters. During the Cold War it was mostly Fox 1 (excepted AIM-54 on Tomcat, but Phoenix guidance limitations aren’t simulated yet :music_whistling:) Until the mid-90’, Fox 3 weren’t very widespread...

I don't know if the new behavior is right, but yes, we used to have target box in NAV mode before...

4: in my experience, the closing speed is unreliable at close range in TWS only (ok in STT). Could you confirm this is what you’re talking about ?

+1 I tried to do it on my own. It's true it's kind of a mess since SA-2 and SA-3 aren't defined in the same files. But there is a solution since Hornet (at least) can identify these SAM. Chinese HQ-7 too (copy of French Crotale), same kind of threat as SA-8 = SHORAD (but not the same radars).

I have the new symbology. But my customization is gone. So I have to paste my custom file after each update. While we are at it, we can also customize decoys programs. But it will be the same problem, custom programs will return to default after update.

Yes, but in DCS we only have noise jamming, and the self protection range is very long (20Nm). It isn't as "clever" as the real one.

We can customize threat symbols in SERVAL.lua and this is great. But the file return to original after DCS World update :( It would be better if it could be customized in "users/saved games" folder. Thanks

Thank you for the update :thumbup:

Mirage III already had HOJ :D

:doh: Ok, but still, when you are in the notch, jamming does more bad than good. You should cut it off :smilewink:

Ok, maybe I did a wrong assumption then, but it shouldn’t be the be the case for most jammer :music_whistling:

From a series of test performed by the 3rd Wing (give back to Caesar what belongs to him :D), any fighter would burn through M-2000C jammer around 20Nm. This is boring to death, I can’t understand why F-15 and MiG-29 would burn through at the same range, and IMHO, this is too far. Overall, you would burn through enemy jammers around 20Nm too. Last time I checked (please correct me if I’m wrong), F-14B doesn’t even show jamming on radar (missing feature). Electronic warfare is kind of lame in DCS. And it’s limited to noise jamming, many more techniques exist IRL (deception modes, like range gate pull-off), but no public combat flight simulator goes into that. Yes, some missiles have HOJ, most of them actually (Fox 1 & Fox 3). You need to know threat range (AWACS, GCI, own radar...). If enemy locks you beyond 20Nm you can break the lock using the jammer. I would advise to use jammer when threats are detected, to delay enemy situational awareness, but to cut it below 20Nm. Also, during the beam/ notch which is a good defence to defeat radar missile’s kinematic at long range and guidance at short range, the jammer is ineffective. It doesn’t jam at 360°.

Here is my custom RWR library, link to ED users files: https://www.digitalcombatsimulator.com/en/files/3312388/

Very interesting work, there is definitely room for improvement here :thumbup: What are you calling the "too slow" sound ? If it's max AoA/ full aft stick you can hear it very often here :joystick: Et craaack ! :D

For the point 2, this is because the Mirage 2000 HUD is KCAS and not KIAS. Go to this page: https://www.japcc.org/aar/ At the bottom download ATP 3.3.4.2, go to Table 2-3. KCAS to TAS Conversion. For instance if you want your Mirage to fly at 250 KCAS at 25 000ft, set the tanker to orbit at 361 KTAS (mission editor uses TAS). Off course, this is true for standard day temperature, but the page also teach you how to account for temperature deviation. This is no BS, I use it to plan tankers in my missions, and I get the speed that I want for my Mirage :smilewink:

Kj-2000 is very easy to change, or you can just install my mod :smilewink:

I did a small customisation. I uploaded to "user's files" and it's waiting for approval. In the meantime you can get the zip file here: http://www.checksix-forums.com/viewtopic.php?f=456&t=209988 I included a kneeboard page. So you can print or just display in the cockpit :smilewink:

Indeed, the problem seems to fixed in Open Beta, it's reacting to both side slip and cross wind.

Rift S too. I would say that the problem isn't that much between F-16 and AWACS, but between F-16 and F/A-18A. These symbols: */ °/ . are quite smalls compared to the letters. Maybe their size could be increased to allow better readability :smartass: (zoomed view) I started to edit the SERVAL library by the way, clockwise from the left: - E-3 - Tomcat - F-16CM50 - SA-2 - SA-3 - KJ-2000 - F/A-18A - Tornado GR4 - E-2D SA-2 and SA-3 being displayed as U is a problem. But since FA-18C can identify these SAM, there is probably a solution :smilewink: We need the Chinese HQ-7 too.

Piece of advice; relax and watch it on TV :thumbup:

The most probable cause is that you are trying to lock with the wrong button. In the control panel use “HOTAS” filter. You will see that there is: - a button to lock - a button to toggle TWS <=> STT - a button to unlock These are three separated commands (as per the real Mirage 2000C HOTAS) as opposed to previously where the lock button would also toggle between TWS and STT. :smilewink: PS: radar tested OK on latest Open Beta as of September 24th

The new RWR is cool, but we need SA-2 and SA-3 in the library or a procedure to add it please.

Anyway that was an interesting discussion about the Mirage 2000 flight control system :thumbup:

He said he turned EP off and EP only starts if the pressure drops below 160 bars. So the remaining question is how much pressure can the wind milling provide ?

That part may be wrong indeed. But it would be easier if we could check a track :smilewink: