Eddie

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 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! 🙂

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

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! 😉

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!

Beautiful work!

Hi! Thank you for the suggestion, will share with the team 🙂

I'll pass your suggestions on to the team. 🙂 Hi! We've had this feedback before and we have recently resized the pilot models but I do understand they are still not large enough. Unfortunately, any larger we start running into clipping issues with the cockpit itself; instead we opted for a slight increase, at least for now.

Hi again, I assume you have tried a complete reinstall of the aircraft since then? We've attempted to reproduce the issue and what @richboy2307 has suggested already are usually the primary suspects as to why these issues arise. Unfortunately I'm not sure we can be of more help since, like you mentioned, it seems simulator-wide. I understand that is not what you want to hear however things like these have the habit of fixing themselves. If you have any other information that could be helpful in cracking down the issue, that is more than welcome. Thank you!

Hello again, Very odd. Unfortunately we haven't been able to reproduce the issue whatsoever and I'm not entirely sure what could be the cause. I would recommend reinstalling the scenery entirely as well as clearing scenery indexes. To do that locate your folder by following the path below. (MS Store) \AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes (Steam) \AppData\Roaming\Microsoft Flight Simulator\SceneryIndexes Then delete the contents inside but leave the folder intact. You can now reinstall the scenery and the indexes will rebuild on next load of FS. Make sure to also install our official GSX profile. Really hope this solves your issue! 🙂

Hi, Apologies for the late reply! I've let the team know, thank you for your report! 🙂

Hi there, Apologies for the late reply. The gates that have it will be controlled by the "sim.cfg" file which is located in inibuilds-airport-klax-losangeles\SimObjects\Landmarks\noolaero VDGS KLAX. The available Nool VDGS gates show up there. (See attached image) Thank you and hope this helps! 🙂 g(

Hello, The cabin is missing due it being a PC-exclusive enhancement-pack. This is done to optimise the aircraft for Xbox use. As for any other issues, suggestions or feedback you have regarding the aircraft, it must go through MSFS Forums. It is a Microsoft product that just happens to be made by us. They dictate what happens to the product and when/if it needs updates; which it will receive alongside the A320neov2 sometime this month (AAU3 update). Thank you!

Hi there, Can I ask one of you, or both, to provide a video/screenshot of the issue? We've tried to reproduce it and can't seem to get the same result you are referring to. Thank you!

Hello! Have you done the steps explained here? Thank you

Hello This is a known issue and will be addressed in a future update. Apologies for the inconvenience. Your patience is much appreciated! Thank you (thread moved to appropriate section)

Hello, We've tried to reproduce this but it seems we are unable to. I've attached screenshots at different gates and the marshalers seem to be fine, for us at least. This is using the most up to date version (v1.3.0) with the official GSX profile installed through the iniManager. If you have the same conditions set as us (same airport ver, official GSX etc), please attach screenshots of what it looks like for you. Thank you!