WernerAir

The problem has been solved by deleting the iniManager Appdata folder in Windows - which solved my other problem with the stuck wishlist as well.

Hi Eddie, thanks for the tip - I now got it working again, and access to the liveries is also working now. The only downside is that I had to redo my settings - especially the quite extensive list of rwProfiles GSX profiles I have installed. Maybe it would be possible to save this separately... Anyway, the important point is that my problem has been solved.

My INIManager version is up to date (sorry - don't have the version number on me right now). Ever since the update that introduced MSFS2024 support, aircraft liveries are not accessible. Sometimes the menu page is completely blank, sometimes the page shows up (including the new MSFS2024 aircraft), but I can't actually click on anything. Is this a known problem?

I had KIAD on my wishlist when all BM World and AMSim products were removed from the shop, leaving a blank entry on my wishlist that I can't remove. What is worse: any other product I put on the wishlist since then also shows up as a blank entry, rendering my wishlist basically useless. Is there anything I (or you) can do to remedy the situation?

So, here is the analysis after the release of AAU3. For the A320 neo V2, I find it much improved. There is a reference to a "fixed jetway alignment" in the release notes, and indeed the angle at which the jetway meets the fuselage corresponds better to the actual airframe contour, as can be seen in the screenshot below. It's not perfect, I would say - in fact, I think it's a little bit open towards the front now, so if I had access to the corresponding config files I would try to tweak it some more by turning it back a little bit. But as I said, I find it much better than it was before. I also tested the A310, but unfortunately I see no difference there - to be fair, there was nothing about it in the release notes, so it is probably unchanged. As a summary, the A320 is much better now - thank you! For the A310, I would encourage a little optimisation as well. Maybe this can be addressed as part of the upgrade for MSFS24?

Hi Eddie, thank you for checking! On the A310 my feeling is the gap is bigger on my system than it is on yours - but I'm glad that you could at least partly reproduce that. Of course as a next step I will wait for AAU3 to be released to see if it changes anything. If not, I guess it will be difficult to find out what exactly is different on my system that is causing this issue. The only thing I can think of is the graphics card / graphics driver, because I have already come across issues like this where jetway animations work differently depending on whether you're running an AMD or a nVidia driver. I am running a nVidia Geforce RTX 4070 TI, and my driver is up to date, but in the past nVidia has seemed to cause more difficulties. Is it possible you are running the sim on an AMD card? Regardless of this however, changing the graphics settings (e.g. turning off DLSS) has had no noticeable impact so far. So I honestly wouldn't know where to start... Is there perhaps a way to put a model.cfg file somewhere to play around with the aircraft interfaces even if it is a plane installed through the MSFS marketplace?

OK, It has taken a while, but I have done a test series at Inibuilds EGLL gate 221. GSX was completely turned off, i.e. I stopped the couatl engine. The procedure was always the same: - load a new aircraft from the main menu - turn on batteries and external power - open the ATC menu and request ground services - request jetway connection - observe the result through external view and drone cam positioned on the tarmac under the main door - make a screenshot of the result I tested for the following aircraft: - Asobo default A320neo - FlyByWire A320nx - Inibuilds A320neo V2 * (here I had to toggle the jetway through the EFB, as the ATC menu did not give me the option somehow) - Inibuilds A310-300 - Asobo B787-10 The first two screenshots show a general overview at the gate. The subsequent screenshots show the resulting jetway position at the door for the aircraft in the order listed above. As you can see, the positioning generally looks good, except for the two Inibuilds aircraft. All sim and graphics settings are the same in all cases, and as stated GSX is not active. Results are reproducible if I toggle the jetway several times. So, any ideas what could be the cause?

Hi Eddie, thank you for your efforts. Yes, so far I have encountered this issue only on the Inibuilds A310 and A320 V2. I have done some additional testing at Inibuilds EGLL, gate 224, and it is completely reproducible, no matter the method for moving the jetway or the graphics settings or any other thing I have tried to change. (in the past I have observed some strange interactions between jetway animations and Nvidia graphics drivers, for example, but that doesn't seem to be the case here, as I tried the same on the FlyByWire A320nx and the jetway docks fine there). I was sure you would be able to reproduce the issue. Since you haven't been, I will do some more systematic testing and produce screenshots and videos - maybe that will give us a clue as to what is going on. It will take a few days before I can do that, though... If AAU3 is released in the meantime, maybe it will help. But I am not so sure about that.

Hi Eddie, thank you for your reply. Yes, I use GSX - sorry for not mentioning that. I am pretty sure it has nothing to do with the aircraft profiles, because I have tried with different profiles (I am using the standard one as it is), and I have also tried to edit the door definitions in the profile manually. What I have observed is that the door definition in the GSX profile changes how any GSX stairs dock at the aircraft, but it seems to have no influence on the jetways. It seems to me that the standard MSFS animation is used here, and this should be driven by the model.cfg file. In addition, I have also tried to dock jetways via the EFB and via the comms menu (i.e. without activating GSX), and the result is the same. It's pretty much the same experience I made when I tried to improve the jetway docking on the A310. I hope this helps... And yes, I am looking forward to AAU3 very much!

Hi there, I have noticed something that should be easy to fix, but I find it pretty annoying. Jetways on the A320neo V2 seem to dock at a strange angle to the fuselage - see the attached screenshots for reference. I have observed this behaviour at many different airports, so my guess is that it probably requires some tweaking of the model.cfg file - unfortunately I cannot access that file, as this is a MSFS marketplace install and it seems to be in the encrypted part. Could you please consider this for the coming update? By the way: The A310-300 exhibits similar behaviour, though there the jetway is usually skewed in the other direction. It would be great if this could also be fixed... Thanks for an otherwise great aircraft!

Yes, now it loaded. Thanks!

Nope, still not working for me. Hasn't worked all day.

Actually, I am not sure the NAV radio autotune function is doing what it should. I have done a handful of flights in the last couple of days, and while the ILS frequency for the departing airport was always automatically selected in the FMS RAD/NAV page, I have always had to set the landing ILS frequency manually (I have been up to almost intercepting the localizer and still the autotune wouldn't set the landing ILS). The correct approach and runway where always selected in route planning - I usually do that before take-off. Just typing in the Identifier from the ILS chart always set the correct frequency and course, though. Right now I am flying from BIKF to LFMN, and I am noticing something else which is strange and might be related. Consider the two screenshots below: I am 48 miles out from STN VOR in northern Scotland, and the NAV radio autotune has selected SOY (the Rwy 36 localizer frequency) for Stornoway airport for both NAV 1 and NAV 2. Why doesn't it tune in STN VOR? Why does it tune in localizer frequencies on the NAV radios at all? Also note on the second screenshot that the Rwy 19 ILS from BIKF (i.e. departing airport) is still selected under ILS, even though departure is more than an hour past. I don't know when the ILS frequency is supposed to updatge, however.

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!