Hi,

I recently found a video on youtube by Sprocket Simulations where an RNAV approach into KSBA is demonstrated with LPV coupled on the GNS530 livery. Please see 17:00 minutes into the video.

I don't have any issues with LPV coupled approaches on PMS GTN 750, however I have been unable to reproduce this with the C414 GNS 530 livery as demonstrated by the above video.

The video instructs to install WT GNS530 package from Content Manager (which I have done). However, this video is now 8 months old and there is now a message on WT GitHub page (https://github.com/Working-Title-MSFS-Mods/fspackages) (DEPRECATION NOTICE see below).

So I am not sure if something has changed and the LPV capture has become broken on FSW C414 GNS530. All I see when joining final on the GPS is APPR (no vertical guidance) not LPV, and AH displays white-red GS INOP flag.

1) Is LPV capture on the GNS530 livery supposed to be still working, or is it currently broken (i.e. a known issue)?

2) With an fully updated MSFS, do I still need to explicitly install WT GNS 430/530 package from Content Manager for C414, or can I exclusively rely on Aricraft Avionics Update 1?

Thank you.

DEPRECATION NOTICE

As of Aircraft and Avionics Update 1, all active Working Title content has been fully integrated into the standard Microsoft Flight Simulator installation. The packages in this repository are no longer needed, and should be uninstalled from your Community directory to avoid conflicts with the base game content.

Update:

This page (https://www.workingtitle.aero/packages/gns/) talks about compatibility issues with hot swapping between GNS530 and other GTN units (like PMS), however I don't this this applies to FSW C414 as a separate panel is provided per navigator. I have both the WT GNS530 package installed as well as PMS GTN 750 for use with the different livery options.

Edited October 31, 20232 yr by m88zk

15 hours ago, m88zk said:

The video instructs to install WT GNS530 package from Content Manager (which I have done).

The WT GNS530 in the C414 will fly an LPV approach including the GP -- I just did it to double check. Here is a pic of the LPV 35L approach into KCOS.

The first thing we should do is make sure you really do have the WT GNS530 loaded into the C414. One way to tell is to see if you can enter waypoints into the flight plan using the keyboard. Note the little blue rectangle which represents a keyboard in the picture below. If you do have the WT GNS530 loaded, AFTER you enter the first character of a waypoint with the mouse as usual, if you then click on that little keyboard symbol it will turn blue as show in the picture and you can enter the waypoint using your keyboard. Can you do this with the GNS530 you have loaded?

Al

Edited November 1, 20232 yr by ark

Thanks for your reply Al.

Your comments prompted me to recheck my Communities folder and I had totally forgotten that many months ago I had installed pms50-gns530 which was conflicting.

Everything works perfectly now after deleting pms50-gns530, but I found that I do need the WT 430/530 package installed via Content Manager to get the blue keyboard.

Thanks again.

kind regards

Martin

39 minutes ago, m88zk said:

... but I found that I do need the WT 430/530 package installed via Content Manager to get the blue keyboard.

After the next C414 update you will no longer need those two WT 430/30 files from the Content Manager for the C414 (other planes may need them, however). The panel.cfg file for the C414 currently installs the Asobo GNS530, but after the C414 update (don't know when that will be) the panel.cfg file will install the WT GNS530 by default. Although there is no real reason to do so at this time, you can make this fix yourself if you are comfortable using a text editor like Notepad++ to make a small change in the panel.cfg file for the GNS530 version of the plane as shown below. (note there are different panel.cfg files for the different C414 GPS options). The line with the // in front is the old line and has been commented out by the forward slashes. The line above that is the new line.  As you can see the only difference between those two lines is the WT530 entries have replaced the AS530 entries in that one line. Note the " texture " line is not changed. So with this change, the panel.cfg file now loads the WT GNS530 instead of the original Asobo GNS530.

Al

[VCockpit01]
size_mm                = 320,234
pixel_size            = 320,234
texture                = AS530_Screen
htmlgauge00=NavSystems/GPS/WT530/WT530.html,         0, 0, 320,234
//htmlgauge00=NavSystems/GPS/AS530/AS530.html,         0, 0, 320,234  Old commented out line.

 

Edited November 1, 20232 yr by ark

Thanks Al.

I made those changes you suggested to panel.cfg and can now use the WT530 without the explicit WT 530 package installed in Content Manager.

Martin