with 2.0 I am also still having the FPS drops, will again try the avidyne-hack, it worked before!
2 Likes
i am also suffering from bad fps drops 
2 Likes
Since the update I can no longer select NAV, and I’m not sure why. I haven’t changed the way I’m doing anything. GPS is selected on the Garmins and EFIS, and the correct leg is activated. Is there something obvious I’m missing?
NAV working fine for me here but I’m loading the flight plan int he planning window before starting the flight, not in the aircraft itself.
working for me but one thing i did note was that when i was in heading mode and changed to nav, nav didnt work and it stayed in heading then running mouse over the ap panel it said “Nav armed” i disconnected nav then heading then re engaged nav and it worked fine
1 Like
I have a similar issue on the Black Square King Air. I have to set the nav source from GPS ( default ) to VLOC and then back to GPS. I am using the most basic GPS.
It doesn’t work for me at all, regardless of whether I enter the flight plan in the MSFS menu or into the Garmin directly. No combination of switching between HDG and NAV works, and switching the nav source to VLOC and back to GPS doesn’t do anything either. Also tried reinstalling PC-12, but the problem persists.
ETA: Disabled all my add-ons and it works normally, just what I was afraid of. Now to try to figure out which is the issue.
1 Like
I’ve just had massive fps drop and here I found a fix.
Go to general option, experimental, switch on/off or off/on ( depends of your previous settings) “use nanoVG…” Then fps should back to normal. I’ve tested twice without issues.
1 Like
on xbox series X the PC12 v 2.0 is UNFLYABLE.
tested on this route:
LIMJ/28 GEN6E GEN DCT LUMAV DCT OTGIG OTGI2E LIPZ/LAREN.I04RX
FPS dropped to single digits shortly after takeoff. Sorry but the code of this aircraft is not optimized for xbox SX and i can do literally nothing to improve FPS (tried everithing……AVIDANE OFF, uninstalling all 3d party addons…..etc).
Hoped things would have improved over time but also this version has serious FPS issues.
Xbox users should stay away from this addon until it is definetly optimized for this platform:-1:t3:
Bummer! Well, my PIREP after flying it last night from Chicken Strip to Sacramento was that it flew very well. No frame rate drops, but I did turn the Avidyne off immediately upon loading. Used the integrated GTN750Xi option. This on PC.
2 Likes
Same problem here. If you solve it can you post?
Well just to pile on, here’s my PIREP. I’m on an Xbox Series X
I flew the PC-12 (or attempted to) from Anchorage, AK to Orlando, FL. (I was going for the Saddle Sore achievement, which I got!! 
)
This was the route PANC/25L N0272F210 DCT TED DCT YESKA NCA13 YXY/N0272F230 J515 YQH DCT YOJ/N0273F250 J513 YMM DCT YVC/N0274F270 J513 YQD DCT VBI J538 DLL DCT OBK J84 DNV DCT TTH DCT GQO DCT MCN DCT TAY DCT OCF LEESE3 KMCO/35L
I took off in the morning and everything was fine for around 8 hours, right around DLL the frame rate started dropping (I don’t have a good way to measure the framerate since I’m on Xbox) but it just became extremely slow. Around every 3-4 real life seconds, would tick one second on the plane. I found something interesting that I haven’t seen in the forums (but maybe I missed it). If I switched to the outside camera, everything ran smoothly like normal, if I switched the view back to the cabin it then went back to a slow crawl. I couldn’t take it anymore and ended up landing at KJVL.
The next day I tried to resume the flight, taking off from KJVL and following the same route that I had planned, but within less than two hours it all became very slow again. I quit, restarted everything and resumed the flight this time I didn’t take off from anywhere, I started the flight directly on the air. Same scenario, within less than two hours everything got so slow as to make it unflyable. On every one of those occasions, switching to the outside camera fixed the problem, although it is useless if you actually want to be in the cabin when flying. Every time I went back to the cabin, it would go to crawl mode again.
The common denominator for when it got slow seems to be the following:
Night time
Altitude at or below 10,000 feet asl
Flying on top of densely urban areas
I used the avidyne on all flights.
Then again I did around an hour flight from central Florida to KEYW at night (also started the flight in the air) and everything ran smoothly so… who knows.
Second question. Has anybody tried using the ADF by tuning an NDB? Did it work for you? It worked for me but only when I’m using the backup VOR pointer, to the left of the main tracker (I don’t know the official names, but the one right below the airspeed indicator). If I tried setting the ADF arrow by using the panel right above the avidyne, was very messy. The ADF arrow comes up, it seems to track something… but it is buggy and it doesn’t work, if you use the backup one that one works fine. Anyway, just wanted to know if you’ve experienced the same, or maybe the ADF does work on the main display I just don’t know how to use it.
Hopefully this frame rate issue gets fixed some day, I really love flying this plane, but it is getting painful.
ADF/NDB are notoriously noisy and subject to several inaccuracies. There really isn’t a way to display this on the primary Horizontal Situation Indicator (HSI - under the attitude indicator) in the PC-12, though other displays, like the G1000 will display that there.
The “secondary” gauge to which you’re referring is called a Radio Magnetic Indicator or RMI. This is a combination of an old-school ADF gauge in which the arrow simply points to the relative bearing (degrees difference) from your heading, 000 being where the nose is pointing. The other thing that the RMI is combined with is the directional gyro, so the compass underneath the pointers moves along with your heading (and is usually coupled to a magnetometer, like the HSI, so it doesn’t drift). This gives you not only the relative bearing to/from the station, but the actual present magnetic bearing to/from the station. From that, you can much easier select and fly a particular course, but there isn’t a course selector like a VOR, it’s just reading the gauge and doing the compensations/math in your head.
Example: if you’re flying on a 270° heading and the arrow is pointing to 290, it tells you three things right away: the relative bearing to the station is 20° right of your nose, the magnetic course to the station is 290° and the magnetic course from the station is the reciprocal of that, or 110°. The formula for this is Magnetic Heading (MH) + Relative Bearing (RB) = Magnetic Bearing (MB). You can also watch how fast the arrow moves to discern trends, and even though NDBs rarely have DME, you can actually figure out how far you are from the station if you know your approximate groundspeed. The RMI can also display VORs in the exact same way, each needle usually electable between either VOR1 and ADF or VOR2 and ADF.
But the big trick with any NDB tracking is that if you want to fly to the station and there’s any sort of crosswind, you have to do a bunch of figuring to fly a heading that keeps you on the same course (freezing the needle), otherwise, you’ll “home” to the station, or fly a hook pattern as the wind pushes you off course and you continue to angle toward it, wasting time and gas (and not pointing your nose toward the desired direction in the case of an NDB approach).
1 Like
Yep I figured out the wind correction on NDB is nothing like wind correcting when you are tracking a Radial on a VOR, I was trying to do an NDB approach to Key West and I was ending up not in the right place and I wasn’t sure where the issue was… Until after several NDB/ADF YouTube tutorials only then I saw where the problem was, which you have explained above regarding wind. Thanks for the reply.
There is actually a way to overlay ADF on the HSI (and VOR1, VOR2 or both at the same time for that matter). It just doesn’t work… If you go to the panel just above the Avidyne there are two buttons with arrows on it. One has a single tail (which shows in white on the HSI when you have it active) and the other one has a double tail (which shows in magenta when you activate it). If you press any of those buttons and cycle through them you’ll see that you can overlay into the HSI either VOR1, VOR2 or ADF (and the same for the other button). This is on top of the regular green arrow for VOR navigation that is coupled to the AP when in VLOC mode. So if you play with those buttons you’ll see that you can in fact overlay those arrows on the HSI, VOR1/2 work fine… The ADF who knows what is doing… But as you said, the ADF works fine on the RMI, I just wanted to see if the ADF is broken on the HSI for everyone else or if I just don’t know what I’m doing.
1 Like
Anyone having problem with climbing to FL400 since the last update?
I set cab pressure before taking off, but still get the CAB PRESS warning and stuck on FL350 max and the speed is also abysmal at that point (110KTS).
I might be wrong but to my knowledge the service ceiling of this aircraft is 30000ft
6 Likes
That is correct. 30,000’
1 Like
Is the best method to recover frames is turning off the Avidyne, or have folks found that disabling it (by commenting the line out in the panel.cfg) also helps?
I disabled it by editing the cfg file. No fps issues since.
2 Likes
How to do that? THX!