I have version 1.4.1 and both the PMS GTN750 (paid v2.1.25) and the TDS GTNXi power on and display correctly, though I haven’t tested all their functionality yet.
Yes, those work. It’s the 530 that has the issue.
That’s exactly the technique I’m using. Today everything worked fine twice at KSBA ILS7, and never worked (tried twice) at KLAX ILS 25L. Not sure what is going one… PNS GTN750
That’s pretty weird! Did it blow through the localizer?
Yep, LOC and GS never go from armed (location down on the AP display) to active, HSI needle displays normal. Doing more tests to find out when it works, and when it doesn’t.
That is odd. FPS on this plane is well optimized. Do you have liveries, camera mods or interior mods? Have the latest hotfix and update from the 750 mods?
1 Like
I’ve done some more tests. This is the result, even if it sounds crazy. Whenever I make a flight plan in the MSFS 2020 world map, I cannot capture LOC and GS as described previously. But when I don’t make a flight plan in the world map, but select the ILS approach during my flight, it works. What could be the difference? I am aware, of course, that I must tune/check the correct NAV freq, the correct course, VLOC on CDI, go to NAV to capture LOC, go to APR to capture GS, etc. (I have used various Garmins in the sim and the 530 in real life, but never the 750). And it is all set up correctly because I can certainly handfly the ILS approach following the needles. But I can’t figure this one out, lol. I must be doing something dumb. HELP, lol!
My routine is to create a flight plan in Little Navmap and enter the waypoints into the GTN750 on the ramp while the engines warm up. This seems to work quite well. I also have Navigraph loaded in both MSFS and LNM, so waypoints match.
I mean, I think it actually makes sense that there’s a scenario where having an MSFS FP in the system is fooling with the AP’s course guidance by inadvertently taking precedent somehow. It would also help explain why TDS users are reporting fewer issues than PMS GTN/GNS users: the TDS can’t read the MSFS flight plan in any sense so there’s no good reason why a TDS user would set up the FP on the map screen beforehand.
Sounds like this is worth posting in one of Flysimware’s official channels.
This is interesting. There is also a difference between filing an instrument flightplan at ATC vs VFR. When flying an instrument departure ATC keeps nagging about resetting transponder. When I cancel the instrument flighplan and right away request ‘flight following’ the transponder is being recognised.
This happened with the GNS530 liveries, however they don’t work after the last hotfix. ;-(
Coupled with the many problems to get hardware recognised with Spad.next , its safe to say there is some special coding going on with this plane. I expect this beta period will take longer than expected…
Purchased this today and struck an issue straight away. When i spawn into the aircraft the default camera position seems to be underneath the aircraft looking at the undercarriage. When i reposition it it with the arrow keys my face is up against the dashboard lol.
With Track IR on i need to sit a meter back from my desk to see the entire instrument panel. Seems like a nice enough plane but its a little unflyable atm for me. BETA I guess by still?
1 Like
I can confirm. Exactly the same. Not a big issue, I just configured a custom camera view mapped to a hotkey. But I didn’t read about this issue anywhere else so I thought it might be something with my trackIR config or whatever. But I’m somewhat glad I’m not alone on this 
1 Like
Actually I like the default cockpit view. At least the Instruments are readable that way. Especially with TrackIR it is no big deal because it is very easy to switch the view to see the desired instruments.
In the real cockpit you wouldn’t have all in view, too. There is less space in the cockpit than most think.
1 Like
for the camera, i use this mod : Flysimware Cessna C414 Chancellor - Better Cameras » Microsoft Flight Simulator
As a heads up, people on Discord report issues with altitude select, the AP doesn’t seem to stop climbing at the entered altitude.
I’m staying on 1.3.2 since it works okay for me so far.
Can confirm, AP doesn’t catch preselected altitude in v.1.4.2
FWIW, I’ve done several flights today with v1.4.2 with the TDS GTN750 variant and I’m catching the armed altitude when climbing every time (I’ve tried using both VS @ 1500fpm and IAS @ 120 kts. Both worked as expected).
I haven’t tried it with any of the other GPS units though…
Are you sure, I just tested that last night, works as far as I can tell…
Doesn’t work on my system, tried several flights.
Wasn’t 1.4.2 released today? Yesterday we still had the broken GNS530?