fixen

The texture on those dishes have no extra impact on performance compared to dishes that would not have the writing on it. Same with the trashcans. It is just a texture file and if it is a metal texture or trash texture, it does not impact performance. What will impact performance is the resolution (which is quite low as we can see) and the amount of polygons. If you give those dishes a rounder look, they will eat more gpu power, because rounder means more poly's. I think they do optimize well in general and some details that look unnecessary might just bring that bit of life to the picture that it needs. When you take it all away it might suddenly look very bland.

I would the idea of not seeing yourself on the f10 map If the f-15/su-27 had the ability to make custom waypoints, which is not the case.

Then you are locking someone who is jamming. The jammer causes false detections and the real aircraft might still be way further away. You know its not a jammer when the intercept speed and other information is displayed next to the bogey.

I don't think you have to be afraid for a long range shot aim-54. When you go full defensive you will bleed its energy quickly. Though I think lethality will be much higher when it is fired at aim-120 distances or slightly longer ranges. It will definatly be Lethal for fighters at those ranges.

I might sound like a bit of a **** here, but you were just lucky the proximity fuses are broken currently, because you would have otherwise died from every missile he fired. Still a fun video though.

Check what the enemy aircraft is doing. Look at a tacview for example. I find the mirage 2000 radar pretty good. The moments I do lose lock is when the enemy is in a notch. That is why I tend to fly lower than the target I am looking at so that it is more difficult for him to go in a effective notch with terrain behind him.

You need to test some systems before take-off which will cause the DECOL light to go off. The switches are on the left console. A green light needs to appear to have passed the check. Check chucks mirage 2000c guide. It has the startup sequence in it. I don't get whats so strange about it. You put the switch in A/G mode when you are flying with a droptank or heavy stores to avoid them from breaking of the aircraft. Ofcourse it is G limited, more then 6 G's and your fuel tank says bye bye. Same goes for roll.

Well, we know the following things: - The radars are very closely related IRL, with the Su-27 having a bigger array among other things - ED made their modules so that there is no difference between them on the RWR (A-10, F-15) So they may, or may not show up seperatly on the RWR. However, I don't think the Su-27 and Su-33 should show up seperatly, since they use the same radar. I don't find this very important in the sim, but it's more that I'm curious now. Though I do find the issue with the ARH missiles important. I posted it on ED's side, so I'll see what that brings.

I think this can be done by RAZBAM themselves (though not sure). If I'm correct they choose the label that is displayed by the RWR for every aircraft. They have a database of icons for the RWR to display which they match to the aircraft that is pinging the RWR. So they should change the Su-33 and Su-27 RWR icons to Mig-29 icons, to simulate the RWR not being able to discern aircraft types due to them having the same radar.

I posted an issue I was experiencing with the Mirage 2000C's RWR on RAZBAM their forum, about the abillity of picking up a launch warning from the F-15c when a ARH missile is launched. The way it works in the F-15c and Su-27 when being launched at by a ARH missile is that you only pick up a launch when the missile goes pitbull (M) and never get a launch indication of the launching aircraft. However, the Mirage does pick up the ARH launch, even when fired in TWS, before the missile goes pitbull. RAZBAM have responded that they can not program their RWR to only detect SARH launches and not ARH missiles launched in TWS. Quote by Zeus: The RWR in DCS gives four signal types: UNKNOWN, SEARCH, LOCK, LAUNCH. It will return only ONE of those types for a given emitter. So if an F-15 fires an AIM-120 while on TWS, then the RWR returns LAUNCH for the F-15 regardless of its actual operational status. Somehow though, the F-15 and Su-27 do manage to not give a launch warning when launched at by a RWR. How is this programmed and how can RAZBAM fix their RWR? The whole thread where the issue is discussed on RAZBAM's side can be found here: https://forums.eagle.ru/showthread.php?t=174789&page=2

Then I wonder how ED (or Belsimtek for that matter) does the RWR on the F-15c, since that can cleary see the distinction between a SARH and ARH missile launch (or more like, not see the ARH launch). Ill post this thread with some extra info on ED's side of the forum, because now I am really wondering how this works.

Thank you, that also works. Would still be nice seeing it implemented officially though.

Exactly, but I bound the buttons and they did nothing. So I wonder If they are broken. I am talking specifically about the "low->int->high" and "high->int->low" PRF controls. The other ones do work however.

Allright, I did some limited testing and will do more when I can find somebody to test with. First let me tell you how it currently works when fighting in the SU-27 or F-15c against a ARH missile fired in TWS: - First step: You are being scanned by enemy aircraft. The RWR shows you the contact, but does not give you a warning tone yet - Second step: enemy aircraft launches ARH missile from medium range in TWS. You can still see the aircraft on your RWR but no lock or launch warning since the missile still has not activated it's own radar and the launching aircraft does not need a hardlock for guiding the aim-120. - Third step: The missile goes pitbull. Your RWR now picks up the aim-120 that has activated its radar. Your RWR immediatly gives you a launch warning tone. The launching aircraft is still displayed as simply scanning and not launching. In this example the lock warning is never initiated by the RWR, since there was never a case of hardlock. Only scanning and launch warning when the aim-120 turned on its radar. A enemy aircraft can also launch the aim-120 when in STT lock. In that case you will hear a lock sound and when the missile goes pitbull a launch warning sound. Now what happens in the mirage: - First step: You are being scanned by enemy aircraft. The RWR shows you the contact, but does not give you a warning tone yet. (same as in the F-15 and Su-27) - Second step: enemy aircraft launches ARH missile from medium range in TWS. You can see the aircraft on your RWR and hear a launch warning with a F-15 flashing on RWR, but the missile has not activated his own radar yet. The F-15 is still in TWS, which should not give a launch warning, yet in the mirage it does. - Third step: The missile goes pitbull and activates its own radar. You now see two launching contacts on your RWR. The F-15C (which you should not see as launching when comparing it to the F-15 and Su-27) and the missile which you should see. If this has to do with ED's coding I will post it on their forum aswell or if you tell me this is how it should work I won't do anything. But the thing I was confused about was the fact that the F-15C and SU-27 never give a launch warning when the missile has not activated its own radar yet, while the mirage does. It helps quite a bit when in a BVR fight, but might be unrealistic. I thought that one of the minor plus points of an ARH missile over SARH is that you dont know when it is fired except once it closed a lot of the distance allready.

Thank you. I have one more question: are the "low->int->high" and "high->int->low" PRF controls broken? They dont seem to change the PRF frequensy. I thought I could use these switches on my HAT (still had 2 free buttons) for increasing the frequensy and lowering it.

I was wondering what the function of the magic search(called "magic unlock" in game)/nav update button was. I can not find anything about it in the manual apart from it being on the mirage 2000c HOTAS.

When the aim-120 is fired in tws I should not get a f-15 launch warning right. Because the radar does not change modes then. It can guide the aim-120 without going into continuous wave mode (which would happen when the radar launches a SARH missile). Doesn't the same apply to a stt lock? You should only get a lock warning but not a launch warning? The aim-120 does not need a continuous wave for launch. If im correct (which don't get me wrong, I might not be), the radar still operates in pulse doppler mode when stt locked but has a continuous pulse doppler scan on the target (not sweeping like in tws) which you pick up as a lock warning. You get a launch warning when the rwr detects you are being painted by a continuous wave (not pulse) which would happen with a SARH launch or when the aim-120 seeker is in range. But I suspect not when a aim-120 is launched in stt mode. Then you would first pick up a lock from the f-15 and then a launch warning when the missile goes pitbull (M), but not a launch warning from the launching f-15. Now I get a launch warning when the launched missile leaves the rail, which I think is not correct (except when launched in close proximity when the missile goes mad dog.)

Sorry i spoke to soon. I am also getting a missile warning. But the F-15 is flashing aswell. Is that just to indicate a hard lock?

Is it correct that the RWR of the M2k gives a F-15C launch warning instead of a "M" for missile warning when a AIM-120 is fired? I made a mission for training and every time the F-15C launches a aim-120 at me, I see the F-15C contact on my rwr flashing, but not a M for missile. Since it is an active missile, shouldnt I get the missile as a contact on my RWR and not get a launch warning of the f-15?

It would be nice if they could make a 3 position switch abstraction with: - Magic select else PCA select - AA gun select else PCA select

There are enough channels to choose from.

Dispenser programs would be nice. +1

It started out as a freeware project but it has become a payed module. I think they could not change the name of the thread, so thats why it is still in the title.

No. M2000C cannot carry it. It has been discussed many times. Also things like exocet are not carried.

Please keep in mind that the icons for the aircraft and missiles in tacview are enlarged quite a bit. What in tacview might look like a near miss, might infact not be that close at all. In tacview you should be able to see the distance between two objects. Take a look and see how close it actually is. Don't get me wrong, it might still be very close, but I have made mistakes in judging distance between objects due to their portrait size in tacview.