Kinkkujuustovoileipä

We have made the various issues with the Mistrals very clear to ED some time ago.

It is a bug, will be looked into.

Thanks, will take a look.

Will look into it and see what we can do. It should be noted that _all_ aircraft in DCS use wheels (including the Huey), there is no actual skid physics simulation in DCS. So we are limited in some areas.

I see you worked it out, but I will clarify that it is deliberate behaviour and it is left for the user to decide whether they want the sight visible or not.

1) The hover trim state is cyclic aft and left. Position the cyclic in the correct place before lifting off. 2) The 'violent roll' is the effect of flapback/blowback and the transition into/out of 'clean' air. The momentary dissymmetry of lift across the forward->rear of the rotor disc is translated into a roll due to gyroscopic precession. 3) Don't turn off the starter motor then. It's probably a bug, and will get fixed. 4) It's chaotic only because you don't understand it, and seem to refuse to adapt to the handling characteristics of a small, light helicopter.

This is currently broken and we're working on a fix.

@grim_reaper68 can you please provide a bit more detailed explanation? I am struggling to understand the issue. I myself use a Warthog, so I should be able to replicate this if you lay out the steps for me.

Not necessary. This is fixed by the engine and FM updates coming in the next patch. @Targanon feel free to check in CB if you wish.

This has already been addressed internally for some time and the fix will be out in the next OB update. @Flappie feel free to test in CB for this behaviour as it will help verify the fix.

Because it's a bug. They happen. There was a lot of testing done on the Gazelle before it released, and yet still, bugs happen. That doesn't entitle you to act like an arsehole. If you don't like it, don't fly it and wait for the fixes to come out.

Sounds like you are either in some really hot and high altitude, or you have a problem with your inputs.

I have said multiple times that we are working on this.

There is no autopilot, only autohover and heading-hold/slave to sight modes. Both of which are buggy and being fixed. Further autopilot modes may come later. The fighting behaviour is likely the SAS, which may be detuned in future update. The pedal issue is likely due to the amount of power you are putting in - more collective power means you need more pedal to fight the torque. In an OGE hover with HOT3s loaded, you are very heavy, thus lots of power, thus lots of torque. This is partly accurate, but the power issue is increased due to a bug that will be fixed in the next update. So, these issues should become somewhat easier soon, but it won't hold your hand

Hi all, unfortunately a bug was introduced in the last update that broke the Mistral. This has been resolved internally and will be pushed in the next OB update. I am sorry this happened, unfortunately the nature of the last patch release meant we were not able to test our pushed changes effectively. We are changing our internal process to be more thorough and hopefully prevent issues like this happening again.

You can just click on the area where the base of the sight is to make it reappear.

Resolved, was a separate issue regarding fuel mass. Thanks for the help, it will fix some other issues too.

Not something we have any control over.

Engine/governor needs some tuning, I suspect NG is too low when power requirement is low.

There is an issue when firing both; the overlapping sounds cause a slightly strange effect. Otherwise they are accurate.

Do not use the autohover functions, they are buggy and are in process of being redone. Autopilot lights will be yellow (top) when out of conditions, green (bottom) when in condition and active. Jerky torque effect is caused by you moving the collective too rapidly and surging the engine. Maintain smooth collective movements. Remember that pedal input also affects torque, and collective input affects yaw.

Try wiping your lenses. No really, I'm not sure what you're experiencing. There is no visual degradation in the periscope.

Autohover is known to have issues, as was mentioned in the changelog. It will be fixed as soon as possible.

Fixed, will be pushed in next Gazelle update.

Fixed for next update.