When I moved from the GNS to the GTN, it was like moving from DOS 3.1 and floppy drives to a modern day computer. Can't imagine having to go back. http://www8.garmin.com/aviation/pdfs/GTN-GNScomp_6xx.pdf

+1

I'd say the old GPS systems like the Garmin GPS 100 and the Bendix KLN89 and KLN90 better suit the comparison to DOS 3.1. The Garmin GNS set is at least up to Windows 98 standard  :Big Grin:  I still find the GNS 530/430 a very user friendly GPS system and the Flight1 version brings back variety in the Prepar3D world.

But if DOS works for what I do, why change?

I'd say the old GPS systems like the Garmin GPS 100 and the Bendix KLN89 and KLN90 better suit the comparison to DOS 3.1. The Garmin GNS set is at least up to Windows 98 standard  :Big Grin:  I still find the GNS 530/430 a very user friendly GPS system and the Flight1 version brings back variety in the Prepar3D world.

I flew RW on the KLN90b. While a great piece of kit I didn't find it overly user friendly. Then when King stopped supporting it we replaced it with a garmin 400...really nice in it's time. Then a couple years ago we got the garmin 1000....now that was stepping into the 21st century. It was great. I retired last spring so that's the last cool gps setup I will get my hands on in the RW..

When pmdg makes the dc6 available for fsx/p3d there's apparently a garmin400 in the overhead panel. Hopefully  this new 430 will work in there.

Dave

I think even if you get worldwide data these days, runways with length of 4000 ft or less are excluded because the database get's too large.

 

(1609 is actually old now, 1610 is current)

 

PM me for details about navdata.

Can you choose to install US/Canada/Europe databases only?. Do those include runways with less than 4000 feet? I hope so, else those products will be useless for my GA flying

Garmin changed their navdata distribution system 2Q 2016.

 

If you can find a copy, you can install just US data for example and have the smaller airfields.

 

If you stick to 1513 or 1601 WW datasets, or earlier,  you are ok also.

 

The Flight1 GNS gauges come standard with earlier data.

But if DOS works for what I do, why change?

 

No reason whatsoever! Well, maybe the lack of support. But that was not my point :smile:

I flew RW on the KLN90b. While a great piece of kit I didn't find it overly user friendly. Then when King stopped supporting it we replaced it with a garmin 400...really nice in it's time. Then a couple years ago we got the garmin 1000....now that was stepping into the 21st century. It was great. I retired last spring so that's the last cool gps setup I will get my hands on in the RW..

When pmdg makes the dc6 available for fsx/p3d there's apparently a garmin400 in the overhead panel. Hopefully  this new 430 will work in there.

Dave

 

There's a great KLN90B freeware gauge out there, which is also used in the A2A Texan. Indeed I find it a lot harder to enter a flightplan compared to a GNS 430, let alone a GTN 650.

Freshly uploaded on the tube. Very detailed and infomative.

 

How did these guys end up with a semi-current  (1608)  navdata set for Europe?

 

Do they tell you?

How did these guys end up with a semi-current  (1608)  navdata set for Europe?

 

 

 

I raised the question on youtube...let´s see  :smile:

Unless they own a 430/530 and have a paid subscription... it wasn't done legally.

Unless they own a 430/530 and have a paid subscription.

 

Hi Ed,

 

Could you guys use the same technique of Screen Scrapping of the demo instead of redoing the entire logic all over again of the GPS? Why did Mindstar take the path of redoing the whole thing? I am curious.

 

I am hoping someone would  do this and provide an API for hardware interface for those knobs and buttons for a reasonable price  Instead of giving us this amputated/crippled GPS.

Hi Ed,

 

Could you guys use the same technique of Screen Scrapping of the demo instead of redoing the entire logic all over again of the GPS? Why did Mindstar take the path of redoing the whole thing? I am curious.

 

I am hoping someone would  do this and provide an API for hardware interface for those knobs and buttons for a reasonable price  Instead of giving us this amputated/crippled GPS.

We aren't about to do what Flight1 and Reality-XP are doing.  I won't go into the reasons why as it would get the thread locked and start a huge freaking fight.

We aren't about to do what Flight1 and Reality-XP are doing.  I won't go into the reasons why as it would get the thread locked and start a huge freaking fight.

 

LOL! Not sure if that is ethos or pathos....

 

 

I still find the GNS 530/430 a very user friendly GPS system and the Flight1 version brings back variety in the Prepar3D world.

 

Absolutely.  The UI is, indeed, um... unique, but I've spent years using it and having learned to think in Garminese I can get where I want to go quickly these days. 

 

Not sure why some seem determined to tell some of us we're "wrong" for wanting the 430/530.  I think we all get that the GTN's are in most ways superior, particularly when it comes to the UI, but those of us excited about having a 430/530 option for P3D have solid reasons for going that route.  If someone's not interested in these, well... they're not interested.  But many of us are.

 

Scott

i just want rxp to lower the price of the 'unlimited' pack and edit the bmp of the bezel so it's a darker shade of gray...

 

then we'll see about the gtn.