Robertfm wrote in Tue Nov 12, 2019 11:22 pm: The button referred to earlier on the 'Virtual Yoke' only de-activates the AP. Looking at it simply from an 'electrical standpoint' an on/off switch is simply that.
<key n="100">
<name>d</name>
<desc>AP (DIS-)ENGAGE</desc>
<repeatable>false</repeatable>
<binding>
<command>nasal</command>
<script>
if( getprop("an24/AP-28l1/internal/engaged" ) == 0.0 ){
instruments.engage_ap();
}
else {
setprop("an24/AP-28l1/internal/kv", 0.0 );
setprop("an24/AP-28l1/internal/horizon-mode", 0.0 );
setprop("an24/AP-28l1/internal/engaged", 0.0 );
}
</script>
</binding>
</key>
So why can FSX/Xplane do it.
Surely if FG want to attract a wider audience who like me simply want to fly without having to have a degree in Computer programming a little less realism would maybe a good thing.
I think you have summed up why people like Saitek/Logitech and other producers of flight sim kit never include FG coding.
Robertfm wrote in Wed Nov 13, 2019 11:55 am:What I mean is the devices are plug and play in FSX, Xplane etc, not FG. The AP panel and switch panel that Saitek make has been well documented as not working in FG. I have seen other companies products that are not made for FG, but for the other flight sims.
Robertfm wrote in Wed Nov 13, 2019 11:55 am:What I mean is the devices are plug and play in FSX, Xplane etc, not FG.
D-ECHO wrote:Could we please split the part about joystick bindings off?
I assume if you change the plane name it will work on any plane that has the KAP140 & Centurion111
Users browsing this forum: No registered users and 3 guests