richboy2307

Hi, could you please elaborate on this one? What is broken about it? It would also help if you could include a screenshot of what you're noticing. As a note, some of the gyro instruments, like the Artificial Horizon wouldn't work properly if the INVERTER is not switched on. This switch is towards the bottom right corner of the front panel. We have flown the plane for extensive periods, point A-B flights even for periods longer than 30 minutes without any reported CTD issues by testers, or observed internally. So this is most likely something specific to your simulator, either configuration or some other addons causing issues (such as SimFX). Can you try the following, to rule out any other conflicting addons? As for the fuselage tank switch, FUSE: The fuselage tank booster pump (electrically driven) is turned ON to supply fuel to the engine under boosted pressure. This makes sense if you're expecting to conduct manoeuvres that may lead to situations where engine could potentially be starved of fuel, or the fuel quantity remaining is generally low. NORMAL: The fuselage tank booster pump (electrically driven) is turned OFF, and the fuselage tank by-pass valve is set for normal operation (i.e. open) to supply fuel to the engine under normal engine-driven demand pressure. BYPASS: The fuselage tank booster pump (electrically driven) is turned OFF, and the fuselage tank by-pass valve is reset to permit fuel from the other selected tanks to by-pass the fuselage tank straight into the engine. This should only work provided either Leading Edge or Wing tanks are selected on. This is indeed an abnormal operation procedure for which you want to avoid routing fuel through the fuselage tank (usually due to a suspected failed/clogged fuselage tank valve). Thanks!

Thanks for the feedback everyone. We're monitoring all feedback/bug reports and are working to improve the product wherever possible. Just as a summary so far, the team is aware of the following reports: Mirrored Textures for repaints Colors/material of Thunderbirds USA livery. Paintkit - this is a WIP. Flight Dynamics - Particularly pertaining to low-speed and stall characteristics - also a WIP. TACAN - also a WIP. The list above is non-exhaustive, and there are other improvements also coming. These are just the main ones I've seen reported on the forums and socials elsewhere. Thanks!

Hi @Javilis23 Yes, you can only have one scenery active at any given time for an airport to avoid conflicts. Please uninstall the WU17 EGSS from your content manager, then restart your sim. Also advised to clear your scenery indexes in this instance: Thanks!

Thanks for sharing. Will see if I can reproduce a crash in those instances.

Yes, is planned but not available on release. Thanks!

No additional repaints or language versions planned at the moment, but thanks for the suggestion. I'll share with the team. As for paintkit, is planned but won't be available on release. Thanks!

Thanks for sharing. I'll forward to the team should they need it. We're also eager to get this plane in your simulators ASAP so expect a release very soon. We just wanted to pack in as many improvements as could be validated in time by the involved parties prior to the target release window. More of those will be coming in the patches post release. We hope you will enjoy this bird and keep sharing your stories, notes and feedback with us! The release is only just the beginning for this plane (and Premier series of aircraft) and we look forward to going forth on this journey with all of y'all! 🙂 Thanks!

Hi, thanks for your report. Yes this was an issue in other languages too. Should be fixed in the upcoming AAU3 update once MS releases it. Thanks!

Yep in this case it does appear to be a WASM crash based on this additional info. In this case, please follow the guidance below to let us know exactly what interaction you made (button clicked, control input sent etc) just before you noticed the crash. ---------- What is WASM? Why do WASM Crashes happen? These can be caused by either a) faults in the code, or b) in the way that code is executed by the sim. a) Faults in Code While we try our best to find and quash all bugs in code, we are still human. Mistakes or oversights can happen and sometimes these can lead the code to fail in certain specific instances, resulting in a WASM crash. These kind of crashes will be reliably reproducible, meaning you can have the crash nearly every time by executing the same code (e.g. by selecting something on the MCDU, or by pressing certain buttons on the plane, or by flying certain SID/STAR/APPROACH etc.) These types of WASM crashes are actionable, and dependent on your reports of the steps taken immediately before the crash happened. These, if reproducible on our end by following the same steps, can be debugged and usually resolved in a following update. b) Faults in the way the code is executed by the sim Since SU15, we suspect, there have been instances of "random" WASM Crashes caused by a "memory allocation bug", wherein the sim tries to reserve memory (for WASM) that it does not have access to, as a result leading to a WASM crash. These types of WASM crashes are difficult to reproduce and not something we can address as its not an issue with the code, rather just in the way the sim tries to store and execute it in some instances. These types of WASM crashes are not actionable on our part and would instead need fixes on the simulator's code (if possible). So why did you experience a WASM Crash? As mentioned above, we will first need to find out if the crash was (a) or (b). So you need to take note of what you pressed or things you did, just before you noticed this crash happen. What systems stop responding, or what you cannot click after the crash is irrelevant as the whole WASM has already crashed, so anything using WASM will equally stop responding. Additionally, please see if you are able to repeat the crash by following those same steps. Once you know, you can mention those steps to us, and we can try to reproduce on our end to see if its actionable. Thanks!

Thanks again for trying all the suggestions above. Hmm, I'm stumped as I cannot reproduce the issue on my end on either iniStore or Marketplace versions of the A300. Same holds true for others internally. We have tried assigning axis through various different means, and tried on hardware such as T.Flight Rudder Pedals, MFG Crosswind, Xbox Controller and TCA Sidestick. Can you also confirm there's no additional external addons like FSRealistic running that could cause conflicts? I also run it and haven't had any issues but just checking. Last suggestion remaining (if not tried already) is to assign your rudder pedals to the 'NOSE WHEEL STEERING AXIS' in MSFS. That has confirmed to work for Hardfloor & another user report from earlier: Thanks!

If using Navigraph (i.e Jeppesen) charts, this information will be at the bottom of the approach chart. It is typically shown as DA(DH) format. DA being the Decision Altitude (BARO) and the DH being Decision Height (RADIO). You'll have to choose the appropriate one based on the type of approach being conducted, and also the Approach Speed Category of your aircraft type. Use RADIO/DH for an ILS CAT II/III approach, use BARO/MDA/DA for all other types of approaches. In the example below, C : 824' (230') is chosen if you're conducting a standard ILS CAT 1 Approach in an A320Neo, which is a CAT C aircraft. So you'd use the BARO value of 824 in the MCDU. The above snippet is from this video that explains this further: https://youtu.be/0u0fN3FEOvQ?t=742 Thanks!

Awesome! Thanks for sharing your solution. Hope it also helps someone in the future 🙂 Thanks.

Please try to toggle REVERSE ON AXIS to NO, then back to YES in order to "force reset" the existing calibration. Then run through the calibration process again and immediately after restart the sim. This will ensure the settings are both saved and applies again properly. See if the issue is resolved after. Also verify in your MSFS control settings that both the throttles are assigned to their independent throttle axis only (Lever 1 to Throttle 1 Axis, and Lever 2 to Throttle 2 Axis). On the EFB, you should see the green bars move evenly together as you move both the throtttles. Also the marked detent on the EFB should match the detents on your TCA Throttles if setup properly. Thanks!

Hi @D-Ruston Thanks again for sharing. As replied to the same message on discord: Thanks!

Hmm that is quite strange. We haven't observed any outright CTDs with the A320Neo V2 on our end. You could also try to change your graphic settings and see if that makes a difference (in case its to do with some kind of rendering/driver/shader cache bug). Thanks!

Can you confirm that you tried to delete the files in either one of these locations only? If you delete the files in any other location that could cause the plane to not function properly. In which case you should delete and re-install the plane via the in-game content manager. Steam: MS Store: If you're still having issues, please try with an empty community folder to rule out any addon conflicts. Thanks!

Unlike the modern airbus, the ATHR is not to be used on the A300/310 for landing other than when coupled with AP for an autoland. This is per Airbus guidance. AP OFF, but A/THR ON is a scenario for which there is no guidance, as such its operation is probably not guaranteed, therefore ultimately not supported. Thanks!

The autopilot can go off for following reasons: Excessive control inputs (either aileron/elevator/rudder axis) - So it could be due to inputs being given whilst you are trying to change views, or if you have any kind of stick drift / noisy axis Excessive Turbulence - in adverse weather conditions or simply too much fluctuation of wind vectors, the AP can disengage if it cannot properly maintain level flight Control Binding Conflicts - You have AP Toggle / disconnect also accidentally mapped to buttons you are using to change views or conduct any other functions. Please double check your control bindings in options. Please check and ensure neither are happening leading to the issue you're noticing. This will only appear once you are properly in cruise and have appropriately filled in the INIT B pages with the relevant data (ZFW/ZFWCG/FOB etc). The INIT B page can only be accessed in pre-flight, with both engines shut down by pressing INIT on MCDU, then proceeding to next page. This is a bit difficult to do without access to charts for the airports you intend to operate in and out of. For the USA, you can typically find the charts online for free, through sites like FlightAware. Equally, you can also find routes with the planned SID/STAR filed on FlightAware for easy reference. I would also recommend watching some videos on Youtube that can guide you through this process. One such example as below, but there are equally very many tutorials out there: https://youtu.be/Y11WmGlvaIE Thanks!

Can you confirm that you have exhausted all suggestions mentioned above? Including the ones about known conflict such as toolbar pushback? Also in this video, did you just spawn on runway or was this after pushback? If after pushback, what are you using for it? It seems like an issue where the "pushback" tool used (be it toolbar pushback or GSX for that matter) hasn't properly relinquished control, hence you're still essentially "slewing". I would also recommend trying to use the A300 with an empty community folder. This is to rule out any conflicting addons. Instructions below: Thanks!

Can you check that any 3rd party programs (e.g. Logitech's controller software) aren't running that may be keeping some sim code/services running that could cause issues. Thanks!

Hi @Adrian Ramdeholl If you join up our Discord, please checkout the following post: https://discord.com/channels/535246634448191499/1243652318868668487/1243652318868668487 Here is a small snippet, but there's a lot more information in that thread: It goes into more detail about the references used and why the sounds are the way they are. While there may be room for small improvements in balancing, overall we feel the sounds to be accurately matched to the references available to us. Thanks!

Glad to hear it is resolved. As the service is dependent on both Microsoft/Azure and Navigraph/Simbrief servers, sometimes there may be temporary outages that can cause problems. Thanks!

Can you confirm you are using the latest version of the iniManager. Grab the latest installer from here and run it: https://inibuilds.com/pages/inimanager-v2 Also, please try to "run as Admin" the iniManager app. Thanks!

Unfortunately that is something only MS/Asobo would know.

Hi @browns11 Thanks for your report. I was able to reproduce the issue. I'll share with the team. Thanks!