It's clear to everyone that the elevator sensitivity of the Camel is quite high. I have difficulty flying it, because I over-react (pilot induced error) and it's pretty sure this is because of the deadzone in my joystick.
I'm currently running RoF on Win XP, but I am in the process of moving to Win7. Yesterday I flew in RoF on Win7 and besides a noticable improvement in FPS (better graphics driver? directx11? 64bit OS?) I was able to control the Camel! It seems there was less deadzone in the joystick.

Is this a feature of Win7? I remember there used to be a "fixed" deadzone in the windows game controller. I am using a standard game controller, no special drivers.

I concur, and it makes the Camel seemingly almost impossible to land, at least to me. In however way I touch the grass, it is either too hard so I groundloop, or too soft and I bounce and then a wing drops. I know flying a Camel was difficult, but is this realistic, especially given the fact that we have no motion cues in a sim, only limited field of view, and much shorter (joy)sticks than they had back then? Also, the difference between the angle of attack at which you don't loose any altitude (not even wih blipping) and the AoA at which a wing drops seems vry small.

I agree, especially when it comes to landing. It seems more difficult than it should. Last night, I couldn't get the Camel down for the life of me. Tried several times. Exactly as you stickshaker, several loops and bounces, no matter how low and slow I came in. I tried to touch with absolutely zero sideslip and still wasn't getting good results. I then took the Spad up for a quick circuit and landing. What a breeze in comparison! Just a slow decent to touch down with no drama.

Looks like patch 1.09 may take care of this JS issue with away to adjust input curves.

Read their update over on the RoF forum under NEWS; WIP 09 .

WF2, you’ve flown this kind of aircraft for real, but will scalable joystick sensitivities solve the problem? My Camel groundloops or topples over so quickly that I don’t have time to react, whatever the sensitivities would be. Could this not be a flight model issue?