richboy2307

Hi, thanks the team is aware of this and investigating. Appears to be random, as it will work some flights and not on others.

Thanks for your report, shared with the team for further investigation.

Thanks, reported to the team and we're looking into it.

HI @skydiver6547 I have my throttles mapped to bravo throttle quadrant. I set the throttle axis to IDLE, used F2 to engage reversers, then move the throttle axis levers forward and am able to go into FWD thrust immediately. Please try to reset your calibration. If that doesn't work, check your Throttledata.ini file from the locations below. Ensure that the "reverse_on_axis = false" is seen. Steam: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a310-300\work MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a310-300\work Thanks!

As answered via discord post, "Its an issue of lack of reconciliation between CFD Flight Model and the sim's event logger (likely designed for the older flight models). In any case, its for MS/Asobo to address. It is not up to us to be fixed and should be reported to ZenDesk as Asobo will need to make changes to the core of the sim to reflect the CFD flight model" Thanks!

Hi, The 'Enhanced' package adds 4K textures, passenger cabin and dynamic seat-back cabin screens. It should have no effect on the aircraft's systems itself. It is also not mandatory to use this package and the A310 will work functionally the same without it. So what you are noticing are probably just bugs in general, not specific to the enhanced package. That is noted, the F4 (Full Throttle) command does not work currently. Are you talking about when you are flying? This is the correct logic and how it is in real life. . When either condition listed below is no longer true, the lights will automatically turn off. That is noted, there aren't any touchdown sounds simulated currently. There is a difference in the sounds, and is most noticeable in front and besides the aircraft. But feedback is noted, thanks! The way it is currently modelled this allows you to still maintain IDLE REV, but feedback is noted, thanks!

Thanks for the video and additional reports. We're looking into it.

Hi, are y'all using any scenery for LFSB as well? I have just flown a flight with the route below, once in GE F and once with PW Pax, with Navigraph Navdata (2405 rev.1) on SU15, with v1.1.1 of the A300 without any crashing issues. LSGG/04 N0473F300 MOLU4N MOLUS N871 KONOL Z59 LUMEL LUME8K LFSB/15 This is with a near empty community folder, no sceneries used for either airport. Not getting any WASM crashes throughout the route, even tried to change the STAR/APPROACH procedures multiples time in the air, whilst in a hold, from ILSZ15 to ILSY15 to ILSX33 to ILSY15, no crashes, and MCDU has changed the procs appropriately. In any case, we do have a new update for the A300 which will hopefully address the issues you are facing. Enclosed is a post shared on our discord. Please try that update (once available) and do report back if you still face such issues. Thanks!

Thanks for the reports guys, but as KSFO is a BMWorld & AmSim product, best to contact them directly (linked social) with bug reports and suggestions as they may not be monitoring our forums.

Reported, thanks!

Thanks for your question. I've shared with the team for a more detailed response of what the EFB is doing. But meanwhile, yes ideally all bearings used should be same (both Magnetic or both True) when making calculations. So you could make the adjustment by entering TRUE bearing for the runway, or by adjusting the reported True METAR wind bearing by MAGVAR. Thanks!

Thanks for the update. As noted here, we're working on it:

Hi @TJC Its on the wishlist for a future update of the scenery. However as you will note, we haven't yet gotten around to another version of NZQN, so we hope to address it whenever we are working on it next. Thanks!

Hi @JayJay3692 Thanks for your post. Can you ensure you have have enabled the 'RUDDER CONTROLS TILLER` option in the EFB (Options Page)? As without that option, if the user (or AI) is giving input on the rudder axis, it may not turn the tiller (thereby nosehweel) enough to allow for proper steering. That being said, the A320neo(V2) is designed and tested specifically to work best without assists, as the whole idea behind it was to offer a more advanced version of the aircraft by comparison to the Asobo (V1) one. Thanks!

Yes, as noted by Josh on discord, the team is looking into the performance issues. As mentioned there, the performance issues currently seem confined to specific type of systems, and such issues were not noticed nor reported throughout testing internally, or in the SU15beta period where users had access to this plane and versions thereof for multiple weeks. As the products have to work on Xbox, performance and optimization is a key focus throughout the development process and we will continue to improve the product in that aspect as far as practicable. Appreciate your patience and understanding on the matter. Thanks!

Hi thanks for your suggestion. I'll share with the team to see what can be done.

Thanks for the suggestion. I'll share with the team.

Can't say I'm noticing this on our end, unless again the PG data has not completely downloaded. I'll share with the team anyways to see if anything can be done. Thanks!

Hi @Joc You can setup custom camera views to your liking. See this link for example how to setup. You can also use the in-game camera from the toolbar on the top to adjust things like zoom level. Thanks!

Good to know thanks.

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

Reported, thanks!

Good to know, thanks!

Hi, I believe direct support has resolved this. The solution is to update to the latest version of iniManager and reinstall. Thanks!