Eddie

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!

The X is just an identifier to whatever livery you wish to delete. I don't know what liveries you want to remove/keep ;).

Hello, Like jankees said, that'll get rid of them showing up in the simulator indeed. aircraft.cfg is located at inibuilds-aircraft-t33/SimObjects/Airplanes/inibuilds-aircraft-t33 If you'd like to physically remove the default liveries too, you can delete the "texture.X" folders for each livery. Make sure you don't accidentally delete any base texture-folders (texture, texture.ext, texture.gse, texture.int). Thank you!

Hello! I'll pass your suggestion on to the team, but as per usual, cannot promise anything ;). Thank you!

Hello, Apologies for the delayed reply. You'll find more luck contacting XwindStudios directly as it is their product. You can find their Facebook here: https://www.facebook.com/people/XWind-Studios/100093480376430/?_rdr Alternatively, perhaps @XWind Studios can reply directly here 🙂 Thank you!

Lovely! Glad to hear 🙂 Enjoy!

Hello everyone, I've shared your reports with the team and we'll get back to you once we have more information to provide. Apologies for the inconvenience and we appreciate your patience! Thank you

Hello again, I understand. Very odd. We attempted to reproduce the issue however been unsuccessful on multiple occasions. Jetways align almost perfectly on each test we did (image attached). Is it only the 320N & A310 that you experience said issues with? No other airliners? I would suggest waiting until AAU3 is released and perhaps it resolves the issue. I've attached screenshots and this is us using the latest (non-public build). No issue. Thank you!

Hi Werner! I see that you're using GSX, could you please double check your profiles and the door definitions for said profiles? GSX natively supports the 32N; remove any custom profiles (if any are installed) and try again. And I'm glad you're enjoying the aircraft, upcoming AAU3 update should make it even better! 😊 Thank you

Hello! Sorry to hear you're experiencing issues! Please uninstall the scenery entirely and clear your 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. (The indexs will rebuild on next load of FS) Reinstall the scenery. This should solve the issue. Thank you!

Hello I'll pass the suggestion on to the team, but no promises! 😉 Thank you!

Hello! Thank you for your report. I'll share it with the team to see if there's anything that can be done on our end, however by the looks of it, it seems unlikely. I recommend reaching out to MS via their forums or Zendesk for further support as this issue stems from the default ATC. Thank you!

Hi! Glad its sorted for you 🙂 I'll mark it solved. Thanks!

Hi again, Non-caster steering is intentional due to the T-33 requiring differential braking to steer. Glad you resolved the wheel brake issue! We have logged the problem regarding the speed brakes. 😊

Hello, Happy to hear it's solved! Enjoy! 🙂

Hello, I'll pass this on to the team. Thanks!