Add missing airports to Nav database?

[jeehell]

Hi

i'm not a fan of letting people code procedures themselves. Please before you start going that way, get some information on ARINC 424. This is not easy. I don't like letting out that information and do support on that, I really do not have the time to.

Regarding ILS, if you don't enter a runway in the MCDU, I believe pushing APPR on FCU should arm G/S and LOC modes as long as an ILS frequency is set. If not, I will have a look.

Now is time to do raw data flying...

JL

[OmniAtlas]

ARINC format http://olravet.free.fr/ARINC424-18.pdf

pls remove if this is not to be publically available. I just googled it.

[bindook]

Kai Tak OM & MM

PM|VHHX|VH|KL| OM|RW13|22.326835|114.092402|
PM|VHHX|VH|KL| MM|RW13|22.331539|114.165248|

[masterp]

I created additional.txt file to put code in, then placed to both navdata1,2 folder and recompiled bin files. However VHHX is not available.
Then I edit directly the navrecord.dat file to add VHHX code, building bin files, and then VHHX is now alive
I have Just made some touch and go with raw data, manual thrust & manual flying the IGS ... feeling GREAT !

[Maddin91]

Glad the code worked for you.

It's weird though. The additional.txt works fine for me. The problem when using the navrecord.dat is, that after an update of the Navdata (no matter if Navigraph or Aerosoft) this file will be replaced - so your code is gone and you have to insert it again. This has to be done after every update then.
additional.txt is not touched by an update - that's what it's for.

[masterp]

Thanks Martin I got the point
I dont know why, at first, I use txt file, however after bin created , txt file disappeared from both nav1,2 folder...VHHX not there.

[Maddin91]

Maybe some code was corrupt in your additional.txt - maybe happend while copying from the forums.

Attached is my file that worked for me.
Regards

[masterp]

Thanks a lot Martin, I will try again with your file and report back later
Cheers,

[OmniAtlas]

Cheers, will try this out when I get back in Jan.
We can try and work on programming SIDs and STARs next

[Beaufort]

Hi to all,
perhaps I´m too blind to see the difference:
I have success adding VHHX to the Database with the following text (THX JeeHell, OmniAtlas, Maddin91!) to "additional.txt":

PA|VHHX|VH|22.316667|114.203333|15|250|F100|9000|KAI TAK INTL|
PG|VHHX|VH|RW13|10930|1864|197|22.322177|114.196318|15|136|KL|1
PG|VHHX|VH|RW31|10930|716|197|22.305538|114.215179|15|316|IHK|1
PI|VHHX|VH|KL|1|111.900|RW13|22.33390756|114.201911688|088|22.33390756|114.201911688|3.1|15|
PI|VHHX|VH|IHK|1|109.900|RW31|22.326954603|114.190941006|316|22.304784469|114.214619994|3.0|15|
D |TH|VH|115.500|VDHW|22.239000|114.289001||||||TATHONG POINT
DB|TP|VH|280.0|H MW|22.239000|114.289001|TATHONG POINT
DB|RW|VH|377.0|H MW|22.3265|114.19116666666667|HONG KONG INTL
DB|SC|VH|236.0|H MW|22.32|114.13216666666667|STONECUTTERS

But I fail to add LSZA (which I want to use when flying ToTom´s A318 with the following text:

PA|LSZA|LS|46.0015|8.9092|915|250|F100|6000|LUGANO|
PG|LSZA|LS|RW01|4429|361|98|45.9995|8.908167|896|17|ILU|1
PG|LSZA|LS|RW19|4429|673|98|46.008167|8.9125|915|197|ILU|1
PI|LSZA|LS|ILU|1|111.5|RW01|46.011708|8.914225|17|46.011708|8.914225|4.4|942|
PI|LSZA|LS|ILU|1|111.5|RW19|46.011708|8.914225|17|46.011708|8.914225|4.4|942|

Does JH recognize the Airport is too small? Adding a faked too long RWY length does not make any effect, whilst VHHX is recognized with the short RWY length of LSZA as well.
THX for any help!