I checked it out today , and yes that panel has a customized autopilot that's why you can't get ISG's LNAV or Vnav to work.
ISG was working fine, but everytime ISG submits a LNAV heading input this autopilot detects that it doesn't match what it has and it switches it back automatically. It does not allow the heading and altitudes to be changed from anyplace but its MCP panel windows.
The ResetApHdg=1 .cfg option does not work here either as all that happens is ISG sets it, and this autopilot sets it back and they effectively fight for conrol resulting in no heading change.
The only way you can use ISG1 LNAV or VNAV is this particular panel is to remove the autopilot gauge(s) and replace them with one that supports default autopilot functionality.
I saw Randy doing it on FlightView, I tried it and it worked.
You'd need to remove the AP_System gauge
gauge06=Ml_ARJv40!AP_System, 1025,75,10,10....
and replace the main autopilot MCP with another.
Example in mine I replaced it with the 737's MCP gauge in FS9.
//gauge35=Ml_ARJv40!Autopilot, 574,290,450,78
gauge35=737-400!Autopilot, 574,290,450,78
See the screenshot below of mine after I made the changes.
Can't tell you what systems were affected by the change, didn't check it out further after I got ISG's LNAV working.
Regards.
Ernie.
Attachments: |

mlb146.jpg [ 177.86 KiB | Viewed 21718 times ]
|
|