Eddie

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!

Beautiful work!

Hi again, For future reference, please chat only in English so that it is accessible for the rest of the community. Thank you for your understanding 😄 The A350 will ONLY be available for MSFS2024, not MSFS2020. Thank you!

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

Hi there, are you using a 3rd party scenery add-ons for MMGL and other airports you may have said issues at?

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(