F1EE radar mode and range indication bug

[Tango3B]

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

[Bremspropeller]

Other lights aren't working as well.

The Centerline External Tank empty light won't come on in the F1EE. Haven't tested the underwing-tanks or the CE yet.

Pressing the TEST button (with a full centerline bag) gives me this:

The auto-wind feature on the fuel-dial is on.

Edited April 13, 2023 by Bremspropeller

[Tango3B]

31 minutes ago, Bremspropeller said:

Other lights aren't working as well.

The Centerline External Tank empty light won't come on in the F1EE. Haven't tested the underwing-tanks or the CE yet.

Pressing the TEST button (with a full centerline bag) gives me this:

The auto-wind feature on the fuel-dial is on.

 

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.

[Iron Sights]

Both noted when flying post patch today. Tried changing my range and the lights not working. Same when I ran a mission with a center tank.

[TheGopnikTsar]

The Barax ECM panel is broken the animation for the switch changing positions is no longer there and the indicator lights are also nonfunctional FAIL is constantly illuminated and the Forward and Aft lights are constantly illuminated and emit light does not turn on even after the 2-minute wait time required for ECM pod 

[Tango3B]

21 hours ago, TheGopnikTsar said:

The Barax ECM panel is broken the animation for the switch changing positions is no longer there and the indicator lights are also nonfunctional FAIL is constantly illuminated and the Forward and Aft lights are constantly illuminated and emit light does not turn on even after the 2-minute wait time required for ECM pod 

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.

 

 

[fausete]

Hi guys, all of these have been fixed internally, thanks for reporting.

[Tango3B]

On 4/19/2023 at 7:39 PM, fausete said:

Hi guys, all of these have been fixed internally, thanks for reporting.

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…

[fausete]

No problem, thanks for the compliments. Just to be clear, the PHIMAT is not done. I meant the fix of all the bugs reported here.

[Tango3B]

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!  

[RockMyRoot]

Came here to report the same issue, happy to find out that the broblem is already reported and corrected

Thanks Tango3B, thanks Fausete