Pat01

No, it was "broken" in the previous update, it has been repared now.

Wow, Sorry I'll correct that from now :)

Hi, Yes it is multicrew, only the copilot can access the gunner position. A bit nauseous with oculus I guess depending on your fellow pilot :)

Hi Gents First post edited. Thanks.

It's just because datas cannot be updated both ways, i.e both pilots cannot use the same switches. I guess ED is already aware of that, they'll change it when they think it's needed.

Hi gents, With the coming update, copilot will use TV,Hot missiles plus all radios.

Hi Gents, Sounds like the camera is off ... Coming in next update, multicrew sync has been reworked, the TV should display the same for pilot and copilot now.

This one is technically impossible to fullfil.

Hi Gents, Just to let you know, there's no controls curvature or else coded in the gazelle.

I should add the following I'm currently using the warthog throttle slider (the grey one named INCR) and it works for me. Some other people who are using the same had to use a curve to make it work. I'd say it depends on the slider itself.

Hi, Weapons adjustements mainly means rockets range and effect changed, at the moment. As soon as we have enough datas and figure how to apply them in DCS the mistral missile will be corrected too. Thanks.

@Haukka81 Can you elaborate a bit more ? Inertia has already been reworked to fit real gazelle pilot feedback since the last update, not sure what you mean about gravity. Speaking about 2.5.0.

Hi, MultiCrew has been reworked, it will show in the next update. Thanks for your patience.

sunski34 Gyro and AP logic has been reworked here, you may experience something different with the next update. Thanks for your patience.

Hi, If you notice no changing, switching the Gyro and the Autopilot Off, it means you definitely have Something wrong on your side. Autopilot off, means no more trimming system, coordinated turn, auto-hover, speed/alt modes, slaved mode. GYRO off, means no coordinated turn, auto-hover, speed/alt modes, slaved mode. Only trimming system can be used without gyro, but needs Autopilot.

Hi Gents, All multicrew issues have been reworked, still some tests to run, and then the fixes will show in the next update. Thanks for your patience.

Hi, Difference between the two modes is quite noticable here. When you swap from normal to easy, it's taken in count right now. When you swap from easy to normal, you have to restart the game for it to be taken in count. Hope it helps.

Hi Gents, Due to latency issues in multiplayer, we had to remove the ability for the copilot to pilot the helicopter. We can imagine how it would be great to have such a feature, but it won't be possible right now. We hope it will allow us to improve the rest of synchronization in multicrew, camera, etc ... Aside weapons, the copilot will also have navigation and radios to deal with like in RL. As we prepare the gazelle to go out of beta state, we would like to give people the best stable experience flying the gazelle. Still some multicrew tests are left to do before we can plan the out of beta release though. Thanks.

Hi Gents, Back to the light subject ... Lights are back in all gazelle cockpits and no more flickering. Finally it took a snap and a half ... Thanks. Of course it will show on next update.

I'm currently fixing the lights, 100+ light related things in a cockpit, 4 cockpits to do, definitely won't be done in a snap ...

Dear DanielNL For us to be able to fix all lights issues in the cockpit, we have to wait for ED to fix 2.5.0 lights. Be sure we are looking forward to have this fixed, but we cannot go faster than the music. Thanks for your understanding.

Hi Gents, I'm not sure I phrased correctly what I thought, regarding your reactions. I try to keep it simple : We are not going to give up or remove the FFB. What I meant is I'm going to fix what already exists about FFB and then consider it done. Still an external view visual issue to fix. All fixes about FFB will show in the next update. Thanks.

Second issue, controls position : diamond or 3d stick in cockpit and 3d stick in external view All these parts have been fixed and work correctly now for both FFB and non-FFB sticks The external rotor movement is ok with the non-FFB stick, but for some reason is not correct with the FFB stick. As soon as one releases the magnetic brake button the rotor disk comes back to "level" instead of keeping the trimmed position. It's only a visual issue, the trim position is taken in count for dynamics. So still this issue to look at on my side. Broken behavior at ground has been corrected too, now you'll need to have around 45% torque before you can roll or pitch the helicopter (was the case before). Thanks for your reports. PS : These fixes will show in a next update.

Ok, one issue at a time First the china hat trim. The china hat trim covers only +-10% of the total path in each direction, approx a diamond size Here's what I experienced with my MS FFB2 : I assigned 2 buttons at pitch up and pitch down trim at a separated device (warthog throttle) so my hand doesn't move the stick at the same time I press the buttons. pressing the buttons I can see the stick moving erratically forward and backward, and my stick is so old that it never goes to the exact position, I have to move it with the hand and release for it to reach the planned position. If I do the same with the china hat I don't see the stick moving in some case, I have to move it hard and release to have it at the correct position. Conclusion, The china hat trims works, but my stick is not able to render the changes as it should. Just what I experienced, hope you guys have a better FFB stick than me.

Hi Gents, After several days spent to check users reports of ForceFeedBack issues we came to the following conclusion. At start the Gazelle was not planned to work with ForceFeedBack devices. At some point we decided to add some code to allow the use of ForceFeedBack in a basic way, this is the current state. Making ForceFeedBack to work properly with the Gazelle would need us to rewrite a big part of the module which would take a lot of time. We decided not to go this way and keep the ForceFeedBack use at its basic state so ForceFeedBack users can still fly the module even with ForceFeedBack uncomplete features. Thanks for your understanding.