jojo

Are you doing the AP test during start up ?

Ok, fair enough for the A-7 which had innovative avionic for its time. :clap_2: But other method you are talking about aren’t CCIP, most fighters in use in the 1970’ still didn’t have it. Osirak strike was in 1981, but indeed, F-16 and Mirage 2000 are from the same generation.

Well, it's AG Mike in early 1980' because you have INS, radar ranging and ballistic computer. No CCIP in the 1960' :smilewink:

I'm sorry, you closed the thread in the bug report, so I can't answer you there. I think there is a big misunderstanding. The problem isn't to hope for a direct hit with a single bomb in CCIP. The problem as I see it in my test, is that if you press the trigger when the pipper is over the target, the first bomb is consistently long, about 200ft long in my test (60m). Yes there is a processing delay which means that the bomb will be dropped some times after the trigger press. What Ergo tried to explain, it's that the delay is known by the system. So the pipper is rised up to account for the release delay. So when the pilot press the trigger, actually he is making a target designation, with very short time CCRP. (By the way, on Hornet & Harriet, if the pilot makes a designation with the dashed pipper, it will transition from CCIP to CCRP, but this would most likely happen with free fall bombs, not high drag). So the pilot has to maintain the trigger pressed and hold still until the last bomb is released, and the first bomb of the salvo will land closer to the target in the centre of the pipper than the 60m long currently. I talked with Jean-Louis Bernard. The guy is a former Dassault Aviation engineer. He worked on the support of Mirage F1 EQ sold to Iraq during the war with Iran. http://les-heros-de-bagdad.over-blog.com/ http://www.editions-jpo.com/fr/home/221-les-heros-de-bagdad-tome-2-9782373011319.html https://www.youtube.com/channel/UCego5xtVXGPakwbYc2Rld9A I asked him about CCIP, and if he had some video about CCIP attack run. Unfortunately it isn't the case. But what he told me matches Ergo description. So the hexagonal pipper represent the impact point of the salvo. There should be a "hole" in the bomb fall line (BFL) which represent the last bomb of the salvo (missimg feature). So all bombs will fall between the pipper and the hole in the BFL, give or take a few meters. We are talking here about Mirage F1 EQ5 from the 80', nothing as fancy as Mirage 2000N or Mirage 2000D. I noted you asked to your "SME" at EC 2/5 and I'm happy about that. I'm sure it will be low priority since they don't use high drag bombs anymore. But I'm confident it will work as described by Ergo and Jean-Louis Bernard. All that doesn't mean it is recommended to attack pin point targets with a single bomb in CCIP. Of course you should set a bomb salvo, put the target(s) between the pipper and the hole in the BFL (inside the salvo projected impacts line), press the trigger and wait until all bombs are released. The CCIP on the Mirage 2000C is only used with high drag bombs, so currently only Mk-82SE and BLG-66. I don't understand why it would make other forms of bombing inaccurate ? This is about improving CCIP accuracy. And you are ruling out any modification before SME answer. Or did you already get an answer ? Question: are you also system coder for Razbam ?

I think got this picture here, extracted from Mirage 2000 EG landing video. You can see that at some point, the speed indication jumps up.

From day one I said the new RWR is great. But: 1- it’s missing a few weapon systems in the library (and these are weapon systems encountered during the aircraft service time). 2- it’s advertised as customisable, but you denied the need because of the SME. 3- I was just suggesting a way to avoid loosing the custom file at each DCS World update.

With the radar scanning 4 lines, it's covering vertically 32 000ft at 40Nm, 16 000ft at 20Nm. I would say 12 000ft at 15Nm. So the closer, the easier it is to have a contact outside vertical scan zone. SO you have to adjust your radar elevation. Then "cold" targets (tail aspect) are detected much closer than "hot" targets (nose aspect). But really it's the same thing most radar equipped fighters...there is nothing much you can do about it.

First, here is what is written on the PDF provided by Zeus on Page 1 onthis thread: Secondly, this is what I'm trying to explain: there is no definitive list of "this threat code" = "this specific threat" for Mirage 2000C. The number of symbols it can display is limited, so it's customized depending on the threat encountered during the mission. So it would make perfect sense to want to customize the threat library depending on the order of battle of a specific mission (or MP MP map for instance: Caucasus/ Persian Gulf/ Syria...). Thirdly, the Mirage 2000C did participate to air cover for operations over Bosnia and Kosovo (Deny FLight, Deliberate FOrce...). So had to deal with the Serbian Air Defense system, and they were using SA-2, SA-3 and SA-6. http://www.ausairpower.net/APA-2009-04.html HQ-7 is a copy of Crotale SAM system. Crotale was exported to Irak, and Mirage 2000C did participate to CAP over Irak during Gulf War and After (Operation Daguet/ Desert Storm, Alysse/ Southern Watch). These are threats Mirage 2000C had to deal with during its active service. Razbam offered us the possibility to customize decoy program and now SERVAL threat library. My request is just to put those files in a place where it won't be overwritten by each update, like we do for HOTAS profile for instance. Last but not least: your SME are in active service. M-2000C is just one training tool amongst others. They may not think of every aspect of the game, you have a much wider base of customers. But if every time we request something, your answer is "get lost, our SME said so", this isn't very productive :( But I suppose you are following that rule: "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Yes DTC would be great, but it wouldn't solve the missing SA-2 and SA-3. And being able to place a custom file in "saved games" would solve the problem of customization lost after update :smilewink: https://forums.eagle.ru/showthread.php?t=287891

You have to set your scan elevation. You can use min/ max (x1000ft) next to radar cursor. Big bombers can be detected head on close to 80Nm. Flanker at 47Nm. A little bit less for smaller fighters.

I tried to dig to add these systems myself. I failed, but these radars are not specified in the same files as all the rest. These SAM are WIP and defined in specific files. It must be possible, but I don't know how ?

From what is explained, AdA gave Razbam the symbols that the system can display. I'm adding that from what I saw on other systems, but close to this one: There is no such thing as one real life table. AdA has a unit (called EPIGE) which is managing and programming threat library. They would customize that library on each deployment. So a same symbol can be used for different threats depending on the deployment. I followed Razbam logic. The higher threats are identified individually. But since the number of symbols is limited, sometimes it's a type of threat rather than a specific individual identification. I just added a little bit more discrimination. I had to use what was left available in the alphabet. But overall, anyone guess is as good as mine. :smilewink:

I already posted this link several times, but it will be good for those who missed it. It's the point of view of a British pilot in exchange in the Ads, and flying the Mirage 2000C from 1993 to 1997. Ian Black flew the Mirage 2000C RDI after the Lightning and Tornado F3. It's a good point of view avout what was the Mirage 2000C RDI in the 90'. https://hushkit.net/2016/10/13/mirage-2000-pilot-interview-cutting-it-in-the-electric-cakeslice/

Yes, because nothing else was available :D But it became true with Mirage 2000-5F :thumbup: I would say that indeed it’s a good module to make the transition from FC3 to full fidelity module, because it simple and very handy. It’s true too that you should fly with wingman in MP, with any module, but even more with Fox 1 shooters. But the question was for a module to make his newbie life easier in MP, I don’t think M-2000C will provide that.

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...

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.

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: