richboy2307

Hi DH, Thanks for your question. The answer to this is Yes. The fuel won't vent simply when the FUSE tank is full. There is an additional condition that ALL the tanks are also turned ON at the same time for fuel venting to occur. Allow me to clarify below, and also illustrate via a video that I made for a similar support query submitted on our discord: Thanks! 2024-09-09 15-31-40(1).mp4

Hi thanks for your report! I do see the "L.E." indication is duplicated on the fuel system page. Whereas one of those (the one marked) should be "WING", as seen to match the fuel values of LEFT/RIGHT WING on the Weight & Balance menu. However, I don't understand your report regarding them being reversed? Could please share a screenshot of where you are noticing that. Thanks!

Thanks for the suggestions. I'll share with the team to see if we can add some kind of acceleration to the scrolling of the totalizer, and an EFB option for auto sync. Could you please elaborate on this? Do you mean a fuel and payload manager? The reason there isn't any is due to the size of this EFB. It being small phone does not leave much room for detailed schematics or or many pages either. Thanks!

Not in works at this time, but thanks will share your suggestion with the team.

I have also used the T-33 along with FSLTL Traffic using the modern avionics without issues. One of the A-B flights I did were KTPA to KMIA (with FSLTL), along with some other operations en-route. Did not experience any CTD with a lot of traffic around, as part of testing returns on the G3X TCAS. So again, the T-33 itself is highly unlikely to be the cause of a CTD. As for the horizon bar, it is a separate element that isn't part of the rotating gyro ball inside. It just moves within the visual limits of the instrument, unable to hide itself completely in either extremity of pitch attitude. That being said, thanks for the additional resources and documentation linked. Will share with the team. Thanks!

Hi @Editer Will share with the team. However it is a limitation of the sim sadly in the way it models droplets on glass surfaces. It will put it on anywhere defined as glass materials that is exposed to the environment. Thanks!

Hi @mgr Yes, this is by design - the AP is disabled upon switching of panels based upon feedback during testing. Reason: To avoid instances where the user is stuck with AP engaged accidentally upon switching panels as there is no way to interact with it in the classic cockpit. Additionally there is no indication of AP state in the classic cockpit, so the issue may not be immediately obvious to a user either if accidentally (or intentionally) engaged via any control bindings in the classic cockpit. As for ease of tuning, we'll look into QoL improvements for tuning via the EFB, specifically for NAV radios. As for the COM radios, they can already be tuned via the EFB by clicking on it. The list is populated by frequencies available nearby the user and can be refreshed by a button on the same page. Thanks!

Hi, thanks for your report. Could you please provide more info or share a screenshot of your sim's graphic settings? So we can try the same settings and see if we can reproduce the issue. At the moment on DX11/DX12 with either TAA, or DLSS anti aliasing not seeing any such flickering (RTX 3090). Thanks!

Hi @tivapularz All the currently available info (such as planned variants) can be found in the FAQ here: We're targeting only the variants listed there for initial release, and will see about other variants only after that. Thanks!

Yeah that was intentional. We had received feedback early on during testing that the horizon line only moved up and down on this particular instrument, whereas bank indicated by the top triangle and the angle of the gyro ball inside the ADI. So it was changed to reflect that feedback. But we'll look into it again and make the changes if necessary. Thanks! Unfortunately also unlikely. I've done 3 60min+ flights with different avionics and could not observe any memory leak or abnormally high memory usage. Sorry, we're not able to reproduce any CTDs on our end. Try with an empty community folder as suggested above. Or without any additional software running that communicates with the sim in real-time to rule out potential conflicts. For completeness, I have been using this plane extensively with addons like FSRealistic, Vpilot, Navigraph Simlink, LittleNavMap, FSUIPC7 and SPAD.Next without issue. Fixed. Thanks!

Hi @Alan_A No worries, I've moved your topic to the suggestions section where I feel its more appropriate. In the image above, 111.80 is tuned into NAV1. The first digit is always 1 so its omitted. Only the 11 / .8 / 0 parts are tuned by each of the 3 dials. For tuning the digits at position A, the click spot for the inner most dial is at position 1. For tuning the digit at position B, the click spot for the middle dial is at position 2, reached by moving the mouse outwards towards clickspot 2 from center of the dial. For tuning the digit at position C, the click spot for the outer dial is at position 3, reached by moving the mouse inwards towards clickspot 3 from outside of the outer dial. Noted. I'll share this suggestion with the team. Thanks!

Hmm, we are not able to reproduce the issue. On either Marketplace or iniStore version. Able to get the chimes across various stages of flight, multiple times. There is a certain cooldown period (less than 5 seconds) for the sound, so they won't play simultaneously if you keep spamming the switch, however at no point did it only play once for the entire flight.

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!