WernerAir

Hi there, thanks for a very nice scenery. Just one thing I have stumbled across: no matter what I do, I can't get a jetway to move at any of the gate positions at Terminal 3. I have tried different aircraft (A32nx, A310, B747), and I have also tried repositioning the aircraft along the yellow line, but without any results. Is anyone else also having this problem?

I had the same problem yesterday. I finally got it to work by removing the scenery through the iniManager and then installing it again. Seems like something is not always downloaded correctly.

I just tried again, and it's working for me again now.

Same here.

Hey, 'I am having the exact same problem. I guess I can stop rebooting my PC then... Must be something on the server side - the app worked fine yesterday evening.

Nice idea, @FelixM. Unfortunately I just had no success testing it - flight from SEQM to SPJC, Cruise level 350, max 399, opt 391. Step climb set to FL 370 - so way below both max and opt. As usual, P.Clb flashes in blue for a few seconds, then disappears. No climb until I initiate it manually. So I have to agree with @gumbyger that this is probably not the issue.

OK, here is the first test of the day: I am flying from LMML to EGKK - attached you will find the SimBrief flight plan I am using. The flight plan calls for an initial climb to FL300, and then a first step climb to FL360 soon after at waypoint ADEXI. Later, a second step climb to FL380 is foreseen at PIGOS. I have made three screen videos, which you will find here: https://c.1und1.de/@520185075732578887/EAJQA_mMQUCq9bNjMOWpMQ The first video shows me setting up the first step climb shortly after reaching the initial cruise alt of FL300. Here, everything behaves as expected. The second video shows the moment when the aircraft reaches ADEXI. As you can see, the aircraft just doesn't climb, and the step climb somehow remains pending in the FMS. I wouldn't call the turn at ADEXI a sharp one. The third video shows another curiosity, which is me trying to set up a second step climb. This should not be possible according to the video cited above. Nevertheless, the FMC let's me insert the step climb, but then behaves strangely with the (S/C) appearing and disappearing at intervals. The videos do not require a password to access, and they will be online for a month from now. I hope this helps understanding the problem - and maybe finding the cause. LMMLEGKK01.fpl

The LNAV path has been pretty straight in all instances I have tried so far. I am going to start a flight just now, and try to document it more precisely.

Hi there, I wanted to ask whether the FMS-assisted step climb functionality is fully implemented in the MSFS version. Because I have not been able to get it to work. Several times now I have set up the step climb as described in this video: https://www.youtube.com/watch?v=TQgv0VZAKGM&list=PLzeFYXw62MgZTxwGc-ogOuIlx8o5HdsK3&index=2 - of course the video refers to the X-Plane version of the A310, but behavior of the FMC is as described, and the S/C point is also shown on the ND. When approaching the S/C point, the FMA "P.Climb" even starts to blink in blue under "P.Alt". So everything as expected so far. However, once the aircraft reaches the S/C point, instead of engaging P.Climb it just remains in P.Alt at the current altitude. The aircraft only starts climbing after pulling the altitude selection knob manually. Is this a bug, or am I doing something wrong?

So I have been trying, but so far I have not been able to reproduce the issue, even on longer flights where I have had a secondary flight plan loaded and spent some time playing around with the FMC. I have found out that I am not sure whether step climbs are working as they should, but regarding the systems freeze there are no news. I guess this is in itself a piece of good news...

I guess the first important thing is learning that this is not something that is just happening to me (i.e. something I did wrong), but there actually seems to be a bug somewhere. Now it's up to us to narrow it down... Unfortunately I cannot contribute to that today, but the good news is I did a flight earlier from GCXO to LIPZ (roughly 4 hours, give or take) and everything worked as it should. The one thing I decidedly did not do today was copy the active flight plan as secondary. I also played around with the FMC a bit less during the flight, so I guess the only thing I can say for sure is that the freeze doesn't always happen.

Hi there, I would like to report that I have had the same issue twice in the last two days. I cannot yet say what exactly needs to happen to reproduce it, but here is what I have observed so far: In both cases, it happened several hours into the flight, nearing TOD. Yesterday it was a flight from LIRF to HUEN, today it was LSZH to GCTS For contrast, last weel I did a flight from EDDH to KBOS where this did not happen - I don't think there was an update to the A310 in the meantime In both cases where it happened, I was fidgeting around with the FMC. In both cases I think it happened right after I pressed one of the keys to the right of the display. Yesterday I don't remember what page I was on, but today I was on the FLTPLN page and wanted to set a lower altitude constraint for one of the upcoming waypoints. I did not try to activate the secondary flight plan (in fact I haven't yet found out how to do that), but today I had copied the primary flight plan - I am not sure whether I had done that yesterday. The effect in both ocurrences was that no cockpit dial, button or switch could be used anymore. The aircraft continued flying, although its capability to hold altitude deteriorated. I "solved" the issue by saving the flight, going back to the menu and then loading the flight I had saved. This is not too god a workaround though - I could continue the flight afterwards, but I had to reconfigure most of the aircraft after reloading and also reprogram the FMC. In addition, although I could complete the flights in both cases I had the feeling that the aircraft was rather hard to fly manually in the final approach later, requiring strong aileron inputs to keep it on runway course. Especially the landing in HUEN was not much fun... Anyway, I hope this account helps to narrow it down, and in any case I wanted to make it known that this seems not to be an isolated incident. I will continue observing what makes this reproducible (and it may be the secondary flight plan), but there seems to be an issue somewhere and I would venture to say it's connected to the FMC. Nevertheless, congratulations for an otherwise pretty neat airplane - and thank you for providing it!