Oh, didn’t know of that little bug. Thanks, I will keep an eye on that!
I guess I found my main question: I was still using the WT Mod for the GNS 530. Uninstalled and the plane intercepted the LOC using the stock version of the GNS.
But I already installed the PMS500 Mod for the GTN. Flew the LOC without issues too.
1 Like
Excellent! Yeah, mod conflicts are always the most likely issue with navigation equipment.
1 Like
Be careful here. When you say mod do you mean in the community folder or from the content manager. If it’s community then yes everything from WT should be removed. However the content manager ones are needed. Well one of them is and the other one is still needed for some aircraft that have yet to update their aircraft to point to the new GNS. The BN-2 Islander for example.
1 Like
Yes, I’m referring to the content manager version. The “grey” one (that applies to the stock aircraft) is there. The other one I removed because of the conflicts it causes to some aircraft. For that matter, I’m using the PMS version. It’s not as good as the WT, but it works well. My V35B Bonanza altitude selector isn’t crazy anymore, LOL.
I hope FlySimWare updates the C414AW to the WT GNS in the near future… The Great Just Flight Arrows are already updated!
1 Like
Not to mention I bet you saved some lbs from the weight of the glass?
Great pic,the 414 is lookin good!
I had an approach yesterday into Savannah Georgia and I had to toggle the vloc gps a couple times then she grabbed the ils approach perfectly.
This is one of my favorite planes to land in the sim, the feel makes you want to perform touch n go’s all day. 
Could somebody please clarify:
Installing the latest version of the 414A, the GNS 530 which comes with it appears to be out of date, with missing features.
In the content manager, I have a v1.1.10 of the WT GNS 430/530, which the default planes are using.
I just installed installed v1.1.4 of the WT GNS 430/530 from the marketplace, and now the Chancellor is utilising the v1.1.10 version (same as the default planes) which seems very strange.
I don’t have anything in my community folder apart from the 414A itself.
Is it correct to have both versions of the Working Title GNS 430/530 installed?
Yes, the default planes already use the Wortking Title GNS, with a lot more functions and realistic fonts, etc
The 1.1.4 version in marketplace (up) is the version you install to have the Working Title GNS 430/530 in add-on planes. Without this installed, the 414 will show the old default version of the GNS.
The 1.1.10 version (down) is the version being used by default planes.
1 Like
So I need both versions installed? 1.1.10 for default planes and 1.1.4 for 3rd party planes?
The 1.1.4 is only a very small linker file (look at its file size) it’s not actually a GNS. All it does is re-direct any add-on aircraft that have not yet been updated to point to the new v1.1.10 GNS. Without it they still point to the old Asobo GNS.
4 Likes
Is the manual “Pilot Manual Version 2.0 Nov 13, 2022” from the website the newest version? It seems rather incomplete.
Using the 400B in the C414 I cannot get the glideslope engaged.
The manual states the glideslope should engage automatically:
How is this done? The localizer is tracked without problems.
Are you using the WT GNS 530 or the old GNS version?
The WT GNS 530.
I see the glideslope on the HSI coming down, but it does not engage.
I experienced the other way around a few days ago. Flying an LOC approach in NAV mode, the plane didn’t follow the localizer. I had to turn the LOC on via keyboard shortcut (CTRL+O) for the plane to follow the approach. My ILS approaches were okay.
I suggest you to remove the WT GNS from your content manager and fly the same approach using the old default GNS to see if the problem goes away.
Ok, I’ll try that.
The cruise checklist says:
Mixtures - LEAN
THat’s not necessary, right?
Either way it doesn’t work.