The biggest issue for me at the moment is with the Spitfire IIa. With realism to full (accept two handed operation) the disparity between control positions and the aircraft response is almost a show stopper. I just had a test flight around for 40 minutes to nail down how to reproduce but turned out it happens in most flight conditions.
I believe this is all related to the same cause. The aircraft instruments and performance loses synch with control inputs from the user. This is not due to low FPS, I was just flying around at between 50-74 FPS.
The faults can be measured as followed:
Aircraft is in sustained straight and level flight, Artificial Horizon shows bank angle in either direction of 30 degrees+, Turn coordinator shows no turn.
Throttle when at around 60% for a sustained period then starts to stop responding to throttle control changes. The icon overlay can show the change but with no response from the aircraft from either gradual or sudden increase/decrease. You have to push it all the way forward or all the way back to seemingly update the aircraft.
Rudder trim is similar to throttle.. small inputs have no effect. Have to introduce massive input to get it to register with the aircraft causing over-correction.
Intermittent failure to register commands for things like Magnetos or Fuel cock. One moment the key-press works next it doesn't.
This is a bit of a show stopper really and CEM is largely unusable for sustained periods of time as a result of the failure of the aircraft to recognize changes to control inputs or key presses.
|