Der Michel

Hi iniTeam, I would really appreciate it, if you could answer the question, what FMGEC System Version you are implementing in this addon. Shouldn't be to complicate to answer. THANK YOU! a) FMS2 HONEYWELL P2 b) FMS2 HONEYWELL P3 c) FMS2 HONEYWELL Release 1A P4 d) FMS2 HONEYWELL Release 2 P5A e) FMS2 THALES Rev 2+ T2 f) FMS2 THALES Release 1A T3 g) FMS2 THALES Release 1A T4 h) FMS2 THALES Release 1A T5B i) FMS2 THALES Release 2 T6A

Hello ini Team, @Eddie, @iniSteven, I have no idea what you are doing. Please, tell us what is the version of the FMS you try to implement? With 1.02 you downgraded the IRS INIT to HONEYWELL P3. Now you implement an OFFSET version of HONEYWELL P4. Some of my reports are based on the assumption you do P3, but if it’s now P4… So, what is it now? left P3 / right P4

It's an old FMS2 HONEYWELL P3 version. Not the FMS2 HONEYWELL Release 1A P4 or even newest FMS2 HONEYWELL Release 2 P5. So the answer is no.

Found another refference for the case of LINE 2 has a DISCO: - NM is then in LINE 4, as leg distance between Line 3 and 4. - The current display of leg distance between line 1 and 3 in line 3 is wrong! - also line 3 shouldn't display a TRK

@Eddie this issue is also relevant for the A350 and all other Airbus ini has done so far. The last two pictures of my post clearly indicates the still long way ini has to go with its FMS.

Update: The Problem is the 4 character WPT. A 5 character WPT was working flawless.

RJTT LDA22Y: MX22 is the hardcoded MAP of that approach. Now the systems displays several items wrong. 1. There is no RWY-Waypoint coded in the NAVDATABASE for that approach, because the MAP is prior the Runway. So DON'T display a RWY-Waypoint in the F-PLN !! 2. The blue track line has to start at MX22, because that's the MAP ! So the INTCPT Heading of 208° has to be drawn blue from MX22, resulting in a different INCTP position with the CF leg (178°) to UTIBO. 3. If the GA is not displayed, then there is just blank between MX22 and RWY. NO green line. 4. The WPT-name "INTCPT" has to be drawn green (also the diamond) on ND. 5. That is not related to LDA, but to all non Precission Approches with the MAP prior Rwy. 6. In the expected is the FIX INFO REF (green RJTT22 ) included, that is currently also not drawn (reported in other topic). 7. In the expexted is also a proper ALTN departure setting included (RJTT22 as departure), currently not possibel in iniAirbus, also reported. EXPECTED picture:

The RJBB24R SOVRI1 Departure is a RNAV SID. In the NAVDATABASE the complete SID has a hardcoded RNP of 0.1 NM. The currently indicated 1.00 is wrong. So you need to read what is in the DB and dispaly it. Please fix that!

1. I expect a right turn at "500" and then to MUMSU - MIMIG - ... The DF leg between "500" and "MUMSU" is hardcoded as right turn in the NAVDATABASE....so you just need to drawwhat is coded. Please correct this ! RJBB24R - SOVRI1 2. You indicate the turn arrow in the F-PLN next to MUMSU. That's wrong! The Leg starts at "500" and the arrow indicate the pilot the turn direction he has to fly. So the arrow has to be displayed at 500 in the FPLN. Yes, the turn is coded in the DF leg and the F-PLN is representing that entry with the WPT MUMSU, but still the arrow has to be indicated next to 500 !! Bellow is a real world example (Yes, a modern Thales, but the same for the old Honeywell!). In the NAVDB the turn is there coded in the DF leg to GIMAL. But the arrow is indicated next to the "2000" of FA leg. 3. As already reported, don't show the magenta value of VA, CA and FA legs on F-PLN or ND !!! EXPECTED picture:

FIX Info doesn't accept a WPT entry. It looks like it just accepts Airports. That's wrong!

The already selected RWY has to be green without selection arrow (line 5 in this case)

The screenshot says it all… I was flying at up to 4x sim rate. I left the PC to eat, and when I came back… voilà. Also the FMS wasn't reacting anymore. The cursor was also slow on the displays. EDDM/26L N0480F380 INPU2S INPUD Y102 ALIBU L604 RELBI L602 SUPUR P1 GODOS M981 NATEB N97 TLA DCT AMCON/N0462F240 N562 MIMKU/N0486F380 DCT PIGET DCT PIKIL/M085F390 DCT 57N020W 57N030W 57N040W 56N050W DCT JANJO/N0493F400 N710B TAFFY DCT KJOHN DCT HANAA FLOSI4 KEWR/22R

I would expect: FMA: DISCONNECT AP FOR LDG at Minimum -50 ft (if entered) or at 400 ft AGL (if no minimum is entered) with the AP/FD remains engaged. or automatic DISCONNECTION of the AP at Minimum -50 ft (if entered) or at 400 ft AGL (if no minimum is entered). But currently we don't have the FMA message and the AP stays connected. So you need to decide what to implement. Depends on the version of the FGE you model. FGE HJ1A would be first case, FGE B9 would be second case for example.

A manual leg should be followed by DISCO.

In flight the System lost predictions. Might be caused by high north route: EFHK/22L N0472F320 DCT TEVRU Y75 OSKEK DCT GODOB DCT ENOXI DCT RIXEM P853 TRO/N0478F310 P600 INPAR/M083F320 DCT 83N005E 87N037W/N0477F340 85N124W 80N141W/N0475F350 75N146W DCT SCC/N0471F360 DCT SCC/N0472F370 Q41 CAWIN J115 TED/N0475F380 J125 ODK/N0476F370 DCT 52N154W/N0466F390 DCT 47N55 DCT 41N55 DCT 35N156W 30N157W DCT ZIGIE/N0469F400 DCT ZIGIE INOYI1 PHNL/04L Departure Time 08:25 UTC

It might be a limitation of the FSM, that it can't do CAT 3 while TRUE NORTH selected.

Erase should have an <- not *

I would expect a CTL behind the station id.

1.04 Happened again.... Some switching EFIS ND mode back and forth, and then they appeared after some time again. And gone again... Please fix that. EFHK/22L DCT TEVRU Y75 OSKEK DCT GODOB DCT ENOXI DCT RIXEM P853 TRO P600 INPAR DCT 83N005E 87N037W 85N124W 80N141W 75N146W DCT SCC DCT SCC Q41 CAWIN J115 TED J125 ODK DCT 52N154W DCT 47N55 DCT 41N55 DCT 35N156W 30N157W DCT ZIGIE DCT ZIGIE INOYI1 PHNL/04L

1.04 I have no idea what you are doing. You added now the COMPUTED HOLD at titel. But your COMPUTED LSK1R and DATABASE LSK2R are THALES design. You are doing a HONEYWELL FMS. Again you touched only a small item of the page. Why are you not correcting all in one step? Please, fix it!

1.04 LSK5R is missing FUEL TIME with dashes below ---.- ---- LSK5R is missing FUEL TIME with NO OPTIMAL below

1.04 still open

@Eddie it's not fixed as promised. I suggest let the topics open until fix is confirmed! You missed two items: - EFOB and EXTRA for VERT REV of Destiantion are not matching FUEL PRED/INIT B during preflight - LSK2R is missing RTA> (at least greyed inop entry)

1.04: Still the same issues. This topic and the other one:

1.04 still open