Jehudale

Hi @Sam, yesterday I had the same. Updateing A310 - worked. Updating A300 (which indicated version 2.07): Downloaded some MB, installed something, still 2.07. Closing app, retrying: Same. Starting XPLane (just main menu), closing it, trying again: worked. I don't know if the start of xplane hat something to do with it but mostly I need three downloads. Magical number....

Hi @Sam, Quote "Just to make sure I understood correctly, after clicking update, the download completed, but it still showed update available within the iniManager, is that correct?" yes, exactly. Unfortuneately I did not recognize if the version number circled in between the updates so I can't tell.

This has bern answered a few times and is well explained in the videos on the inibuilds youtube channel.

I experienced a few times that multiple downloads are needed. It says there is an update, it downloads something, and then without error it finishes and says there is an update. But after a few tries it worked so I never reported that. But yesterday there I recognized something you guys should know, meybe it helps with the problems others have: My A300 was at version 2.02 but worked so far so I didn't update yet. But after also an update for the A310 was avail I decidded to update both. Startting with the A310 it downloadded about 70 MB, instaled it and the plane was up to date. Next I started the update for the A300. It downloaded 1,9 GB, did a lot of copy and install and still said there is an update avail. So I started it again, same result. I closed the ini manager and tried again, same result. After the fourth download (1,9 GB*4!!) the update was finished. Interesting thing about it: I was four versions behind the actual one as far as I know and I needed four complete downloads. Just an idea. Anyway most of the times it takes more than one download, I was suprised the A310 updated in the first pass. Maybe the user should get some more feedback from the app in case of an error. That would also help you in supporting. It just runs the same task a few times and as a user I wonder what it is doing and what failed...

Do not run it while X-Plane is running.

Evtl. gibt es keine ATIS im Onlinenetzwerk für den Flughafen zu der Zeit. Du kannst die Daten auch manuell eingeben. Die ATIS kannst DU abhören über Funk oder auf der Minimap von XP nach Anklicken des Flughafens einsehen. Ansonsten versuche alternativ über CPDLC die METAR des Flughafens abzurufen, die geht in den meisten Fällen. Dann ausdrucken, anheften und die Daten ebenfalls manuell eingeben.

To me that happened onlz on descends so far, when I used FLC before that. Than it sticks to the manual dialed speed instead of the FMS speed, mostlz because teh selected speed is in mach and it wants to hunt that at lower levels. Mz workaround in that case is to go FLC, dial in a slow speed until it gets to knots instead of Mach, dial it up again to 270 and re/engage profile mode. That helped always. It never heppened to me after takeoff as far as I can remember.

Looks like it is related to what I have posted

Oops, I guess the PW engine has less fuel burn. There must be a reason that the later A310 were more build with the PW eninges (source: Airbus A310 | Aircraft Wiki | Fandom)

Of course you might. A "double" typo error, should have been TOC (Top of climb) but in that case it also fits for BOD (Bottom of descend) 😄

Additional note: If you missed TOD do step 1+2, then press profile to re-arm profile and the plane also goes into P.DESC mode.

Steps to follow BEFORE reaching TOD: 1.) Set the descend altitude 2.) Pull the knob to arm it, P.DESC is shown in blue below P.ALT When reaching TOD the plane will descent.

Blue=BOC, white=TOD

800-1000 ft/min at the final or the whole approach? Maybe it is also triggered when to fast, i only know it from steep appraoches or cominh in to steep on manual approach. BTW 160 knots with full flaps sounds wrong to me, even when fully loaded. The highest approach speed I got in the past was about 146 or 148 with full load. Maybe that is the reason.

It usually goes on by itself when the apporach is to steep, mostly preceeded by a "caution terrain" warning. Does not happen on 3 degrees approaches when no terrain collision may occur.