Tango3B

This has definitely NOT been fixed. Issue is still present. DGFT mode STT can‘t hold any lock for more than a few seconds. This is quite a biggie in PvP and needs an immediate hotfix! Also, „fixed“ needs to be removed from the thread‘s description. It is just not true and highly misleading. Furthermore, evidence in the form of tracks has already been provided. Thank you.

Yes, TEL mode works just fine. A quick correction on this, though. TEL is by no means a vertical scan. It is more like a HUD scan, actually. Another note: BPZ, the other ACM mode, is currently not working as intended so do not try that mode.

Hi. IC mode is a short pulse mode. This would then also be supported by a certain explanation in the real world F1ED manual which sys the following under "remarks" in section 1.75/15: So, looking at this in formation we can probably deduce from this that this mode is intended as a medium/low altitude mode in our version of the Cyrano radar which does not have the MA and LA modes of earlier Cyrano IV versions. Also, keep in mind that the radar is currently very much work in progress so there might most probably be some noticeable changes to the radar beahvior coming in future patches which will be affecting the simulation of PRF, clutter and things like that. Also, "Cyrano" actually sports a TWS mode which is currently missing. Anyway, I hope the above picture at least sheds "some" light on your question. I would also like to hear from Chicho...maybe he can expand a bit on this? EDIT: fyi, the F1ED manual is plublicly available and unclassified.

Okay, got your intent there but let‘s talk about NCTR in this context. ED hardcoded NCTR to only work at/or below 25nm. This really is quite unfortunate. Why exactly is that? NCTR prints can, under the right conditions, be obtained from far greater ranges. Can we please agree on the fact that this has to be coded in a much more dynamic way? We really need to get rid of this static radar behavior. Being fully aware of the fact that NCTR always was and still is kind of a hot topic I want to point to Razbams form of implementation which really shows the beauty of what can be done. I really hope we will see some of this coming over to the F-16 in the future, too. Thank you.

You are making some pretty false assumptions here. I strongly suggest you double-check your sources. If you want to have access to the appropriate performance data I strongly suggest you take a look at the actual flight manual of the F1ED version which is publicly available and also contains all sorts of performance charts and data you might be interested in. This should hopefully clarify most things for you. Also, if you have trouble using the radar and you think there is something wrong I would kindly like to ask you to open a different thread and please also include a track. A short vid would also help to support your claim. Thank you.

She will eventually be patched to that standard, my dude. And you made the right decision...the F1 is just about to become polished...being more than a "DCS year" old you can expect to see constant changes in the weeks to come. Currently, I guess that the main focus is on the radar, the INS and certainly bringing the F1BE out. Which actually shouldn´t be too long from now, by the way. Also, a few other systems like the Phimat should be close to completion. So yeah, if you want to fly something really special and exotic, you just can´t go wrong with the F1.

Let me be very clear here, ECTAE. Some of us who answered the smear posts by Thinder wanted to set something very straight. The FM is fine as it is. Some tuning here and there of course, right? Right. This was the original intention. And we gave tips. Mkay? Also, Chicho happens to be a former Mirage F1 pilot. He gave great advice here. And CrazyGman really made a nice vid showing the beauty of the F1. Also, I hope that my posts concerning some tactics were kind of useful. Unlike Chicho, however I never flew a Mirage. I fly a different jet in a different airforce but you can bet I know exactly how BFM works. Anyway, the three of us wanted to help others who do not understand the very way you need to fight in the F1. And this leads us to the next point. A lot of people flying PvP in DCS take flying and managing the aircraft and its systems very very serious. This is why some of us dove a little deeper into detail. These people want to know this very information. This has certainly nothing to do with rivet counting. Sure, you can hop into the F1 and have fun without all of this knowledege...but isn´t it much nicer to know more about the how and why and actually do stuff right? You decide...

Exactly this. And if I may add an additional point to chicho‘s excellent description here. The F1, as an interceptor, has a an additional advantage over most of the other contemporary aircraft it may enconter as an opponent. Speed! And she also accelerates reasonably well. You also need to use that to your advantage. So if you‘re fighting on one of these well known Cold War servers always keep your speed up and quickly extend if you can‘t outmaneuver your opponent. This is absolutely valid and no shame. Just extend for some time, then turn back hot an give him a 530. Always make a gameplan if/when to disengage. Think ahead and use your speed. Even a well flown 21 has a hard time catching you on the deck…

Hold your horses here, Thinder. The FM is actually quite close to the performance charts publicly available. This is a fact and this has also been tested. Also, AERGES did a really good job adjusting the FM over the last few months. Furthermore, I strongly agree with Fausete that in the F1 you really have to understand the basics of dogfighting and you have to have a constant eye on your energy state. The F1 is easy to fly but a lot harder to fight in. Avoid getting slow, stay above 400kts. Best is around 425-450kts. Try barrel rolls, flat scissors and Yo-Yos. Have an eye on your fuel. If you‘re above 50% of fuel she's a bit like a pig. At or below 50% of fuel she really starts to shine. Also play with the curve setup for your stick. This is very important so you don‘t constantly overshoot AOA. You really need to learn flying her. Treat her nice and she‘ll do some amazing things for you. Indeed, you can beat any contemporary jet. Just use the right maneuvers and fly smooth. Don‘t yank on the stick like a madman. Again, learn the fundamentals of dogfighting and you‘ll get better eventually…just keep trying and you‘ll succeed.

Yeah, I totally agree. She´s a tremendous amount of fun to fly. Also, the radar simulation is flat out the best in DCS. Period. There is nothing like this. And guys....the best thing is it only gets better from here!!! Just imagine for a sec how she performs with JTIDS, HMCS and 9X...man, this will be quite something. What a nice module to fly in...10/10

Many thanks for todays update. You did a really good job, that's exactly what I meant with a brief update on your development work. I think the update was at exactly the right time.

First of all thank you for your reply 9L, I really appreciate it. The slightly negative undertone of the previous speaker aside, I think many of us here in the community have really been patient beyond measure with regard to this very topic - with all due respect. The whole number has been dragging on for an entire year now, please don't forget that. I personally totally understand that certain things take a lot of development time, at the end of the day you want the result to be right. I totally get that. But... a brief intermediate status of things must be. I think it's totally understandable if some in the community are starting to get a little restless as this not only affects the F/A-18, but also the Viper. And we don't want to fool ourselves, please. On your credit side there is currently not much progress to be seen in this regard. Still, I think many of us are keenly interested in this very topic. And rightfully so. So please just think about what you could present to the general public in the near future as a kind of "update teaser"... you just can't come along without it at this point. We've heard long enough about promises and postponements. Now it's up to you to simply deliver. And please guys don't derail this thread. Just leave these words as they are. No small wars please, everything else has been said on the subject, I think. Thank you, good luck and all the best to the team.

ED had the following to say in their Newsletter from January 13th, 2023: "Radar Update. In parallel with refactoring the Flight Model and FCS, a refactoring of the Hornet radar is well underway. Key elements to address are improving the look-down, PRF, scan azimuth and more in order to offer improved detection and target tracking simulation." So, ED said it is "well underway." Then again, ED went completely radio silent on this topic. Same goes for the promised white paper regarding radar performance. I would also like to hear where we currently stand with the progress made on the radar. Any official statement on this? Any news to share would be very much appreciated... Thank you. Link to said Newsletter January 13th, 2023:

So, what I meant to say here is that the antenna dish should always point in the same direction as the aircraft‘s nose in relation to the horizon unless I manually manipulate the antenna elevation and/or the azimuth. Another exception would be if the radar is actually tracking a target, of course. I think this is common sense, right? In the F-5, though if I pitch 20 degrees up my radar does not point to where my nose is actually pointing. The antenna dish is moved 20 degrees down in this case and I would have to constantly keep the antenna centered manually to point where my nose is pointing. This is obviously wrong and should be reviewed. I hope this clarifies my point.

Okay, so today I tried the F-5E. I actually don´t know if I should laugh or cry after seeing that the radar is not stabilized to the artificial horizon of the aircraft but to the actual (!) horizon. I am basically speechless. Who had the bright idea to actually code it this way? And yeah, I know what it is written in the real life manual but this does refer to the ADI of the jet, of course! Like in every other jet in this world, by the way. You would find the exact same passage concerning the way the radar is stabilized in the technical description for the Cyrano IVM, for example but of course the ADI is meant. No one in his sane mind would actually stabilize the radar to the actual horizon which would mean if I climb 20 degrees nose up my radar would then be looking 20 degrees down. This is hilarious to say the least. Somebody must have interpreted this completely wrong in the rl manual when this module was developed. I think this has to be thoroughly reviewed.

Yup, copy that and the current state is fully understood. Anyway, your dedication to the F1 is very much appriciated. Credit where credit is due, right? Right. You guys do a phenomenal job on this kind of an exotic module. I love it, the F1 is just that kinda gurl...you know?! ;-D Concerning the PHIMAT. As long as it is not ready for public release, please let us equip the 3d model as a "dead" placeholder to balance out the BARAX pod, though if in any way feasible. Or, and I fully understand that this is unrealistic, please let us equip the BARAX on both wings. You´ll get the control panel for it just on one side anyway but you would be able to carry a viable (balanced) MP loadout without bothering too much about trimming. Please consider adding this for the time being as the BARAX pod is just too good to not be carried while its counterpart is still in development. Anyway, thank you, Fausete!

Wow, now this is what I call good communication with your customers and dedication to your product. Excellent job, fausete. Keep the good stuff coming…

Excellent . Good to hear you are working on improvements in this area since currently the noise simulation sadly is completely static regardless of certain conditions and altitude. Really looking forward to the upcoming changes…

Okay, interesting. Let‘s see how this works out, then. Anyway, I would like to hear from the Dev team itself where they currently stand with their progress. Also, while Discord might be a nice supplement to the official discussion around a DCS module I feel the place to share such vital information in the first place should be this very forum, not any third party source. Thank you.

@6S.Duke Hey, has there been any progress on this bug? I mean it is the middle off april now, right? And since there was zero love for the Macchino in the most recent patch I think now is a good time for an update on your part, right? Right. This extremely annoying bug has been there for much too long, so I would really appreciate an answer. Thank you.

This has already been reported as part of this bug report, too: A seperate bug report may help, though. Can you please, by any chance, add a track of this happening on your system, bones?

Yup, can confirm the BARAX controls do not work when you cold start the F1EE. The clickable functions are not working at all, currently. Air start/hot start however does actually let you activate the korry to start transmitting from the BARAX pod. The rest of the controls are dead, though. So the BARAX is basically borderline useless in its current state. Concerning the underwing drop tanks I can also confirm that the tank empty lights do not come on. I think, we do not need an additional bug report for this. It is 100% reproducable for all clients in MT/ST and SP/PvP. Something really went wrong with this patch, apparently. Can happen though, no hard feelings. Aerges will fix this, eventually. ++ One thing to add concerning the BARAX pod, though. Even though the PHIMAT pod and its controls do not seem to be ready yet, please add the Phimat pod as a dead loadout to the loadout options to counter the BARAX pod. Aerges, you would do us a very big favour, if you would do that. Unless the BARAX is not "balanced" out by the PHIMAT many guys struggle to equip it as a viable combat loadout which is sad because the pod is really really working well - and it should be, the French pods had a very good reputation for being very effective and as a bonus very light, too. Also keep in mind to balance the BARAX pod drag a little bit more. The pod weighs only 89,275 kg compared to a MIAGIC II at 89,357 kg. So, the BARAX really should not have that much drag to it. It is very slick, actually compared to the comparable Iraqi Remora pod, which was slightly heavier and more bulky. I think, we need to adjust the drag values a little bit more to make it more realistic since it currently let´s the wing drop like a sinlge MK-84. ++ Aerges, thank you for the recent FM fixes and an overall good patch - and the F1 in general, I really love it. It has become my most loved module in DCS - by far. The above mentioned issues concerning the F1EE do have to be addressed a.s.a.p., though. Greetings, Viper.

Good spot. Yup, I just noticed the same. The "centerline tank empty" light does not come on. In fact, this seems to affect the entire fuel sequence lights - only tank group No. 3 lights come on when you get down to 1200lbs or less. Dear Aerges team, please add this to the above bug report. Also, this seems to exclusively affect the F1EE. I didn´t notce this behavior while flying the F1CE.

When flying the Mirage F1EE the radar mode LEDs to indicate the current operating mode next to the radar display do not work except when you select V1 mode. All other (implemented) radar mode indications next to the radar display are not illuminated. Concerning the range indication only the 60nm and the 7nm range LEDs do actually work. The 15nm and 35nm indication are dead. This is only for the Mirage F1EE. The indications do work in the F1CE, though. Tested under MT and ST. 100% reproducable on my system. short YT vid to showcase my findings: https://youtu.be/tCagSAhFzv0 Mirage F1EE Cyrano Mode and Range bug.trk

Can we please get tracerless gun ammo for the DEFA gun like in the M2K? Would be quite helpful in PvP if the enemy does not see the tracers flying all around his jet in case you miss a few shots, right? Thanks.