I installed the latest Reality XP update which apparently included a database update for the Garmin 430/530.  The update said it would configure "aviation DB 1607 via GNSDBFILE env. var."  There are now many airports missing from this version, and I cannot seem to go back to the earlier version I had (2015) which had all airports.  I have replaced the BMAP.bin and worldwide.bin files in the Garmin/GNS trainer/GNS/db folder with my original BMAP and worldwide bin files, but it makes no difference.  Has anyone else run into this problem?  I'm wondering if there is some other file that is causing this, and if so how I can get back to my older database.

This appears to have happened to me as well.  And I am adept at keeping my worldwide.bin file updated.  I was concerned about this as the update description sounded a bit ominous in this regard,

It appears that the recent update modified the file and location, perhaps into the program data RXP path with a different file specification.  in my case:
C:\ProgramData\Reality XP\Common\GnsTrainer\dbfiles

If this cannot be overcome then I will wish to rollback to the previous release. 

I have not installed the GTN update yet and will hold off on installing it.

3 hours ago, xoddahs said:

I'm wondering if there is some other file that is causing this, and if so how I can get back to my older database.

It appears this worked for me.  Take your previous more current worldwide.bin file and put it in the folder I referenced above in my earlier message.

Then rename this file in that folder to some other name:  
006-d0170-00.bin     .bin         15,776,116           6/14/2016

Then rename worldwide.bin to that name: 006-d0170-00.bin

Be deliberate in what you do as there are two .bin files in that folder.  The one to replace is the larger one.

Edited August 24, 20214 yr by fppilot

Had same issue in X-Plane/Win10.  In that case, the installer will add a windows environment variable ""GNSADBFILE", pointing to bin. The variable will override the database location. Deleting that variable fixed it. So perhaps it is similar situation on Flight Sim?

My memory may be failing me but I believe that somewhere around that time (AIRAC 1607) Garmin had to exclude smaller runways (like less than 4,000 ft or so) from the worldwide database due to file size limitations. Those smaller airports remained in regional databases.

I'm not sure if that may be your issue.

1 hour ago, DavidP said:

My memory may be failing me but I believe that somewhere around that time (AIRAC 1607) Garmin had to exclude smaller runways (like less than 4,000 ft or so) from the worldwide database due to file size limitations. Those smaller airports remained in regional databases.

I'm not sure if that may be your issue.

That indeed is the case, but from a just-out-of-date standpoint what has been available among users has included all of the regions and that allows a choice.  Just have to position the one that is best.  That is why I suggested he replace the file that is in the new location with the worldwide.bin file he was previously finding satisfactory,  Just have to name it from worldwide.bin to match the new filename. 

When flying a different region the same file replacement and renaming applies.

Edited August 24, 20214 yr by fppilot

fppilot, that was the trick - renamed my original worldwide.bin and placed it where you indicated.  All my airports are back.  I do not have any kind of programming background, so I am word not allowed when it comes to things like Windows environment variables.  I now understand that in this case it does a redirect to the newer database file, but I'm not sure why it's done that way.  In any case, it worked, and I am very appreciative.

My database, as I previously said, is from 2015.  Is there a newer one available that anyone knows of?

 

In my last post, I meant to say "I am word not allowed when it comes to things like Windows environment variables."  Not sure how that got garbled.

 

word not allowed!  I'll try again -  "I am not knowledgeable when it comes to things like Windows environment variables."

 

Stupid autocorrect - didn't know it was on. It didn't allow me to use the word "word not allowed".

Hi,

I'm sorry for the delay with this question.

1) Please don't overwrite or rename the default GNS trainer database files

The GNS Trainer installs a set of database files by default here:
C:\Program Files (x86)\Garmin\GNS Trainer\GNS\db

This folder is a "special" folder for Windows (Program Files) with specific user access rights for a reason.

Instead, the GNS V2 supports specific means and facilities so that you can override and redirect the simulation to any other folder and/or files of your choice in an unobtrusive manner.

In other words:

Should you are using any custom aviation DB file, don't rename worldwide.bin at all. Instead, put the file in a folder you have control over (say "Documents\My GNS DB\") and use the environment variable GNSADBFILE to redirect to it.

Similarly, if you are using a custom set of DB files (aviation, obstacle, etc...) put them all on a folder you have control over, and use the environment variable GNSNAVDATA to redirect.

Last but not least, say you have a whole custom set of DB files from a more recent cycle, and you also have aviation DB files which are more recent, you can use both: put the whole lot for example in "Documents\My GNS DB" and set GNSNAVDATA to redirect to this folder for the whole lot, then put the aviation DB file for example in "Documents\My GNS DB\AVTN\" and set GNSADBFILE to redirect this specific file only to this folder.

We've added easy to use and configure environment variables so that you don't have to rename files, move files, lose files, overwrite files. You can use this facility to your advantage: it is all documented p20 and p21 of the RXP GNS User's Manual, in the chapter "Configuring Aviation Database Files", which is explaining in details what are environment variables in general, what are the ones the GNS is supporting, and what they are used for.

 

2) As for the latest update and the DB files:

We've tried our best to make it as clear as possible is is optional:

Quote

New: includes optional Aviation DB 1607

We've also tried our best to make it as clear as possible what this option is doing in the release notes:

Quote

The installer can configure the GTN Trainer 6.11 Worldwide Aviation Database AIRAC 1607 (compatible with the GNS Trainer 3.30).
When you select this option, the installer will set the GNSADBFILE environment variable (see user's manual for more details).

NB: The GTN Trainer 6.11 is no longer available for download and these files are included by courtesy. More details in:
"C:\ProgramData\Reality XP\Common\GnsTrainer\dbfiles\readme.txt"

We've also tried to make it as clear as possible what the new DB files are in the aforementioned readme.txt:

Quote

Garmin GTN Trainer v6.11 Aviation Database AIRAC 1607 (compatible with the GNS trainer v3.30):

- Jeppesen (Worldwide)  : 006-d0170-00.bin
- Garmin (North America): 006-d0170-30.bin

See RXP GNS User's Manual "Configuring Aviation Database Files" for more information.

It seems it was not clear enough though and I'd welcome your suggestions to update the installer wording!

This is challenging because it must display a single phrase, in the installer window, something which would explain and leave no ambiguity for all of these points:

• It is an option you can opt-out.
• It will install a 1607 AIRAC cycle which is more recent than any other custom or stock DB with an earlier AIRAC (and therefore potentially having different, less or more information than what you were used to in the case you were already manually overwriting the stock DB file(s))
• It is unobtrusive and reversible in running the installer again and deselecting the option, or in manually renaming/deleting the environment variable
• This will be using the embedded GNS V2 facility meant to overriding the stock DB which is documented in the User's Manual p20 and p21, or more generally in the chapters "Configuring Alternate Paths" and "Configuring Aviation Database Files"

I'm looking for any suggestion which will help making this clearer.

Edited September 3, 20214 yr by RXP

On 9/3/2021 at 10:51 AM, RXP said:

• It is an option you can opt-out.

 

IMHO, perhaps make it default to opt-in, instead of opt-out?

It seems users are more likely to be negatively impacted by breaking changes (e.g. airfield removal).

If users have been awaiting a new database, they are more likely to be on the lookout for it, and actively seek it out ( i.e. opt-in).

Just my .02

Can anyone give me some examples of missing airports?

Also, by default it uses the WW DB 006-d0170-00.bin, but if you're in the US, what about editing the environment variable and use instead:

C:\ProgramData\Reality XP\Common\GnsTrainer\dbfiles\006-d0170-30.bin

Edited September 9, 20214 yr by RXP

On 9/3/2021 at 7:51 AM, RXP said:

• It will install a 1607 AIRAC cycle which is more recent than any other custom or stock DB with an earlier AIRAC (and therefore potentially having different, less or more information than what you were used to in the case you were already manually overwriting the stock DB file(s))

I'm looking for any suggestion which will help making this clearer.

This is actually misleading... If you were running with the previous default, you would have a 2009 WW database with small airports included.   The 2016 database excludes smaller airports, as best I know.

Edited October 3, 20214 yr by Bert Pieke

@Bert Pieke I'm sorry to ask but I don't understand: what is misleading ?!!

I'm just saying if you use the 1607 DB, you could end up having more, or less, or same, than any DB you might be already using. I can see the wording is confusing though, and I'd welcome any suggestion to make it clearer. (not easy to cram the whole idea in a few words here?!).

Besides, I'd really like to get some examples, so that I can try finding which next best DB could be used instead in the installer for example:

On 9/9/2021 at 3:43 PM, RXP said:

Can anyone give me some examples of missing airports?

 

On 9/9/2021 at 12:43 PM, RXP said:

Can anyone give me some examples of missing airports?

I typically use my home airstrip CAM3 for the test.

3 minutes ago, RXP said:

I'm sorry to ask but I don't understand: what is misleading ?!!

You make it sound as if you only lose airports if "you were already manually overwriting the stock DB file(s))"

Edited October 3, 20214 yr by Bert Pieke

It will install a 1607 AIRAC cycle which is more recent than stock DB. If you're already manually overriding the stock DB file, you might want to opt-out this option.

Does it sounds clearer?

Edited October 3, 20214 yr by RXP