lordauriel

that doesnt work, due to the completely custom fuel system little navmap can't read the values or did I miss something since I last attempted to do it

I know what OP means and I think this is mainly an effect of the challenger having an atrocious "feel" to it at high AOA. It just isn't pleasant to fly at close to vref so my trick is to mostly fly ILS by raw data in the last 4nmi or so, because the FD encourages use of pitch to control vertical speed which is a BAD idea pitch for speed, throttle for v/s, and let the FD zip around, it's ok, don't chase PS Try using command bars instead of V flight director that way you can more or less focus on lateral guidance and let the pitch command slip

I hope you realize that there IS wingflex, no matter how much you deny it. it is unfair to compare trying to move the wing by hand, to what the wing does when the airplane is airbore with high wing loading, in a scenario where the pilot pulls up (rotation, upset recovery etc) or turbulence. Implementing wingflex in PlaneMaker is simple and takes mere minutes. A small value that makes the wingtips flex a bit in moderate turbulence or high positive G is enough, and would add a lot. Here a CL650 video showing some wingflex during normal approach in light chop. It's not much, but clearly visible. Yes it's a stiff wing. BUt it does flex.

Hi The rate at which most knobs change values when manipulated with the mouse wheel, seems very slow. Prime example is the DATA knob used to dial in minimums (radar alt). It increases in +1ft steps and takes a silly amount of time and scrolling to get to 200ft, let alone values above 1000ft. But in general it would help to have the following behavior for all kobs: Hover mouse cursor over Knob, arrow symbol appears. Hold down LMB, which leads to increasing values by twice (or even te times) their "normal" rate. Other devs have done this for their addons, or similar solutions, and it's just fine. Am I missing something here or why do I seem to be the only one complaining about this? Same with setting altitudes for the AP, I had to do a workaround with the keyboard. The "mouse wheel acceleration" I keep hearing about, doe not work for me. one wheel "click" is always a fixed value (1ft for DH, 10ft for DA etc etc)