14 minutes ago, btacon said:

but…fall behind in the slightest way and all the old flaws come roaring back,

Wasn't it the type rated pilots who said the the real thing also can be very unreliable and that you have to be on your toes with it?

So you'll never know whether a failed localizer capture is not a perfect simulation of the real thing.

16 hours ago, Farlis said:

If you have it on Aerosoft one you just have to go to the Aircraft and pick the Manuals tab where all documents are listed. There is a "Third Party Livery update guide"

There we go! I found it. some convert, some are too old, but thank you, this helps quite a bit.

3 hours ago, Farlis said:

Wasn't it the type rated pilots who said the the real thing also can be very unreliable and that you have to be on your toes with it?

So you'll never know whether a failed localizer capture is not a perfect simulation of the real thing.

I hope you guys refer to autopilot, because if radio navigation equipment fail to capture localized it definitely an issue !

I have not been able to try the update yet, as I own it on the Marketplace. But people are already reporting bugs that have been around for 3-4 years, and are still not fixed after an update 2 years in the making. As someone else mentioned, it does not inspire confidence.

I will give it a shot once it is in the Marketplace.

Anyone having issues with throttles? I'm not sure if it's a binding or an airplane issue. When I move the throttles, the virtual cockpit throttles move fine and correspond to my physical throttles fine. But N1 is all over the place. Toga is usually finem but if I move the throttles small, I can massive fluctuations in N1. Tiny movements will often result in thrust going to idle...then ramping back up to near full thrust. It's bizarre. I don't have any binding conflicts that I know of. It's frustrating.

I don't have issues with the throttles.   Obvious question but did you complete the calibration using the EFB?  Did you check for any conflicts?  Make sure you don't have other bindings in your throttle like mixture, etc...  

I had 2 issues on my latest flight.  One, the ground handling during takeoff and landing was really bad.  The worst I’ve seen actually.  Second, when I changed my approach runway it messed up both the TOD calculation and started turning the plane back to an earlier waypoint.  I was between two enroute waypoints so a runway approach change shouldn’t have had any impact on the path the autopilot was following.  Other than those two things it was mostly ok.  

VOR 2 CRS reading changing on the display text but not rotating the VOR 2 compass. 

Can't justify spending my time with this when the Fokker F-28 is so good... and works.

5 hours ago, BMIBaby said:

VOR 2 CRS reading changing on the display text but not rotating the VOR 2 compass. 

Can't justify spending my time with this when the Fokker F-28 is so good... and works.

Was the nav selector also set to VOR2? Cause it’s usually slaved to the FMS

6 minutes ago, Lucky38i said:

Was the nav selector also set to VOR2? Cause it’s usually slaved to the FMS

Yes, with the VOR2 selected the yellow CRS2 text altered correctly, yet the yellow VOR2 compass didn't spin, leaving the VOR needle always deflected to one side. Not what you want during a high workload STAR and VORDME approach with surrounding high terrain! This wasn't a problem on ASCRJ V1. 

20 minutes ago, BMIBaby said:

Yes, with the VOR2 selected the yellow CRS2 text altered correctly, yet the yellow VOR2 compass didn't spin, leaving the VOR needle always deflected to one side. Not what you want during a high workload STAR and VORDME approach with surrounding high terrain! This wasn't a problem on ASCRJ V1. 

Yeah that does sound annoying sorry to hear.

Anyone else getting a “on again, off again” TOD marker?  IOW 3 of 5 of my flights have been without a TOD, but it was displayed in the VNAV data displayed above the route. It was just hit or miss on the lubber line.  
 

In all flights the VNAV TOD was honored and descent began without intervention.  Anyone else?

-B

Edited April 4, 20251 yr by btacon

2 hours ago, BMIBaby said:

Yes, with the VOR2 selected the yellow CRS2 text altered correctly, yet the yellow VOR2 compass didn't spin, leaving the VOR needle always deflected to one side. Not what you want during a high workload STAR and VORDME approach with surrounding high terrain! This wasn't a problem on ASCRJ V1. 

Just tried it on mine and having no issue at all. Maybe try a reinstall? 

1 hour ago, btacon said:

Anyone else getting a “on again, off again” TOD marker?  IOW 3 of 5 of my flights have been without a TOD, but it was displayed in the VNAV data displayed above the route. It was just hit or miss on the lubber line.  Anyone else?

-B

Yeah B I’ve been getting this too. I’ve only done four flights, one being a quick turn in KTUS but I’ve definitely seen this.  My VNAV also worked as expected 

Kevin 

Edited April 4, 20251 yr by KevinS137

On 4/1/2025 at 8:13 AM, Alistair Logie said:

Same. I actually bought the 500/700 when it was released and then bought the 900/1000 separately when it came out. I emailed PCAviator, so I’ll post back here when I get a response. 

Unfortunately I’ve not received any response from PCAviator. Not sure if anyone else has had better luck.