Eddie

Lovely shot! How you liking the switch so far? 😊

Would you mind trying to reproduce the issue with an empty community folder (to rule out any potential conflicts)? You don't need to uninstall all your add-ons. Simply rename the existing community folder to _community temporarily. Create a new empty Community folder in its place and only put the A300 in it. Alternatively reinstall the A300 if you haven't already. If this doesn't end up resolving it, I'm afraid we're limited on what we can offer help-wise. I've tried a few times now to reproduce but just can't get the same result unfortunately. Apologies for the inconvenience! Thank you

Hi! I've let the team know. Does indeed look like an ND drawing issue. Thank you for the report! 🙂

Hello, What you're getting at does indeed make sense. I've let the team know. Thank you! 🙂

Hello, Unfortunately that is not possible, no.

Hi and apologies for the delayed reply! We are unfortunately unable to reproduce the issue on our end. I suggest waiting until AAU3 is released as that may resolve your issue! If not, you are welcome to come back here and let us know 🙂 Thank you

Hello, Apologies for the delayed reply. I have followed your steps to the tea (as well as disabling GSX) and still unable to reproduce, at least not to your level. Observing the A310 jetway-connection, there is indeed a gap similar to yours, however, it is not major at all and the overhead protection still connects seamlessly so I believe this is fine, as far as I can tell. As for the A320, it seems to connect perfectly and nowhere near the results your screenshots show. Albeit the version I'm using is the latest build of the 32Nv2. I don't see how that could be a factor, but it still could, so I would wait with that one and urge you to check again once it releases to the public; hopefully sometime this month (MS said a September release for AAU3 if I do not recall incorrectly). Anyway, apologies for the inconvenience and I do hope it will be resolved for you sooner rather than later. Thank you!

Hello again, I understand, I believe in this case this is relating to the issue discussed here: TL;DR:

Hello again, I double checked today again and still unable to reproduce. Very odd that this behaviour is only recorded at one single airport. Either way, my suggestion is for you to clear your "work" folder. Delete the contents of it and try again. A300 Steam: %APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a300-600 MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a300-600 Let me know if this solves it! Thank you

Hello, Try reseting your calibration entirely. If you change the REVERSE ON AXIS option (to yes or no) it will force reset the calibration, so you can start the process again. Then use the below guidance on calibration

My pleasure. Good luck! 🙂

Hi! We unfortunately know as much about the new cloud service as you do. Nothing we can comment on for now. We will of course share our plans once we know more about it! 😊 Thank you!

Hello, We've forwarded this to them. Thank you for letting us know!

Hi there, I've done some testing, just to confirm, when flying to this airport, are you having any issues in other aircraft? I've tried reproducing and I am indeed getting the same problem. Tried on default A320neo, the Neov2 & the 787. This leads me to believe that the airport itself is missing data, and this could be the case for other airports in Mexico as well. But please confirm whether or not this issue persists in other aircraft. You can also give this a read as its a similar issue where we've relied with potential solutions: Thank you and apologies for the inconvenience!

Hello I understand your frustration. Unfortunately, we haven't been able to reproduce, as mentioned. We are not having said issue and I can't find similar reports made recently; that makes it really hard to figure out exactly where it's going wrong. Things such as these to tend to resolve themselves, and I hope sooner than later. Again, apologies for the inconvenience. Will reach out here again if I have any updated information! Thank you

Hi again, I'll take a look tomorrow and see if I can reproduce the issue. Will get back to you with the result! 🙂

Very odd. I'll look into it further and get back to you soon.

Hi there, I've just tried loading in on most gates at EICK and chocks appear just fine. Are you using a specific scenery? Any other details are appreciated too! 🙂 (Gate number, etc)

Definitely not fun to keep doing, but unfortunately I personally have idea if there are any alternative solutions, at least for now. Hoping MS fixes this soon 🙂

Hello, Currently it's not steerable on the ground using rudder/steering inputs when stationary, but it isn't fully free-castering either as it's real-life counterpart, in that it will respond to rudder inputs when you're taxiing.

Interesting. Glad it's sorted for you regardless. Will look into this, thanks for the information! 😉

Hi! EDDG should receive the update through the iniManager later today. Apologies for the inconvenience! As for the PrealSoft Berlin landmarks, we will reach out to them for an update. Thank you for your patience!

No worries at all! Just letting you know :). If someone has the same question, they would just have to search the forum and find your post, that is why it's important we keep the forums in English. Thank you 🙂

Hello, I've reported this to the team as it does seem to be a bug. Thank you for letting us know!

Hi! As always, your insight and suggestions are always appreciated. I can't comment on further decisions we'll be making regarding the aircraft but I will raise the suggestion with the team regardless. As always, no promises 😉 Thank you!