So, the problem if you tried to program the device in FSUIPC would be that both FSUIPC and GFDevFSX. However, I will relay this remark to the developers. Pete Dowson said: Unfortunately, I note that, in FSX at least, the 'GFConfig' program GoFlight supplies for configuring their devices does not actually allow the trim wheel (s) on the LGT to be freed from GF control. See the cutoffs lever as a simple rocker switch with as very long handle. Therefore, there is a threshold in the axis value above wich the cutoff is considered as on and under wich the cuttof is considered as off. That is how these are linked to the axis function in MSFS. I think that would be more intuitive for most people? My suggestion would be 1:1 matching the animation of the levers in the cockpit with the HW controls, and just nothing happens until the last 10% range or whenever fuel is currently cutoff. I was trying to troubleshoot this for 30 minutes in settings last night, until I ran across the thread. The reason is simple the Warthog has 2 throttles. Currently I only use FSUIPC for my throttles. Some times deleting the fsuipc.ini and starting over can fix a lot of controller related issues. While very powerful it can cause lots of issues. It's fine that the behavior is on/off - but it looks like a bug that the lever in game doesn't move 1:1 with your physical mixture/power levers on the hardware. A lot of you use this to set and configure your controllers. But the response in the sim will be 50 times less squirrely and less over the top at controller extremes than if you were using MSFS instead of FSUIPC to manage controller movements. I think my issue here is the animation of the levers in the cockpit - ie you move the levers on your throttle and nothing happens until you hit the bottom 10% of range - then the levers abruptly move to off. You will now see a response in MSFS flying with no sensitivity curve, and no effectiveness set (as of yet).
0 kommentar(er)
