jojo

GTX1080 TI, I rolled back from 457.30 to 442.19 to get rid of radar FPS bug.

It’s true, SERVAL wouldn’t spot Spoon Rest (A band, 275km range) or Flat Face (C band, 250km range) EW radar. But these would overload the SERVAL display. And you know you have to be on the deck if you want to be unnoticed. At least the system covers Fan Song and Low Blow which are the engagement radars. These are the main threat radar. So the pilot would know when he is targeted by these systems. Most engagement radars would be E band and above.

I answered you on MP, but it can be interesting for others: SA-2 FCR: Fan Song E/F or G (depending on variants) SA-3 FCR: Low Blow I (missile remote control on band D). SERVAL: E to J. SABRE: H to J. SERVAL should at least detect SA-2 and SA-3 tracking. SABRE shouldn't be able to jam SA-2, but SA-3 yes. But DCS isn't as detailed about electronic warfare. Sources: Flight Global – Electronic Warfare Directory - 1989 Jane’s radar and electronic warfare system Forecast International

To avoid spamming the project update topic, share here pictures, videos or informations about various variants of the Mirage F1 And the Voltige Victor. Display starts at 6'00". Mirage F1 CR last air to air gun training.

Edit.

I'm not sure. I would say it's an easy modification. But given the fact they didn't have Super 530F before procuring former Qataris Mirage F1 EDA, they probably didn't do it. Spain bought EF/A-18A (C.15) in the 1980', upgrading the Mirage F1 was probably a lower priority. It would be wise for Aerges to make a French Mirage F1 C-200, apart from the weapons, it's very close to the CE.

This is wrong. Mirage F1 CE is just Spain variant of the Mirage F1 C. Mirage F1 EE is a Mirage F1 C with INS navigation system. Mirage F1 EQ5/6 were totally multirole: - AA with Super 530F (not Super 530D contrary to what he published multiple times), and Magic. - AG with dumb bombs, laser guided weapons such as BGL and AS30L. - anti-ship with AM39 - anti-radar with BAZ-AR (export of ARMAT) - kind of jamming export with REMORA pod. Nobody else got the full kit.

I said during the 1980'. Today the most advanced Mirage F1 are the Moroccan Mirage F1 M VI, with weapon system derived from Mirage 2000-5, full glass cockpit, Mica missiles and so on... Spanish Air Force did have different sets of RWR in its fleet...

During the 1980', the only one who purchased full options Mirage F1 were the Iraqis with EQ5/ EQ6. Nobody else ever got so advanced Mirage F1. I do hope that we get a French Mirage F1 C-200, very close to Mirage F1 CE. Air refuelling, BF radar threat warning system, Barax jammer pod (also seen on Spanish Mirage), but Super 530F, Magic 1 and later Magic 2. I guess it would be very hard to find data on Exocet use on Mirage F1. I don't even know if any customer outside Iraq used this option, same for targeting pod. Good summary in Spanish: https://www.taringa.net/+militares_en_t/los-mirage-f1-espanoles-hasta-el-f-1m-actual_16gl5c

With the radar FPS bug, even at half price it's too expensive. I should have come here before buying :mad:

I tried. I also tried MSI Afterburner. Maybe I missed something, but it doesn't provide detail of GPU Frame Time and CPU Frame Time. At best I have the global Frame Time corresponding to my frame rate. Oculus Performance HUD used to provide that data. But now it is being turned off by DCS World !!!

:cry: Ok, tank you. At least I am not mad, I tried it long ago and it was working. So does anyone have a solution to display CPU and GPU frame time with Rift S ?

Hi, I would like to run Rift S with Performance Head-Up Display enabled in Application Render Timing mode. I tried to enable it with Oculus Debug Tool and Oculus Tray Tool. The HUD is visible in Oculus Home but disappear when DCS starts. Does anyone know hot to do it ? Thanks

Hi, I would like to run Rift S with Performance Head-Up Display enabled in Application Render Timing mode. I tried to enable it with Oculus Debug Tool and Oculus Tray Tool. The HUD is visible in Oculus Home but disappear when DCS starts. Does anyone know hot to do it ? Thanks

If you disengage the AP in climbing turn, you will have to fight your stick to get back manually to level flight...because you are trimmed for a climbing turn :smilewink:

AFAIK, this is precisely how it's behaving in game and the source of his problem :smilewink:

AIM-54 needs a PD-STT in SARH :smilewink: http://www.heatblur.se/F-14Manual/weapons.html#id3

The last time I tried, TWS AUTO was working well. If it's broken...we might as well wait for a fix :(

You should not disengage auto pilot during a turn or a climb. Use AP SBY first to bring back to wing level before disengaging. If you forgot, re-engage AP then use AP SBY. Also don't use AP during formation flight (at least not maneuvering formation flight). For instance it's OK next to the tanker just to trim "on speed" during straight leg, then disengage. REARM CDVE on landing gear lever panel may do the trick, but it isn't the intended use...

Yes, you need to maintain radar contact, this is what I meant when I said you need to keep targets within radar scan area. TWS = maintain TWS contact at least until targets blinking at TTI =16. STT = maintain STT lock until impact. launched active = mad dog (fire & forget). But please read the manual :smilewink:

Yes, and someone correct me if I’m wrong, but from what I understood, the AIM-54 in flight updates its flight path from target’s echo in TWS (kind of SARH) rather than up link from Tomcat.

There is the intended functions described in HB manual...and there is how it works in DCS. It looks like HB is struggling with ED API to get AIM-54 to work as intended. The way it’s described in the manual, if you launch in STT, it’s a Fox 1 until impact. If you loose the lock, it won’t switch to active mode. It isn’t that clever. When you launch in TWS, you should keep the targets within radar scan area. The radar will send “active command” to the missiles, which will be shown in the cockpit at TTI = 16s with targets flashing. If you go cold before “active command” is sent by the radar, the AIM-54 won’t go active and is lost. The active command is sent automatically, RIO can’t force it. Off course you can also launch active from the missile release, but it’s rather intended for short range.

Nice, keep training and you will become even more effective and accurate :thumbup:

I only saw pictures of Eclair-M mounted on Mirage 2000D and Mirage 2000-5F. There are pictures of Mirage 2000C RDI with Eclair, but not many. Indeed the Eclair is labeled for 2 flare racks and 1 chaff rack. https://forums.eagle.ru/forum/englis...56#post4053656 EM = Chaff IR = Flare The problem is likely a core DCS issue since you can trade flare for chaff and the opposite. In DCS you can load up to 32 flares, but you can't add the 18 chaffs from Eclair pod to go up to 130 total (112 internally). Smaller flare racks have been developed to carry 16 per rack (so 32 internally without Eclair pod, 40mm diameter instead of 60mm). I don't know if it's in use on Mirage 2000C RDI ? IRL trading the drag chute or hook for additional decoys is a safety issue. So the threat has to be really serious to carry the Eclair instead of drag chute. Originally Eclair was developed in house by AdA because of SPIRALE delay (internal decoy dispenser system integrated with ECM). https://forums.eagle.ru/forum/englis...17#post4053617 ECLAIR without SPIRALE. Later it was kept to further increase total decoy count if necessary. Here is a picture of Mirage 2000C RDI S5 from Cambrai (coded 12-KO). Live missiles, SPIRALE + ECLAIR https://www.alamy.com/stock-photo-oct-10-2013-french-miragemirage-2000-is-a-multirole-combat-fighter-84350250.html The most likely use of this configuration was operation "Trident" in 1999 over Kosovo. Mirage 2000C were deployed from Istrana in Italy. Eclair-M is industrial solution by MBDA.