Bug - No airports in Active airport/runway selector

[Darrell Ryan 990634]

Gergely,

 

I could not find a way to report this using Mantis so I am posting this here.

 

Symptom: Active airport/runway selector dialogue does not contain any data in the airport field.

 

Problem: The mechanism that retrieves this data appears to rely on a non-standard sector file.

 

Description: To troubleshoot the problem, I took our current sector file and removed all airports and runways except for one. The following results in the symptom:

 

[AIRPORT]

KJAX 118.300 N030.29.38.600 W081.41.16.300 C ; JACKSONVILLE INTL(AIRPORT)

 

[RUNWAY]

; KJAX - JACKSONVILLE INTL(AIRPORT)

07 25 074 254 N030.29.46.381 W081.41.59.881 N030.30.19.339 W081.40.12.101

13 31 134 000 N030.29.31.780 W081.42.03.010 N030.28.42.240 W081.40.56.129

 

Workaround: The following results in the correct display of airport data in the Active airport/runway dialogue:

 

AIRPORT]

KJAX 118.300 N030.29.38.600 W081.41.16.300 C ; JACKSONVILLE INTL(AIRPORT)

 

[RUNWAY]

; KJAX - JACKSONVILLE INTL(AIRPORT)

07 25 074 254 N030.29.46.381 W081.41.59.881 N030.30.19.339 W081.40.12.101 JACKSONVILLE INTL(AIRPORT)

13 31 134 000 N030.29.31.780 W081.42.03.010 N030.28.42.240 W081.40.56.129 JACKSONVILLE INTL(AIRPORT)

 

IOW, if the entry in [RUNWAY] has "JACKSONVILLE INTL(AIRPORT)" as what appears to be a data field (no comment identifier, i.e. ";") then the dialogue is properly populated both with airport and runway data. Otherwise, it simply does not populate the airport field at all, however it does populate the rwy field.

 

This a bug for the simple reason the original ProController sector file format (.sct) also used by ASRC and VRC, and for that matter the new .sc2 format for VRC, do not define any such field in a [RUNWAY] entry. Despite this, EuroScope seems to have defined such a field for this pupose and as a result caused a major function of the software to fail, unless a similar non-standard sector file is in place. I urge you to patch this as soon as possible, as I was initially attracted to this program and would very much like to continue my evaluation. I'm sure you understand that it is unreasonable for me to change our sector file to a non-standard format just to be compatible with EuroScope.

 

Thank you for your attention.

 

Darrell Ryan

ZJX DATM

cc: RB, ZJX Chief Engineer

[Gergely Csernak]

Darrell,

 

This behavior is described in the http://euroscope.hu/wiki/index.php?page=Quick_Start at the How To Use Existing Sector And Position Files section. Yes, this is a light modification to the original sectorfile. But we need this information to connect the runways to the airports. We have tested and this change does not effect nor ASRC nor VRC.

 

Gergely

EuroScope developer

[Darrell Ryan 990634]

Gergely,

 

I withdraw my claim this is a "bug" since it obviously is an intended way to enable a feature. But it does require "hard modification." I have not counted them but I guess there are over 1000 runway entries in our sector file.

 

Thanks,

Darrell

[Sami Ylismaki 878340]

Gergely,

 

I withdraw my claim this is a "bug" since it obviously is an intended way to enable a feature. But it does require "hard modification." I have not counted them but I guess there are over 1000 runway entries in our sector file.

 

Thanks,

Darrell

 

This should help you out: http://fishu.kapsi.fi/fixrunways_zjx.php

 

Just paste all the values below [runway] into it and it will reformat the runways. Once completed you'll only have to copy & paste it back into the sector file. It's a very simple utility completed in couple of minutes and made just for this. In fact writing this post will take longer.

 

Should anyone else need help with similar reformatting the utility can be easily changed to accept different input formats, as long as the airport is mentioned somewhere in conjuction with the runway data.

 

This is how it works:

 

The accepted format:

 

; EVB - NEW SMYRNA BEACH MUNI(AIRPORT)

02 20 000 000 N029.02.56.281 W080.56.59.021 N029.03.34.229 W080.56.46.140

06 24 000 000 N029.03.17.561 W080.57.28.789 N029.03.41.101 W080.56.39.232

11 29 000 000 N029.03.21.262 W080.57.13.460 N029.03.09.029 W080.56.26.830

 

 

The output:

 

02 20 000 000 N029.02.56.281 W080.56.59.021 N029.03.34.229 W080.56.46.140 EVB - NEW SMYRNA BEACH MUNI

06 24 000 000 N029.03.17.561 W080.57.28.789 N029.03.41.101 W080.56.39.232 EVB - NEW SMYRNA BEACH MUNI

11 29 000 000 N029.03.21.262 W080.57.13.460 N029.03.09.029 W080.56.26.830 EVB - NEW SMYRNA BEACH MUNI

 

What it does:

 

Each commented out line will trigger it to memorize the line and it will be copied to the end of each runway input until the next commented out line. It will ignore short lines, like empty commented out lines.

 

Once done you can copy all the lines by pressing CTRL-A and then CTRL-C

 

I made a small change that will remove "(AIRPORT)" from the names to make them shorter.

[Darrell Ryan 990634]

Sami,

 

Wow! Talk about a helping hand! I really appreciate this. I will download and run it as soon as time permits.

 

THANK YOU

 

-D.

[Dorian Pope 1230746]

I hate to revive a dead topic but the website you have Sami has made my life complete! It works like a charm! Thanks for your help I really appreciate it.