2 minutes ago, ryanbatc said:

Be sure you're only using the analogue selector below the HSI to change altitude though.  ALT button the AP is only to HOLD present ALT.  If you want to capture you set the altitude, press the little white circle to ARM the ALTS, then use a pitch mode (like IAS or VS) to do it.

That doesn't seem to work now with the latest beta release.  I just tried a flight, set the altitude selector and clicked arm and flew with the GNS 530 version and it didn't capture the altitude.  But when I clicked the ARM button and the ALT button on the autopilot it did capture the altitude.  I'll check again and see how it works with the autopilot in the PMS50 variation.

2 minutes ago, jfwharton said:

I checked the tablet click spot for every livery, every variation and the tablet closed when I clicked on the camera click spot on each.  I also noticed that when the tablet is open clicking on the window click spot for the tablet does not do anything.  It only works to bring up the tablet.

I found it. I'm stupid.  

1 minute ago, jfwharton said:

That doesn't seem to work now with the latest beta release.  I just tried a flight, set the altitude selector and clicked arm and flew with the GNS 530 version and it didn't capture the altitude.  But when I clicked the ARM button and the ALT button on the autopilot it did capture the altitude.  I'll check again and see how it works with the autopilot in the PMS50 variation.

With the PMS variation, you set the altitude in the analog Alt Alert area, and arm it. Then in the GPS, you use either VS or IAS to climb towards it. It will then capture the altitude. I just checked that and it works (and for the altimeter altitude too!)

3 minutes ago, jfwharton said:

That doesn't seem to work now with the latest beta release.  I just tried a flight, set the altitude selector and clicked arm and flew with the GNS 530 version and it didn't capture the altitude.  But when I clicked the ARM button and the ALT button on the autopilot it did capture the altitude.  I'll check again and see how it works with the autopilot in the PMS50 variation.

The GNS AP is different slightly though.

For that one, set the altitude selector as usual.  Press ARM button.  Press ALT on the AP, then use the thumbwheel on the lower center console to change pitch up or down.  It should capture then.

2 minutes ago, Grothauser said:

With the PMS variation, you set the altitude in the analog Alt Alert area, and arm it. Then in the GPS, you use either VS or IAS to climb towards it. It will then capture the altitude. I just checked that and it works (and for the altimeter altitude too!)

OK, so the ALT button works differently on the PMS variation than it does on the GNS variation.

I cannot seem to get the PMS750 to capture a VOR. The PMS GTN shows "VLOC" the Autopilot shows "VOR" and the needle on the HSI is definitely moving as expected. However, it just straight through the radial with the needle offset moving right through the middle  to the other side without the aircraft turning at all. Straight ahead through it.

1 minute ago, Grothauser said:

I cannot seem to get the PMS750 to capture a VOR. The PMS GTN shows "VLOC" the Autopilot shows "VOR" and the needle on the HSI is definitely moving as expected. However, it just straight through the radial with the needle offset moving right through the middle  to the other side without the aircraft turning at all. Straight ahead through it.

What is your intercept angle?

5 minutes ago, jfwharton said:

OK, so the ALT button works differently on the PMS variation than it does on the GNS variation.

Yeah. In the manual provided by Flysimware there is a link to the real world autopilot manual as well and it gives a bunch of info on how it works. It is definitely different than the GNS.

A couple of bugs for the new v1.2.0 release:

1) Prop lever still has no effect on the RPM when on the ground. That is, trying to test the prop governors during engine run-up results in no RPM drop when pulling the prop levers back.

2) Fuel computer now counts down, but the fuel flow, while better, still appears to be too high. I tried 0.75 for the fuel_flow_scalar and that was just a bit low so I'm thinking somewhere around 0.85 is probably going to be dead on. I think someone else reported that 0.85 was pretty accurate.

Edited March 30, 20224 yr by geoffda

5 minutes ago, ryanbatc said:

What is your intercept angle?

Approximately 30 degrees. Though it's worth noting that I would expect the NAV mode to turn to the 30 degrees when within a close range of the radial, but it doesn't. I set the 30 degrees in HDG mode, switched to VOR and it just cruised right through. If I can ever figure out how to embed an image, I took a pic of my panel just before I sailed through the radial

 

In order to capture a VOR you need to use HDG to set up an intercept, then select NAV on the autopilot and of course VLOC on the GTN.  When you start to intercept the VOR course you need to then select APP on the autopilot in order for it to track the course.  The autopilot will then change over to VPP mode.  I don't know if that's the way it is supposed to work.  It should capture using VLOC and NAV but it doesn't.

Edited March 30, 20224 yr by jfwharton

Is the default fuel 10% or so?   Personally, I'd gas it up.  

4 minutes ago, jfwharton said:

In order to capture a VOR you need to use HDG to set up an intercept, then select NAV on the autopilot and of course VLOC on the GTN.  When you start to intercept the VOR course you need to then select APP on the autopilot in order for it to track the course.  The autopilot will then change over to VPP mode.  I don't know if that's the way it is supposed to work.  It should capture using VLOC and NAV but it doesn't.

I'll give the APP button a try. That should NOT be part of following a VOR that isn't part of an approach procedure. Just for VOR to VOR navigation, APP shouldn't be involved.

 

1 minute ago, Grothauser said:

I'll give the APP button a try. That should NOT be part of following a VOR that isn't part of an approach procedure. Just for VOR to VOR navigation, APP shouldn't be involved.

 

I totally agree.  NAV should work but it doesn't so hopefully they will fix it.

OK - Can confirm that works with the PMS GTN. It shouldn't work that way, but it does.

Also: when crossing the VOR station in the dead zone cone, it keeps trying to acquire and picks it up again on the other side. It SHOULD revert to ROL mode as soon as the signal is lost crossing over top.

Edited March 30, 20224 yr by Grothauser