I did a flight to Dubai (OMDB) in the Captain Sim 777 (and later I tried it in the CS 767). I had selected my STAR (DUBI6S) and Transition/Approach (LOVOL) for landing on RWY30R, so all was set. All was fine until I reached the final turn towards ULDOT, where the ILS/GS should have come alive, but didn't! There was nothing showing! I pressed APP and the Heading Indicator changed to 120 degrees and the 777 (and 767) turned away from the airport. I was puzzled at what was happening and so I ended up disengaging the AP and landing manually.
I started FS Approach Pro with the 777 all ready for the approach and started about 15 or 20 nm from RW30R, used the CDU to select RW30R as the ARR and proceeded to approach. As soon as I pressed LOC or APP, the heading Indicator switched to 120 and the 777 and 767 flew away from the airport.
So I opened (using notepad) the
FSX\Captain_Sim\navigation\runways.db file from the Navigraph cycle 1308 and looked up OMDB runway 30R. This is what I found in regards to OMDB:
OMDB;3.00;110.10;25.264617;13123;55.350414;12L;122.0
OMDB;3.00;
109.50;25.252828;14590;55.364370;
12R;
122.0OMDB;3.00;111.30;25.235914;14590;55.394875;30L;302.0
OMDB;3.00;
110.90;25.247683;13123;55.380950;
30R;
302.0As you can see, the frequency for 30R is 110.9 and the heading is 302 degrees. So why was I doing a 180 degree turn every time I pressed LOC or APP? Here is why I believe it is happening:
Notice that in the FSX MAP (Airport Info for OMDB), runway 30R is listed as 109.50 @ 300
o, whereas runway 12R is listed as 110.90 @ 120
o!
So that appears to be the answer to the problem. To fix this, I have edited the runways.db to match the runways at Dubai as they are listed in FSX.Both the 777 and 767 fly it fine (they Autoland without any problems now). Here is how it looks after I modified it:
OMDB;3.00;110.10;25.264617;13123;55.350414;12L;122.0
OMDB;3.00;
110.90;25.252828;14590;55.364370;
12R;
122.0OMDB;3.00;111.30;25.235914;14590;55.394875;30L;302.0
OMDB;3.00;
109.50;25.247683;13123;55.380950;
30R;
302.0I checked the NavDataPro runways.db, and they are almost identical to the navigraph ones:
OMDB;3.00;110.10;25.264617;13123;55.350414;12L;121.8
OMDB;3.00;109.50;25.252828;14590;55.364369;12R;121.8OMDB;3.00;111.30;25.235914;14590;55.394875;30L;301.8
OMDB;3.00;110.90;25.247683;13123;55.380950;30R;301.8So I checked this out in the OTHER 737NG and it flew the ILS/GS (for runway
30L?) okay UNTIL about 2 or 3 miles from the runway threshold, then it started swaying left and right, I had to take control of the 737, then go around, reset the NAV Radios to 109.50 and so that it too landed fine on runway 30R!
So the question is this: Why is the navigation data matching what is most probably the real world data, but is not matching the info in FSX. It was easy enough to change the runways.db. But NOT so easy to change the OTHER's navigation data! But it looks like it can be done here:
DUBAI INTL OMDB30L14590300 25.235914 55.394875111.3030000060
DUBAI INTL OMDB
30R13123300 25.247683 55.380950
110.9030000031
DUBAI INTL OMDB
12R14590120 25.252828 55.364369
109.5012000010
DUBAI INTL OMDB12L13123120 25.264617 55.350414110.1012000010
I'll have to test it out to be sure.
How do those people flying on VATSIM (or similar online flying), get around this problem? Do they use runways 30L and 12L so they won't encounter any problems with the discrepancies?
I would be interested to find out if you others have encountered this problem at Dubai. Where else in FSX might this be happening?
Pages: 1
Has anyone else noticed this? (Read 6036 times)
