Guys, for your information, this has very little to do with a decision made by Flight1 to "privilege" US simmers or to "punish" those who use runways shorter than 4000 ft and much with Garmin's decision to split their own database. That simple.

But Flight1 could very easily have provided information to this effect about the update they published so that people like myself could make an informed decision about whether to update or not. That IS their call. Not the end of the world but it would have been nice to not go through the update process and then have to roll straight back again

Can we use the old database files from the previous 5.13 garmin trainer then? I think we can just copy those files back and all will be okay.

Can we use the old database files from the previous 5.13 garmin trainer then? I think we can just copy those files back and all will be okay.

 

There are people posting on the GTN support forum that they would like to reinstall 5.13 and how to get a copy of it. Apparently this affects people in Europe mostly. 

 

 

Can we use the old database files from the previous 5.13 garmin trainer then? I think we can just copy those files back and all will be okay.

 

Possibly yes, but I didn't try so far; instead I reversed to GTN trainer V5.13, which suits my purpose.

Just an FYI. I discovered today on a few flights, that when I tried to put a few airports into a flight plan, my GTN didn't seem to have the airports in it's data base and wanted me to create waypoints. After trying a couple of times, I decided to go to the GTN Trainer, and input the same airports, and they came right up. The two airports were CYTZ and N38. I found out that there are two databases in the GTN, one is North America, and the other is Jeppesen Worldwide. What the update did was change all the database defaults for my aircraft  to worldwide . The GTN Free Trainer was still on North America, and that is why I could look up the airports there. but not in my aircraft using the GTN 650. To change it, I went into the F! GTN config program, and select the aircraft, the GTN unit you want to change, and scroll all the way to the bottom and and find AVDB and you can change it from World wide to North America. Now I have my airports working again. 

 

Probably that's good and enough in case you decide to exclusively fly inside the US. If you eventually decide to fly into Europe, or anywhere outside the US with a GA aircraft like the ones on which a GTN is or it should be installed, you'll be missing a LOT of known airports and will have to create user waypoints for each to be able to use the GTN capabilities. This is for me a non-sense and it doesn't matter to me if it comes out of a Garmin or a F1 decision.

That's why is becoming very useful these days to have safe backup copies of previous versions in a separate drive in case people wants to revert back to them.

I'm staying with my v1.14 and my airports!.

Cheers, Ed

Can we use the old database files from the previous 5.13 garmin trainer then? I think we can just copy those files back and all will be okay.

Would that give us the full airport database together with the v6 trainer nav updates?

Would that give us the full airport database together with the v6 trainer nav updates?

 

 

I think it will, that way you can use the latest Garmin Trainer with the previous database. I don't see why it wouldn't work.

I have Macrium Reflect on my PC which backs up entire harddrive on a continual basis. I am going to take the database folder from a few days ago and copy it to the trainer database and see what happens, Will report back. 

 

 

 

Well, that apparently doesn't work, because when I start the GTN trainer now, it hangs up on verifying on Navigation and Terrain. 

Guess I have entered into one of those Custom Holding Patterns for about 30 days on this upgrade until there is more clarity....

Pm me if you're outside of the USA about navdata

 

And yes, you can use the older navdata

I have Macrium Reflect on my PC which backs up entire harddrive on a continual basis. I am going to take the database folder from a few days ago and copy it to the trainer database and see what happens, Will report back. 

 

 

 

Well, that apparently doesn't work, because when I start the GTN trainer now, it hangs up on verifying on Navigation and Terrain. 

 

You have to copy the navdata file only and rename the file.

 

PM Ryan or me if you run into difficulties with this.

You have to copy the navdata file only and rename the file.

 

PM Ryan or me if you run into difficulties with this.

 

 

Is this the file you are talking about?   006-D2659-00.dat   which is one of 8 files in the db folder? 

Is this the file you are talking about?   006-D2659-00.dat   which is one of 8 files in the db folder? 

 

In the new Trainer: the 006-d0170-00.bin file.

 

In ProgramData\Garmin\GTN Trainer Data\DB

 

In the old Trainer: AVTN_WW_DB.bin

Yes, and the -30 file is the Americas one - you can switch between the two using the F1 config

 

 

In the new Trainer: the 006-d0170-00.bin file.

In ProgramData\Garmin\GTN Trainer Data\DB

In the old Trainer: AVTN_WW_DB.bin

 

Thanks a lot for the info, Bert!