fausete

The issue has been fixed.

Hi, @Kobal, The problem you describe with the pedal movement has to do with the antislip and is completely unrelated with what this thread originally described, which had to do with the yaw damper frequency behaviour. What you describe is due to the aircraft temporarily not detecting weight on wheels, and thus activating the antislip during the take-off roll. I've just fixed it so you'll have it available in the next OB release. And obviously, immediately after take off, the aircraft will naturally tend to align itself with the wind (and the antislip will help), so you'll still notice it reacting to the wind and you'll see the pedals moving once the wheels leave the runway.

Hello, have you tried running a repair of your install?

Hi @CrazyGman, Confirmed there's a problem. The bug is not with missile cool-down, as otherwise you wouldn't get the white triangles indicating the missile is ready to fire. We'll investigate.

Not a guide but for this case, search Mirage-F1EE.lua in CoreMods and paste add_ECM_pod(Pylons_EE, id_PHIMAT, 2, 6) in line 8.

Hi, EM -> radar IR -> infrared

Hi @Snacko 2-1, We prefer to provide something that works to avoid any negative impressions. If you fly in SP, editing the luas will allow you to fly with the PHIMAT too.

We've posted a little explanation here:

Hi @jaguara5, No, no changes made in the FM apart from the yaw damper and the turbulence behaviour. I've quickly tested the turn rates and they coincide with the data we have and the behaviour shown in the last adjustment early this year. If you feel the behaviour different, it might come down to the changes to the yaw damper (obviously depending on the maneuvers you were testing).

Hello, We are sorry for the inconvenience, but the module is still in intensive development, and we have had to manipulate command ranges, to keep things consistent internally. In particular, the last massive change was necessary to prepare for the F1 BE. And of course, later on, things will settle down.

Hi, glad this helped. just to clarify: M means Marche (on in French) A means Arret (off/stopped in French) And then you have Manuel/Auto, which mean the same as in English but unfortunately share the same initials with Marche/Arret, potentially causing much confusion. In general, when you read M/A in a switch in this aircraft, it means on/off. Cheers

Hi guys, This should be solved in the next update, as we've transfered the BR-250 and BR-500 to ED.

Hi, it's been fixed, will be available to the public very soon.

Hi @jojo, If you're noticing the commands diverging from the target value, then yes it's that bug. If on the contrary, the controls are fighting the asymmetry, then it's just lack of authority (which we will review anyway). Another test you can do is to engage the AP with more than 10° of bank and see what happens, as the bug only affected the heading hold mode.

Hi @jojo, Asymmetrical payloads will undergo another round of testing by SMEs. Regarding your second message, this problem has been fixed internally.

Hello @TLTeo, This is known, the radar is still heavily WIP, and this will be fixed when the radar is completed. Thanks for taking the time to create a clear and straightforward report with a TRK tho.

We've adjusted the yaw damper and now only the most extreme levels of turbulence (selected in ME) generate some jittering in it.

Yes, the 3D model is done and we are seeing how to implement the pod itself.

Hi, I've been testing it and it seems like our fix for the multiplayer issue has also fixed this.

Hello. The real F1 was quite sensitive to this kind of oscillatory behaviour induced by the pilot on the pedals on take off, with future pilots being trained on how to avoid it. Nevertheless we will review the intensity at some point down the line. If you find it too uncomfortable, using curves will probably help.

Right now, the cannon pods and more variety of Spanish made bombs.

Hi @Bestandskraft, good catch. Some sort of argument mixup problem happened at some point in the past months. We realised some weeks ago and it's fixed internally, so it will be available to you in the next OB.

They are planned but other payloads have priority right now.

No problem. I didn't even think that might be why you were seeing what you were seeing. Glad you found out!

De nada!