Jump to content

Steph21

Members
  • Posts

    506
  • Joined

  • Last visited

Everything posted by Steph21

  1. This is an old bug, that is still present on latest Open beta. From latest Razbam manual, page 207 and 208, the mirage 2000 is equipped with 16 flares in the SPIRALE system, and can add up to 3 rack of 8 flares (24 flares in total) on the ECLAIR Pod if equipped. 1st bug: When getting airborne with the default 16 flares, only 14 are available as shown in track attached. Program 8 was used for this test (default program created by Razbam, dropping 6 flares per salvo), and from the F2 view you can see, that first 2 salvo drop 6 flares each as expected (12 in total), but third salvo drops only 2 instead of 4 (6+6+2 = 14 instead of 6+6+4 that would make the 16 mentionned in the manual). 2nd bug: In the Rearm menu, qty of flares can be increased above 16 without having the Eclair Pod mounted. This should not be possible. 3rd bug: In the Rearm menu, qty increase by 16 and we can go up to 162 flares. We can select following values: 0,16,32,48,64,80,96,112,128,144,160,162. And this give acces to the qty of flares selected (you can test it with the program 10 dropping 32 flares per salvo) which is not realistic at all. Based on information given by the manual, the only values available should be: 0,16 witout Eclair Pod 0,16,24,32,40 with Eclair pod mounted: 16 from SPIRALE, and then increment of 8 (not 16) for each rack added in Eclair Pod Chaff Qty Rearm Menu.trk Chaff Qty 14 instead of 16.trk
  2. Strange to request so many new track files for bugs not listed as fixed or worked on in the change logs of the last update. Will you request those for each update for bugs not listed as fixed ?
  3. From what you describe, looks like an old bug that has never been sorted. If i remember correctly, it was listed in Razbam bug tracker. To be confirmed by Elmo
  4. Steph21

    CADR AR

    Nice, hope we will hear more about it from Razbam. Should be useful coupled with DO to help with reattack after a pump/abort. And could also help for SA. Kinda hard to follow up new features implementation and bug fixing sometimes on the Mirage, as change logs provided with Open Beta update are not always listing all the stuff included in the update.
  5. Issue is still here on latest open Beta here is a track file showing the issue in a mission on Caucasus with start time set at 03:59:00 am Local time (23:59:00 Zulu time the day before). Clock stays stuck at 00:00:00 (Zulu time) until 04:00:00 am local time (00:00:00 Zulu time the same day as local time), then seconds needle start moving and clock displays current Zulu time Clock bug Zulu_Local time.trk
  6. As long as it continues to work as it is right now in the meantime, i'm fine with it as it can be used without that much trouble.
  7. TrueGrit, can we expect some news on the progress made on your Typhoon (data gathering/validation, 3D model, systems coding,...) before end of the year ? It has been a massive shitty year, but an update from you guys would make it a tiny less shitty ;)
  8. Just to add that it seems to be a displayed issue only. Fire computer seems to take into account the feet value initially entered, even if value displayed is then not correct as described above.
  9. I've reported the issue long time ago: https://forums.eagle.ru/showthread.php?t=279185 It's not linked to accumulated drift as i could reproduce this issue with drift disabled and from airstart near the target with drift enabled. Also, when doing INS Update with OBL mode or PI mode, when clicking on REC on the PCN to reject the update, you'll see a second Drift value displayed on the PCN, you have to click REC a second time to reject the Update. Displayed drift on PCN, doesn't correspond to the drift of the + mark on the HUD. Seems the value displayed is way off, and if it's >15Nm you won't be available to validate the Update. If you keep spamming the INS Update function while targeting the same update location, drift value will go down and eventually goes above 15 Nm, enabling you to validate the update and set drift back to 0 (as currently a validated INS update set drift back to 0, whatever the quality of the update) I'll let Helljumper answer your question, just wanted to give some extra input on this issue that i could reproduce on numerous occasions.
  10. Seems it works with FCLS in landing gain, so when landing gear are down or Air Refueling set to opened. In cruise gain, OFF position is not recognized Strange
  11. I was asking Galinette :) So he could see why his post was set as duplicate :thumbup:
  12. Isn't your issue the same as described in the link below and marked as "reported" ?: https://forums.eagle.ru/showthread.php?t=286885
  13. How can we get contradictory infos if they all come from official sources of Mirage 2000C pilots/engineers? Any chance SNA would differ from 2000 variants, from N to C for example, that could explain it (I guess 2000D can be put apart)? Mirage 2000 put apart, still wonder the point of high angle dive bombing with high drag bombs. Official notebook from USAF for the f-16 gives max angle of 15° for bombing with high drag bombs for example. Low drag bombs are use for higher angle deliveries. So I find surprising that AdA would use such tactics, but that's just me. At least Elmo is here talking with us, so you could at least watch your langage.
  14. It should be introduced with the new incoming F4 standard
  15. It's like that since new dcs lighting implemented in 2.5.6 All modules are impacted afaik but some give the option to tune the gain in the controls. Not the case for the mirage. You do have a switch on right console that you can set to nvg, it will adjust some of the lighting for nvg use You can also adjust HUD brigthness with the scroll wheel near the switch use to turn on HUD display
  16. Steph21

    RWR update

    Hi Elmo, you mean that based on AdA and SME feedback, the M2000C has no specific RWR symbology for SA-2 and SA-3 tracking radar? In current default file, 2 is used for SA-12 wich is not available in DCS, and 3 is not used. I guess SA-2 and SA-3 are shown as U on RWR currently. From what i understood from Zeus, he took the info provided by AdA and tweak the RWR symbol list to ajust it for assets modeled in DCS. I think that tweaking it a bit again and assign 2 to SA-2 and 3 to SA-3 would make sense, as currently 2 and 3 would never appear in DCS, whereas SA-2 and SA-3 are available as SAM assets. Personnal customisation is another story.
  17. I feel exactly the same. They teased the Meteor in some screenshots, another European weapon. Still not confirmed officially though. Might also get some other MBDA weapons later on.
  18. Thx, i've add tracks to my previous post
  19. Yes i've seen it, but it doesn't mean anything as you don't know what were shoot parameters, objectives of the tests, target parameters...etc Here is a working video, showing shots at low altitude (5000 ft for the shot from the Rafale), low range: Here is another short one, at higher altitude: But if you want to believe that MICA has only a 20km range at high altitude, i've no problem with it :thumbup: Just be sure you're not talking about the VL-MICA, which has a 20km range as it's being fired from the ground. French Air Force is very happy with the MICA on their 2000-5 and Rafale. And they are now delighted to get the Meteor to work with the Rafale AESA radar. MICA NG will soon be available also and will be a good complement to the Meteor. But as "ATE" mentioned, we don't really care about the Typhoon in France. It doesn't fulfill the needs of our French Air Force and Navy, the Rafale does. Furthermore we are working with Typhoons, not against them. We are happy with our Rafale. If you are happy with your Typhoon, then everybody is happy :) i'll be happy to give the Typhoon a try in DCS, and then i'll be delighted to switch to the Rafale if it's ever implemented in DCS.
  20. Way more, it's in the 60km range for IR version and 80km for EM version. Only the seeker changes between IR and EM version. Not talking of the MICA NG to come that will have a greater range.
  21. Would be great to add SA-2 and SA-3 in the default file also.
  22. Works fine when no dropped tanks. Just tested it on latest OB: - Air Start, slick configuration, i get the notification - Air Start, 1xRPL 522 or 2xRPL541 configuration, jettison tanks, i don't get the notification i can provide tracks if some other guys can confirm the same behaviour. AAR notank.trk AAR cenraltankjettison.trk
×
×
  • Create New...