richboy2307

Hi @poganets76 good to know! Just for future reference of other users, what was the issue/solution? Thanks!

Reported, thanks!

Good to know, thanks!

I'm not noticing this on my end. Considering its working fine for you on some flights as well I'm not sure this is 100% related to the aircraft itself. Is this happening at every airport? Also are you noticing this on any other aircraft? You could try to delete the contents of this folder, so as to force a recompilation of the generated files in case something was corrupted. Steam: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a320neo MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a320neo Thanks!

Thanks, glad to hear this. Also appreciate the kind words. And wow, that's amazing! Must have been quite the experience working on these birds. Glad you can relate to the experience. Feel free to open up those cowlings in the maintenance panel of GE variant to feel even more at home 😛 (just kidding) Thanks!

Reported, thanks!

While this may make X-Plane users such as yourself unhappy, the reality is the team is currently occupied with MSFS development, fixes and optimization. Ideally we'd be able to work on both those and X-Plane products simultaneously, but we do not have unlimited resources and have to prioritize their utilization accordingly. Your patience and understanding is greatly appreciated. Thanks!

Hi, Thanks for your suggestion. There are no custom GSE used, it just calls for the default sim Ground Service Vehicles using the buttons on the EFB. So you could call for such services using the in-gam ATC menu as well if you are not using 3rd party tools like GSX. I'll check with the team if we could add a "Toggle Stairs" option as well. Thanks!

Is your sim pausing for some reason? Please double check you don't have pause or active pause assigned to a key you may be pressing. Thanks!

Thanks for your suggestion. I'll share with the team, but this is not planned currently. Also moved to the right forum section.

Yes this is detailed in the FAQ here:

Hi, sorry can you be more specific about the issue? Or link me to an older post (A300) about this? Thanks!

Thanks for your suggestion, I will share with the team however the clickspot is not likely to move. Alternatively may I suggest assigning a button/key to the 'AUTO THROTTLE TO GA' command from control options? You could also use the 'LVAR:INI_Takeoff_Toggle' if using 3rd party mapping tools. This was covered in the video here: https://youtu.be/N4cxNccH66U?t=1411 Thanks!

Thanks for your feedback. It is noted and passed on to the team.

As mentioned above, we are working on longer term art fixes on windows and wings. They will come in a planned update. Thanks!

Hi @gibbo_ireland There is a white livery included with the package that you can paint on. Releasing the paint kit however is not up to us as this is a Microsoft Product. Thanks!

Hi, Unfortunately I cannot see your posted screenshot. However feedback regarding performance is noted, and the team is working to improve on this. In the meanwhile you can try the following to improve performance: Uninstall the Enhancement Package, as this adds 4K textures as well as a passenger cabin which could cause performance issues in RAM / VRAM limited systems Set cockpit refresh rate to low (Options > Genera > Cockpit Refresh Rate) Use developer mode to open the FPS monitor. If you are seeing yellow/red indications on the MainThread, please try to reduce load on your CPU by reducing traffic, Object and Terrain LOD in settings. Thanks!

Reported, thanks!

Hi all, We are working on an A300 update 🙂 Please anyone having sudden CTD, crashing on load in etc, please report back (@ me) if you are interested to participate in test builds for this purpose. Thanks!

Hi all, We are working on an A300 update 🙂 Please anyone having sudden CTD, crashing on load in etc, please report back (@ me) if you are interested to participate in test builds for this purpose. Thanks!

Thanks, I see it on our end too. Bug report logged.

Sorry you feel this way. We continue to improve and update our products periodically, especially with performance in mind for Xbox builds. However owing to the complexity of this large airport in particular, and its vicinity to a dense populated area as well as the hardware limitations of Xbox, it is possible you will run into scenarios where you're pushing the boundaries of what it can handle (particularly when it comes to RAM) and thereby experience performance or instability issues. While we do our best to mitigate these as far as practicable, it is impossible to completely negate this whilst also offering the visual fidelity that customers have come to expect of us. Nonetheless, as on Xbox the purchases are made via in-game Marketplace, you will need to contact Microsoft/Asobo support regarding refunds. Thanks!

We'll look into publishing a list, but in the meanwhile you can do the above. Thanks!

Unfortunately not able to see your posted images. Nonetheless, we are working on longer term art fixes on windows and wings among other things. They will come in a planned update. Thanks!

Hi, are you still facing this issue as of SU 15 public release? We have not been able to successfully reproduce crash-on-load on either A310 or A300 reliably internally or through our beta testers till date so I'd recommend the following: What can you do? Troubleshooting such as : Do a flight without any other addons, or third party A310 liveries in your community folder, to see if there are other addon conflicts. (Simply rename existing 'Community' folder temporarily e.g. '_Community', sim will create a new empty one on next launch. After done testing, delete new Community folder and rename the old one back to 'Community') Delete the contents of your "work" folder after a fresh re-install to ensure no corrupted data Steam: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a310-300 MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a310-300 Make these flights in default "White" or "Inibuilds House" liveries to eliminate any "bad" livery files causing conflict And when you do encounter the issue, report with: Screenshots/Videos of the failed systems or anomalies you notice Write-up of the things you did just prior to the crash (e.g. what you clicked, what you interacted with, what control inputs you gave etc) Route information & navdata used (E.g. Navigraph data - KLAX/24R LADYJ4 CSTRO DCT DUCKE DCT LMT DCT MOXEE TMBRS2 KPDX/28L ) Any extra things you noticed just before to the crash (e.g. momentary sim-freeze, abrupt winds change, sudden weather update etc.) All this allows us to try and recreate your flight to see if we face the same issues or find common conditions across reports to try and nail the issue. Your patience and understanding is greatly appreciated. Thanks!