4 hours ago, Bert Pieke said:

@ryanbatcTry:

(A:CIRCUIT ON:20,bool) (A:GPS DRIVES NAV1,bool) and if{
(A:HSI CDI NEEDLE, Number) /-/ 127 + }
els{ (A:CIRCUIT ON:20,bool) (A:NAV HAS NAV:1,bool) and if{
           (A:NAV CDI:1, number) /-/ 127 + }
           els{ 127 }  }

I need to test with the new WT GNS to see if this changes anything.

18 minutes ago, ryanbatc said:

I need to test with the new WT GNS to see if this changes anything.

Please do and report back.

13 minutes ago, Bert Pieke said:

Please do and report back.

We have bigger problems...the CDI button doesn't even work now hehe.

Performance seems waaaaay of in this version - with physical collective at 100% I'm barely hitting 84% torque and 110kt in level flight.

 

With that collective setting I should be ripping the rotors apart at the same time as experiencing retreating blade stall

13 hours ago, sd_flyer said:

Do you guys know how to bind force trim?

A force-trim button would be nice, but I find the Increase/Decrease Rotor Longitudinal/Lateral Trim to be equally, if not more effective

Now, if only Asobo will give us the basic one-click fly-by and tower views

Edited November 12, 20223 yr by rooitou

Someone is already on the torque issues hehe

https://flightsim.to/file/43693/bell-407-improvement-mod

I believe that the panel brightness knob needs to be fixed as well. It is either off or then on and too bright. There is no gradual brightness adjustment.

There's a dedicated feedback subforum for the 40th on the official forums

https://forums.flightsimulator.com/c/community/40th-anniversary-edition-feedback/356

I wonder why the key binds to increase and decrease heading bug don't work with this aircraft.