My main comment was, please don’t just say “I’m using the PMS50”.
The PMS50 what? Please add GTN at the end of it. Or GNS530 if that’s what you’re using. I still don’t know.
It doesn’t matter, but, personally, I’m still using the PMS50 GNS530 for compatibility for some of the planes I use, and I deleted the Marketplace GNS530. IOW, yes, there’s still a use for the PMS50 GNS530 in the sim even though it’s not supported anymore. It still works as is for those planes that still reference the AS530.
I did. Just because they say PMS50 GTN doesn’t guarantee that’s the one you’re talking about.
All I’m asking for is clarity when offering help. There’s enough confusion already surrounding all the GPS addons and their interactions without adding to it. If I was confused, I’m sure others will be too.
The PMS50 site is for the GTN750. The github site is for their 530 implementation. The other links go direct to the pages referenced, such as their fix for the 530 mouse click issue, or the specfic WTT 750 packages. Not sure what your point is otherwise, if you can’t understand the context from the actual site where you download said packages.
Perhaps you should just include links in your replies, would make it easier to know what you are actually referencing.
There is no popup mode (aka toolbar mode) for the github 530 implementation only their 750, and if you use both their 750 and 530 packages (or have) then you would absolutely know the difference.
It’s there so you can use it in aircraft that don’t have it integrated (like the PC-12 wasn’t initially), or if you want it on a second screen without pulling it out. It’s good to know all the features they offer.
Just sayin👍
Thanks for your help,
But my question had nothing to do with any external systems, just the basic instrumentation of any aircraft, even non-IFR certified ones.
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?
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
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.
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.
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.
