Taking an approach into EGPH using the GTN750  is behaving in a way I can't quite make sense off.
The best way I can explain is via the screenshots below but basically I've got a flight plan created in the unit from EGNC to EGPH but the origin airport doesn't really matter.
Once I start putting in the arrival and approach at the bottom of the arrival it always places the airport itself BEFORE the approach, when I then add the approach the airport as a waypoint sits between the arrival and the approach.

What then happens is when I reach the final waypoint of the arrival the plan will then turn the direction of the runway as the airport itself is a waypoint here.
If I put in an approach to ILS 24 it turns to 240 way too soon obviously, the same goes for 060, doesn't matter what I choose.

After TARTN it should go to CI 24, instead of turns to 240

 

It totally ignores the approach basically, not like it's going the direction of the airport either, it just turns to 240.

 

 

And as you can see in the Navigraph route I would be turning 240 well away from the actual airport, if I would have gone ILS 06 on the approach it would turn 060 already there as well.  You can ignore TLA here as I removed that as a waypoint as it was kinda pointless.

I tried to remove the airport waypoint from the arrival but that then wipes the flight plan all together. I am relatively new to the GTN750 as I only bought it the other week but am I doing something incorrect here, I don't recall having these types of issue with the standard G1000.

The only way this DOES work is if I don't use the GTN750 for this, eg if I use an airliner with an FMC and enter in the STAR and Approach then it does not behave like this at all.

Thanks

Don't use a gtn 750/650 in place of the g1000.

I don't why it's responding like that but the Gtn is not meant to be used with g1000

As Ryan said, the G1000 should be a better unit to use. HOWEVER, what you are seeing is a result of the limitations of the (rather word not allowed) default MSFS flight planner.

The GTN750 uses the default flight planner unless you are using an aircraft that enables the WTT (Working Title Technologies) framework. PMS50 has various Community folder addons for many aircraft to enable WTT; they're on their website.

If you're using a plane that has a WTT option, use that, as its logic is much much better. Alternately, the TDS GTNXi, uses the Garmin trainer logic and is more intuitive. Finally, the G1000 will be much better than the default flight planner as it uses WTT.

Right, seems I have some very incorrect assumptions here.

I thought that the GTN750 was a 100% replacement of the GTN530 and G1000 units already inside the sim so whatever they were able to do the 750 was able to do albeit with a more intuitive interface.

So I installed a mod to replace all the 530's where there is no native support with the 750, I fly the Fokker F28 so I can use the 750 instead of the 530 if I want to use GPS instead of VOR to VOR.  I guess that may be the issue here, I also tested with the Kodiak where the mod replaces the G1000 and now I noticed that there is a seperate download for the Kodiak.  I'll try that one that on the kodiak next and compare, I guess the toolbar version may be what I need to use for the Fokker in that case as apparently that does WTT, some testing to do.

It also explains why the 146 does not manifest this behaviour as I understand its FMC uses the WT one.

Thanks for clearing that up, I had no idea about those caveats!

 

Edited March 5, 20242 yr by stefaandk
addition

 

That is the standard behaviour for the PMS WTT mode or not. I've asked PMS about it (since it is no longer an issue on the Working Title units) but apparently it can't be changed.

Work around is to activate the approach before you hit the leg direct to the airport. Not ideal though....

This isn't the behaviour you get on the Garmin Trainer (ie TDS) based products.

 

G

Yeah it's a bit of a bummer that I purchased a lifetime on the PMS50 only a few weeks ago and the reason being is that it had integration with Navigraph and based on my research at the time the consensus seemed to be that it was the better option for 'simmers'.   The airac lining up with Navigraph seemed like the logical choice, this particular issue though kinda blows that out of the water.

So are you saying that there is no fix for this at all, even with the toolbar one?  While the TDS would not behave like this and with the new edition its airac would now also line up with what's inside MSFS?  Has the pms50 product effectively become redundant?

Thanks again.

I have a lifetime license for the GTN750 as well. I've been happy with it and think that it still offers some benefits over the TDS unit, although I'm finding the TDS unit (which I got just now, after the Navigraph update) to be much more intuitive and powerful for the daily stuff.

The question you're asking came up on the PMS50 Discord and I've since seen a page on the website that highlights the differences vs the TDS unit: https://pms50.com/msfs/extra-features/

Personally, I'm currently running both at the same time. I'm using the TDS on a second screen and the PMS one in the cockpit. I prefer having the unit be on a second monitor, plus I like being able to take advantage of the PMS unit when helpful.

41 minutes ago, stefaandk said:

Yeah it's a bit of a bummer that I purchased a lifetime on the PMS50 only a few weeks ago and the reason being is that it had integration with Navigraph and based on my research at the time the consensus seemed to be that it was the better option for 'simmers'.   The airac lining up with Navigraph seemed like the logical choice, this particular issue though kinda blows that out of the water.

Same boat for me as well, although there are still advantages and disadvantages to both units.

I fly into Edinburgh regularly in the sim, generally if I'm flying the STAR I get vectors, else ATC gives me TLA and no STAR. On the PMS I find the STAR & Vectors to final work best...

 

G

Either the PMS or TDS will be fine... but don't use a GTN on a G1000 aircraft, or one with an FMS for that matter.  I would highly recommend sticking to addons that support the GTN in 3d cockpit (and use that as a reference even if you are doing GTN 750 hardware/ standalone)

Aircraft with TDS GTN integration:

https://tdssim.com/gtnxivcintegration

Aircraft with PMS GTN integration (skip the ones with G1000 replacement!!):

https://pms50.com/msfs/aircrafts/

Children of magenta line! LOL What is wrong with switching to heading mode intercept localizer manually and then fly ILS? Or alternatively quickly press proc->activate vector to final ?

2 minutes ago, sd_flyer said:

Children of magenta line! LOL What is wrong with switching to heading mode intercept localizer manually and then fly ILS? Or alternatively quickly press proc->activate vector to final ?

Nothing is wrong with it - but the avionics should still be able to work (as long as we aren't using GTNs in place of a G1000)... especially as many airports do not have a traditional approach.

Yes exactly, it's very confusing if it's not behaving properly.  I love my old school planes and even love a VOR to VOR that's why I love flying planes like the 146 and Fokker F28.

At the same time I also tend to multitask when flying so having the option of a GPS tracking the flight plan and associated procedures is certainly a bonus but to then discover this is certainly frustrating.  I now loaded the same flight plan into the G1000 on the 172, added the procedures and then opened up the 750 from the toolbar and yes the G1000 is routing correctly while the the 750 is again putting a turn to 240 at the last waypoint of the arrival prior to the approach.  So indeed 750 is simply not doing the right thing regardless. 

Downloaded the official kodiak add-on as well for the G1000 replacement and still misbehaves so it's almost useless really when it comes to its ability to follow the magenta line.  
Then I pulled up the p28 Arrow which has official support for the unit by enabling it via its tablet, still the same issue!
Ok one more the Chancellor 414 which has support via its livery selections for a choice of GTN750 and GTN750+WT.
So I picked GTN750+WT and again still wrong!!!

Then for the one where it really mattered the most and what brought this to light is replacing the 530 with the 750 in the Fokker 28.
I removed the mod so the 530 is back the default.
Next I used the toolbar 750 to import the flight plan from Simbrief so it shows up in the 530 but as you can see below the 750 has that EGPH waypoint and a turn to 240 again prior to approach while the 530 does not!
For a paid product this is disappointing to say the least, I would love to see someone pull this up in the competing GTNXi to see how it behaves there!  It's the INPI1E arrival and the ILS 24 approach.

I guess this is enough as a work around at least as it will allow me to follow a GPS route in the F28 without some sudden weird turn but yeah pretty clunky.  

Worst of all is that no matter what I can't rely on the 750 to do the right thing with any approach anywhere based on this behaviour.  The only GPS units which do this transition correction are the 530 and the G1000.  Not a single combo of the 750, offical, mods you name it is doing this correctly, they all have the premature turn so yes it's a serious shortcoming of the product.  Is this going to be an issue on every airport's approach !?!

 

59 minutes ago, stefaandk said:

The only GPS units which do this transition correction are the 530 and the G1000.  

Actually, the TDS GTN750 flies the approaches correctly.. so should belong on your list.

Euh not sure what to say to that as the whole reason for the existence of this topic is the fact that the GTN750 did not behave correctly.

It should go TARTN > CI24 which is what the built in ones do.

Instead it flies TARTN then turns a heading of 240 which isn't even going towards EGPH from its position at the time.
It just flies the runway heading ignoring the approach procedure itself and will just keep going that direction endlessly.

Yet at the same time it knows of the approach existing because if I were to pick ILS 06 it would fly 060 degrees.

 

8 hours ago, ryanbatc said:

Nothing is wrong with it - but the avionics should still be able to work (as long as we aren't using GTNs in place of a G1000)... especially as many airports do not have a traditional approach.

if you sim pilot yes. But trust me real GPS units are far from perfect! I had at least two I owned that glitched IRL during approach. Both were bench tested and consequently serviced .