Vibora

This is known and fixed. Txs.

It is known and fixed.

Yes, will do a few.

We are looking at it. Thanks for the report.

The trim doesn't move the stick in the C-101, as you can see in the cockpit 3D model. Thank you! S!

Yes, FFB is implemented in a realistic way, of course.

We'll work on it. Though it will take some time as we are busy with other issues.

The pilot will faint after a certain time, due to oxygen starvation, if both cabin press and oxygen press are too low. This happens also in multicrew.

Maybe you were using a low atmospheric temperature and/or high pressure? That would affect engine performance, and aircraft performance in general. EDIT: I see you wrote you were using default weather. Then I don't know what can be the reason for that difference.

You'll get quite a large amount of additional liveries, of most countries, if not all, that use or used the F1.

Fixed. Expect it in next update.

I still think there could be something faulty with your peripherals or your axes settings in the C-101. Did you try unplugging your peripherals, using keyboard for throttle and using another joystick or another axis as throttle? Even though you deleted inputs in saved games, when entering DCS it assigns default axes, maybe some of them is faulty or interfering with your throttle assignment, delete them all before entering the mission, and make some tests assigning specific axes to throttle until you determine the faulty one, if there's any. In any case, we have made some changes in the code so that compressor stall doesn't happen at mission start, if switches or axes are not in the correct position yet.

Did you delete or back up your inputs saved games?

It seems your airplane engine compressor stalls because you move the throttle instantly to full power. How do you manage to do that? Lookt like a potentiometer issue in your peripheral. Also, the throttle and brakes are at 100% at mission start, that is not normal either, at least for brakes.

Take into account that you can also set failures using triggers. The problem is that they are not set at a certain time, but within a time.

You can set the aircraft as player in the ME instead of client and still open it in multiplayer, and enter both front and rear cockpits in multicrew. The failures will appear on both cockpits but not synchronized, so timimng will be different on both seats. We will investigate if failures synchronization is possible and how should be implemented.

You said you can advance throttle to 51%, so I excluded the red warnings inputs issue. A better explanation on your side could help. It could be that you have another peripheral interfering with your throttle.

I don't know. Unable to reproduce. Would need a trk. Can you record one and pass it?

Thanks for your feedback.

Delete mouse folder in Input\C-101CC and Input\C-101EB. That should fix it. Please let me know the results.

It is a pull and release knob. Fixed C-101EB input. Now key or joystick binding will pull the knob when pressing the corresponding key or button. Not sure if it will be included in next update. Thanks for your feedback.

I can only reproduce that in Open Beta (2.7.0.5659), but not in internal testing versions. That means it should be OK in next update.

Sure.

Added. Thank you for your feedback and cooperation.

We'll look at it.