A320 FMGS B34

[adonismartinez]

Hi,
can anybody test the following approach:

EDDF (scenery Mega EDDF X by German Airports)
25 R
Z ILS 111.35 IFNW

Everything is OK about the frequency on PFD, MCDU and RAD NAV. AFCAD of EDDF is correct as well, the frequencies/RWYs correspond with the data of NavDataPro.

When I am approaching the localizer (with LOC armed) the Airbus intercepts it without any problem but the localizer leads the Airbus straight down to RWY 25C (and not to RWY25R)!?!? No idea why!

I am really curious if somebody else will experience the same behaviour.

BTW
Doing the same thing with the MS Default Cessna the ILS 111.35 is leading the aircraft down to RWY 25R - as it should be.


Regards René

Hi Rene and Jeehell

I did an ILs approach, while LOC AND GLIDE were centered visual showed that Im aiming to a side of the runway, no idea why, maybe the view point of FS or something. Attached image can show what happens.

Also a pair of issues.

- Vertical revision in primary flight plan nor secondary flight plan is locked, it is not possible to set for high altitude airfields the 250kt/10000 ft constraints.

-Like the real airplane's OEB 39 "Erroneous fuel prediction in Alternate destination upon modification of a company route" happens the same! Great job !! The bad news is that this happens if the MCDU is not filled in the DIFFSRIFS order. While inserting data in the "C" format, fuel predictions are innacurate.

- Alternate flight-plan-departure-airport (primary flight plan destination airport) does not show the departures asociated when filling the alternate flight plan, instead alternate destination airport shows stars and arrivals. Alternate flight plan is not sequenced and the "enable alternate " feature will not work correctly.

Thats all by now, I will perform a pair of flights now and keep you posted.

Regards
Adonis

[romeow]

Hi Adonis all all the others,

I've completely forgotten to post that it isn't necessary anymore to test the EDDF approach I askd for few days ago. The problem is fixed and all the approaches onto EDDF are OK now. I've found several (old) AFCAD files for EDDF inside the FSX folder which caused the mess. I don't know why they were there. Probably something went wrong with the EDDF X installer.
Regards René

[jeehell]

Hello Adonis,

Regarding the mis aligned localizer, did you run the navdbapp.exe alone (FS and FMGS closed) to build the ILS database?

I'll have a look at the other issues.

Regards,
JL

[OmniAtlas]

Flying at a crz at a mach speed of .610 (couldn't climb to FL350)

Anyone know why?

Capture.jpg

[OmniAtlas]

On closer inspection it looks like I am only using an N1 of 77% on the left engine, and N1 of 80% on engine 2...why the discrepancy? Both engines are in CLB mode.

[filippoporcari]

don't know about the discrepancy...which CI did u used?
fil

[OmniAtlas]

don't know about the discrepancy...which CI did u used?
fil

I used a CI of 40...then when I couldn't climb to FL35 I changed it to 80...still had problems.

[filippoporcari]

sounds very strange: with a CI 40 u should not have mach .61 in crz but a higher mach number...
really don't know what could be wrong...never experienced anything like this.
which was the crz wind?
did u use a weather engine?
...u should be able to climb with ANY CI...btw if u were not able to climb ...u should have tried LOWERING the CI and not increasing it: the aircraft was probably not able to climb because could not reach the mach number given for the selected CI; a lower CI gives a lower speed (mach) that means a steeper climb.
regards
fil

[OmniAtlas]

I reinstalled OPUS back then, I don't know if that was the problem. I noticed the temperature was flickering back and forth between different degrees C -- I will try again with stabilize winds and temperatures. cheers.

[SSO]

Omni,

Gear up?
I had that issue a couple of times in my early FMGS flights, due to button programming issues and the lack of gear indicator up in your face