Hi

I'm unable to activate different legs within the default GPS system. With an active flightplan I select a waypoint press the menu button and press 'ENT' but nothing changes. After pressing the menu button receive the activate confirmation pop up but it is blank. After looking around this forum and a general search for FSX I'm sure that I should be seeing two waypoints here. I have tried different default aircraft, different plans with the same result. I have not made many additions to the default P3d setup. I have checked the install files for the two FSX aircraft I have added and they do not appear to have overwritten any P3D gauge files etc. A screenshot can be found here.

Any help would be much appreciated.

Yes sorry. Using Google and my BB Code is useless. The link should work okay now.

Just tried it and you're correct the Default GPS won't let you jump to another Waypoint. So I loaded up my own GPS (GNS430) that I created last summer and that works OK.

Not sure why the P3D GPS500 isn't working, I think the FSX one used to???? Have you tried porting over the FSX GPS to see if that's OK?

Regards

Jim

I have fs9 but not fsx, do you know if it will have the same file with the file name being fs9gps.cab?

Quote from jailsea on May 1, 2012, 13:29
I have fs9 but not fsx, do you know if it will have the same file with the file name being fs9gps.cab?

It is essentially the same file so it should work. I'm don't think MS updated the GPS when they upgraded from FS2004 (FS9) to FSX (FS10). If they had done they'd probably have changed the name!!

Jim

Geoff, the main reason the FSX file is larger than the FS9 file is because of the alternate xxx_night.bmp bitmaps required by the FSX lighting system. The actual .xml file is identical.

However, the differences between the FSX and Prepar3D gps500.xml files are legion! For one thing, several more Pages have been added to the WPT Group. On the other hand, aside from the minor difference of using @ g t ; instead of >, there's no difference whatever in the <Macro Name="MENUButton" macro, so I can find no obvious reason why it's not working as designed for selecting a specific Leg of the current Flightplan.

As a matter of fact, I do have the v1.2 version of the fs9gps.cab file. I had quite forgotten that I still have Prepar3D v1.2 installed on my "older FS Flightsim Test" computer!

The first thing I notice is that some, but by no means all, of the new "FAA" version changes have somehow crept into the original "non-FAA" version of the XML script... Surely this must have been accidental, and may well account for the "broken" MENU button function reported.

What I'm going to do is rename the v1.3 .cab file and copy/paste the v1.2 .cab file, then give it a through test. If it works correctly, then I'll be able to make an assesment of the differences to see what has "gone wrong."

For the record, I'm using a free program cleverly named ExamDiff.exe that I found on the web.

Here are the first two "differences" between the scripts. Note the non-FAA version has "FAA" in the gaugename header...

< <Gauge Name="GPS_500" Version="1.0">
---
> <Gauge Name="GPS_500_FAA" Version="1.0">

< 	<Macro Name="kWPTPageCnt">7</Macro>
---
> 	<Macro Name="kWPTPageCnt">9</Macro>

We added SIDS and STARS support which was fairly intensive. It sounds like there was a bug introduced in the process. The faa variant also has a splash screen set that displayed when you first turn it on. We turned that off by default because it annoyed most users. SIDS and STARS require custom content to work properly, so what I will do is move our upgraded versions of the gauge into a new cab file p3dgps.cab and return the fs9gps.cab file to its original version. I'll see if i can get the original cab uploaded somewhere while you wait for the patch. Using the fsx or older version of p3d cab should work too.

Thanks,
Beau