Der Michel

Ok, today 1.08 it's working but only in the ICE IND setting.

The HF Holding is wrong displayed in F-PLN. Example was EGKK. In this case the holding FIX "MAY" is missing. It was also missing at the ND.

This topic will cover issues with HOLDING and the example is created with SIM NAVDATA (JEP and LIDO code some procedures different, so LIDO contains the HM and JEP not). I start with the DATABASE HOLD for a GoAround-procedure EDDV-ILS09L. 1. Issue HOLDING PATTERN WITH A MANUAL TERMINATION (HM) has to consist of 2 lines in the F-PLN. The DATABASE HM is currently indicated with one line. 2. Issue The white SPD label is missing 3. Issue The HOLD R shoulnd't have a turn indication arrow. The R indicates already the turn direcion. 4. Issue Distance of 0 is missing 5. Issue When entering that existing HOLD from a non tmpy f-pln it's indicated in TMPY- mode. That's wrong, it has to be indicated in a "normal state". It will switch to TMPY mode, when anything is entered/changed. 6. Issue Top left the holding pattern type has to be DATABASE, COMPUTED or MODIFIED. In this case DATABASE as nothing was changed. 7. Issue It shouldn't read HOLD at HOLD R. It should be HOLD AT NIE in this case. 8. Issue DATABASE/COMPUTED button logic is not working correct. When pressing COMPUTED, DATABASE should get avail to be able to revert to DB values. At the same moment COMPUTED has to be unavail, because it' now computed and the top left indicates now computed. When anything is changed manually, both buttons get's avail (database of course only, if it's in the DB) and top left indicates modified. Now also a HM, but this time MANUAL HOLD (HM is the only type you can manually insert (HF and HA are only avail via NAV-DB) in F-PLN: Same issues as above issue 2 and 4,5,6,7,8 9. Issue first and second WRB point has to keep it's previous speed of 308 10. Issue When entering the HOLD via the second WRB and editing it created a second hold. shouldn't happen. 11. Issue Prior takeoff the label has to be TIME, not UTC 12. Issue For Holdings part of the active F-PLN there have to be predictions for UTC/TIME and EFOB 13. Issue (SPDLIM) shouldn't be there in F-PLN. Just teh magenta speedchagne dot at the ND. (SPDLIM) is only for altitude related speed limit. 14. Issue White has to be HOLD R and the following PAM. SPD label is missing In the second PAM line, there should be the target speed and not the repeating sign " for the altitude, but numbers 15. Issue White has to be HOLD R and the following PAM. The first PAM has still to be there as from WPT

The missing picture from sim and more points: 6. The label of teh TO-WPT has to be yellow, not white (NUDG5Z) 7. Departure is missing the rwy altitude

Ok, found a Photo. Topic can be closed. Thank you.

The question is how the tool determines the position. Contact point of the gear, Datum reference of the model? Maybe the tool has just to take into account some offset by itself.

Hi, thanks for your feedback. It' might be software version related, but not directly an airline option. I can't imagine that airbus changed the layout of that page between two software versions. I never saw the currently modeled version. Can you please check back with the devs/advisors/resource photos? Can you maybe post a picture of the ressource? I'm always willing to learn something new.

I did today a flight into Tokyo and discovered a lot of bugs, all related to LDA approach. This will be now a longer post. Let's start: 1. ARRIVAL page is missing FREQ and LS--> IKL and 110.1 2. NAVAIDS page shouldn't indicate DESELECT FLS, because there is no FLS possible for LDA. Expected is following: 3. At less then 300NM direct distance to the destination airport the FMS has to autotune the LS (see also in this post): 4. Manual tuning was not easy, first it tuned the wrong IKL (wrong freq), then it offered a list of two, and at third try it offered a list with 3, including the correct one. I would expect a list of all availabel IKL at the first try. So your database built in the backend is slow or incomplete, or something else... 5. The CLASS has to indicate the correct type. If the ILS has an DME it's ILS/DME and not just ILS: 6. Wrong landing capability was indicated at FMA. APPR1, not F-APP for LOC-FPA 7. FPA was missing the angel at FMA: -3.0°

Ok, will try it that way...thanks.

@richboy2307 or @haza2 anything you can do in regards to the quota?

@Eddie I need your help. I have a problem with the forum, because I reached my quota for attachments. Please, is there a option to rise the limit for me, else I can't report any more issues.

After inserting a departure it should be ERASE TMPY* and not UNDO* The departure RWY shouldn't have a diamond at the right The lines top, left and below of the TO-WPT diamond should be also yellow in TMPY mode The TRK and DIST for the TO WPT, should be also yellow in TMPY mode the dashes at the bottom should be also yellow in TMPY mode

the shouldn't be units behind LENGTH and CRS EOSID has to be dashed, as long as no RWY is selceted If a RWY has ILS it has to be indicated in the RWY dropdown selection after selection of RWY, the FREQ/CHAN has to be prefilled with ILS FREQ SID drop down menu has to offer up to 12 entries, prio scroll requirement If NONE SID is selcted, the default leg should be a VA-leg and not CA, and should be 1500ft above ground (THR alt + 1500)

A picture of the default display ALIGN ON REF:

There shouldn't be any red area or white marks, with FADEC off.

The upper part (Engine) should have a different layout:

There should be a gap between the value and the unit for: CRZ TEMP and TROPO RTE SEL and ALTN RTE SEL have to be greyed out as long as no FROM/TO is defined. As soon as FROM/TO is defined, the TRIP WIND has to default to TL000

That's my understanding from what I read in the forum. You are not the first who is asking.

Hi, have you tried this? Please report any WASM crash (freeze of avionics) according following, only then they can track and solve it:

it was disabled for 1.08. There will be a new OIS option in the next update. There was a lag during apporach, when the map was not preloaded.

@Eddie is this also tracked/forwarded?

@Eddie is this also tracked/forwarded?

@Eddie is this also tracked/forwarded?

@Eddie is this also tracked/forwarded?

@Eddie is this also tracked/forwarded?