Zeus67

No. Different positions.

Sure!

Okay. The modeller came through and made two Magic pylons, one with and one without the DDM sensor. Now I need to make the option work.

I'm sorry that you feel like that and I will try to make that possible.

Nothing on the range. As for FOV, this image is very clear in showing how limited it is: It basically can only see down and to the sides with probably a limited rear aspect view. As I said before, the location indicates that the designers never considered using the D2M for air-to-air engagements. It is designed to detect MANPADs, which of course will be below the aircraft. However on the Rafale, they included it from the beginning as an air-to-air defense system: In that position on the top of the tail, it can provide 360º warning for missiles launch above and behind with limited capability below. There are probably other sensors in the aircraft belly to cover that area.

I'll see the possibility of installing the D2M sensors as a pod, that way you can load them or not in the ME and we don't have to worry. I must talk to the modeler on this one.

People don't fight or I will sic the moderators on you. :smartass:

If I can find a solution that does not involve me rewriting all the radar code.

I can do that, my problem is the pylon model. As in I will need two pylons, one with and one without, to reflect this possibility. Let me see what can be done.

At this time I have no idea how to solve this issue that does not involve an extensive rewrite of the radar code. Basically I would have to recode it from scratch. This is at the bottom of my priority list because of that. If I find an easy answer to this problem then I will fix it as soon as possible.

It has the capability, it just does not use it. Probably a money reason since the system is for those aircraft flying close to the ground and under threat from MANPADs.

I'm sorry but I doubt it. The D2M requires a modification in the Magic II pylons so we can model the sensor window in them.

No. I will make them right now. Thanks for the remind.

The Détecteur de Départ Missile (DDM a.k.a. D2M) is an optional sensor for the Mirage 2000. The sensors themselves are in the rear end of the Magic II launch pylons. The Mirage 2000C (Chasseur) does not carry it although the ECM panel does have the switch to turn it on/off. The system is installed in the Mirage 2000D, which is the two-seater attack variant. It is mainly used to detect the IR signature of MANPADs in order to warn the pilot of a missile threat that cannot be detected by the RWR. Since MANPADs have a very limited engagement zone, it makes sense that only the attack variant carries the D2M. I decided to include it because I know many of you like to drop bombs with the M-2000C. Please take note that if you do not carry Magic II missiles, you won't have the D2M system. How it works? Apart from knowing that it sounds the alarm after detecting an enemy missile launch I don't know. Like all other aircraft defense measures, the D2M is heavily classified, so no public info exists apart from some photos showing their location. The coverage zone is my decision based on two things: 1. If I let the window to be blinded by the pylon in the rear aspect, then the blind spot behind the aircraft will be very wide. So I assumed that inside it has a prism that allows it to cover some portion of the aircraft rear towards the engine exhaust. 2. It cannot look too far ahead because it will be masked by the missile in the pylon. So I guessed that the best coverage would be 135º that allows the sensor to cover a large portion of both the rear and the side. There is a blind spot that is exactly towards the rear, but the probability of a missile being launched at that spot is quite low and with distance the sensor fov will eventually overlap. How the threat warning will be presented on the cockpit is a WAGUESS. I think that an aural warning along with a spike (a thin line) showing launch azimuth in the RWR would be the best. The system is WiP and I will try to have it ready this week.

We'll see what can be done.

I would if I could but that parameter is handled by ED.

Both in RL and in DCS the Super 530D has the capability to reacquire a target after loss of radar lock. But there is a caveat: The target must be inside the missile's radar field of view. For the real S530D it is classified, for DCS it is quite small.

Video showing the latest accuracy changes to CCRP with TAS:

The piper shows the point of impact at the indicated ranges. Since the range is always changing, the point of impact moves with it. The rockets/shells should land within the piper. Of course, accuracy is affected by aircraft attitude. At shallow dive angles, the impact point drifts too far from when you fired the rockets/gun to when the rocket/shells impact. A high dive angle and you compromise aircraft safety due to low range to impact. That is why a 10º dive is recommended.

1. You are flying too low to use rockets. The **** KM is telling you that the radar is pointing at the sky so you have no range. 2. I've been told that a 10º dive is the best for either rocket or gun attacks. That means that you must have some altitude.

No. So far the antenna is locked when in TAS. So you will have to maneuver the aircraft. What this means is that the antenna will follow the reticle as it moves left or right due to lateral acceleration forces on the aircraft.

Hello folks. I've just finished reworking the AGR mode for the radar, also known as TAS. This also required a rework for both CCRP and CCIP modes. Most of the changes are internal and are not visible. The HUD elements remain the same. One of the reworks that affect both modes is the bomb release limits table, actually tables since they are quite big and change on bomb type. So now you will see a big X across the HUD when you run afoul of one the limits. This does not means that you won't be able to release the bomb, it just means that it is dangerous for you to do so. But let's move to the accuracy part. So far CEP for both CCRP and CCIP has been bad. I've worked these last two weeks trying to improve on them. I feel that they have indeed improved but also I feel that there still is room to work. But, now it depends on where I must apply myself. CCRP: 1. If you do not use TAS, the behavior and accuracy has not changed. The aircraft targeting computer will try to elucidate the spot that you are aiming at and will extrapolate terrain height based on your altitude above ground. There is a high probability that the bomb will overfly your target spot. That is, it will hit long on elevation. 2. If you use TAS, the radar will compensate for lateral deviation and the targeting computer will calculate the position of your target based on slant range. This also means that the target reticle will now move left or right depending on the aircraft's lateral velocity and it is tied to the antenna on elevation. So the spot it marks on the ground is the spot where the radar beam hits the ground. I've flown many test flights testing the changes and so far the bombs are now hitting on azimuth but they tend to fall short on elevation. That is they strike the ground before they reach the target. Now, curiously the distance between bomb strike and the target starts to shrink the closer to the target you make the lock and release. I've checked the bomb flight using F6 after release and it flies true to the target but if they fly for too long they start to lose forward speed and drop to the ground. As you can imagine, I am not happy with this but I cannot find a reason why this happens. So it looks like I will need to ask ED for help on this to identify where the problem is and thus increase accuracy. The new TAS targeting solution will be available on next release. CCIP: 1. No TAS: Same as before. 2. TAS: With the new ground level method it is better. I feel it should be even more accurate, but it is a big improvement. For an 8 bomb load you can have 6 of them drop within the area inside the targeting hexagon. Why two of them decide to hit outside, I don't know. I'll try to see what is the underlying problem there. This has also been extensively tested by me, using Active Pause. Of course, I am a lousy bomber so when I go in normal mode I tend to miss the target. I have some ideas to improve TAS antenna movement on this mode but I need to be clear what it is what I need to do. So here you have it. A big change in bomb accuracy that I feel it is an improvement over what we had before and the best thing is that I did not have to cheat like some aircraft that I know do. I'm closing shop for the dates 2016-1028 to 2016-11-6. I am leaving out of country for a week. CptSmiley has graciously agreed to make certain that these changes are in the next release. I have already submitted them to ED but there are always last minute changes in the sim that we need to account for. CptSmiley will make sure that our code will be 100% compatible with the next release. Thanks for your support and I will see you in November.

Go to Special Options to deactivate the gyro drift.

I don't know. We'll check.

There is no need to memorize the coordinates for each parking spot. All you have to do is press F2 and you can read current position in the status bar.