Zeus67

Folks now we have official subforums for both the campaign and training missions. Any comment, observation or bug report you can make it there under its own thread. Baltic_Dragon will monitor those threads to answer your queries.

Yes. In rral life it is hardcoded.

No, but now you can modify it. To modify the CMD program you must edit the ../../Cockpit/Scripts/SPIRALE.lua file you will see something like this: You have to modify the programs[n][x] entries: chaff = number of chaff bundles to be released flare = number of flares to be released intv = time interval between each release cycle = how many times will the program be repeated c_intv = time interval between program cycles panic = not used. You cannot modify the PANIC program (6 chaff + 3 flares). The entries 1 thru 10 must exist, otherwise an error will occur. There must be 10 entries exactly. Keep the existing index order, otherwise there is a high probability that the programs will get reordered on aircraft load and you won't know how it was reordered.

I have added the keyboard binds but have not tested them: Decoy Release Program Knob Up Decoy Release Program Knob Down I must change the names but I cannot think of anything. :helpsmilie:

I´m sorry baltic_dragon, it seems that I forgot to include the campaign intro in my submission to ED. Here's the doc. Campaign_intro.pdf

Yes they are. After all, the sensors are not different from the ones that are on the seeker heads of IR missiles.

A line is drawn for each missiles. In your case two lines are drawn. Because French? ;) Actually because the IR sensor cannot determine range just azimuth and perhaps signal strength. Another reason is that I don't want to copy the A-10C instruments either. The functionality is the same but interface should be different. Remember that these are highly classified systems. Any implementation, is just pure guess work or as I call it WAGUESS.

The campaign and training missions will be available on next 1.5.5 update.

It detects the missile while the engine is burning. If the missile is detected at launch but then it gets outside the sensor fov due to maneuvering, the missile will disappear from the RWR. The audio alarm rings for 10 seconds upon detection, so the alarm will keep sounding even if the D2M loses contact with the missile itself.

Yes. It has been submitted to ED so it will be in the upcoming patch.

I think so. I have no control over that. Thanks.

All missiles within the sensors fov will be detected and subject to the same rule.

Here is the problem: the RWR and the D2M are independent sensors and they both have their own alarms. To prevent sensorial overload to the pilot, the D2M asks if the RWR has detected the missile. If it has then it disregards the threat because the RWR already has it covered. If for any reason the RWR is malfunctioning the D2M will sound the alarm. This last part is still untested so I don't know if it will work as intended.

Due to thecnical constrains I had to implement 3 "eyes" per sensor. The coverage is still 180 degrees azimuth and 80 degrees elevation. Unfortunately there is no way for me to block the upper coverage so I rotated the sensor eyes to simulate it. It looks like there is no "blind spot" but that is an optical illusion created by the drawing of the rotated cones.

You are correct. It has nothing to do with the FBW.

I'm correcting my post: DSV is the acronym for Détendeur à Section Variable (~variable section pressure regulator), it's an annular assembly of eight "pressure reducing valves" that can open or close depending on the engine needs; opening/closing those valves changes the bypass ratio of the engine. It seems that the light turning on when the FBW GAIN switch is activated is a bug.

I will not make any further comment on this thread or on this issue. Whatever changes I make to the DDM will remain undisclosed.

This is the option in the ME: By default the DDM sensors will be mounted. You have to explicitly disallow them.

All INS input headings are in true heading. The system internally converts them to magnetic heading. The only navigation device that uses magnetic heading is the HSI when you are entering a VAD (TACAN offset).

Well, I'm glad somebody can make better video guides than me.

All available images of Mirage 2000Ds using the system show them only in the rear of the Magic II pylons. None mounted elsewhere. Available images of the system mounted in the Rafale show them in the top of the tail, one sensor on each side. Interestingly enought the Rafale uses both spherical and squarish sensors: So, by design it seems that the "sqarish" sensors are the ones limited to 80º degrees in elevation (+/- 40º) due to design restrictions. This also creates a problem with the M-2000C. The Magic pylons that have the sensor are always covered by the wings (see the first image). so I wonder if the down vision is either 40º or closer to 60º. The use of prisms to force view angles is a possibility. What is certain is that it does not have the capability to look up because the wing acts as a huge umbrella.

I deduce that there are two sensor types: one with 360º coverage and another with 180º coverage (the one mounted on the Magic Pylons). What is not clear is if the 80º elevation applies to both or only to the 180.

Okay. somebody was kind enough to send me a copy of the 3428 1990 issue of FlightGlobal magazine where they detail a little bit more about the DDM: Link: https://www.flightglobal.com/pdfarchive/view/1990/1990%20-%203428.html

Just an aclaration. I never said that down visibility is bad. It is obvious that the D2M was designed to detect MANPADs so perfect down visibility is a must. I said that there is a blind spot at the rear due to sensor placement. The C can use it but it has never been fitted with one, probably due to two reasons: 1. The C is mainly an interceptor and France has always had dedicated attack aircraft like the Jaguar. 2. To keep costs down. The D carries it but then the D is a strike aircraft.

Because it is part of the features promised when we began the project.