Systems

Inibuilds A300 Master WASM Crash Thread 1.0.8 FS2024 This thread will be the new location for all WASM Crashes relating to the Inibuilds A300-600R for Microsoft Flight Simulator 2024 Below this message will be where users can upload their WASM Crashes pertaining to the current version of the A300. NOTES: If you do not see orange expectations screens on your displays or "WASM exception in X gauge" in the developer console it is not a WASM crash. The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo. Investigations will only be opened into WASM crashes once they have been confirmed to be reproduceable. …

Just bought the A300-600R Premium for MSFS24 the other day (along with the A340, which so far has been working perfectly, for what it's worth). Really cool plane, and I'm liking the new features/improvements compared to the older A310-300 included with MSFS24; but I'm having trouble getting several of the button and switch clickspots on the overhead panel to work. Several of these are critical to flight, so this has unfortunately rendered the plane unflyable for me. First off, all of the overhead panel pushbuttons (for instance, all the fuel pump controls) have really tiny clickspots: the "hand" pointer (I'm using Legacy cockpit interaction mode, which, per my unders…

I’ve had a read of the WASM crashes. No need to add as they’re already there. Mine is primarily entering. STAR and hitting the STAR button in menu. Someone has mentioned click spots on the overhead. I have the same and periodically all other click spots around the flight deck. MCP, FMC, lights etc. Allan all round mismatch. Hope this helps Ryan

Two main issues: - The copilot doesn't always auto-tune the radio to a new frequency when ordered to -Trying to log in to KUSA on the CPLDC page results in a "format error" message, so ACARS messages are not sent or received during the flight

Flying the 2024 Premium PW Freighter, noticed same on GE Pax. Trying to tune the ILS to 110.8 however when turning the dial it jumps from 110.75 to 110.90. In fact, after touching the dials, the kHz only lets me select .10, 15, 30, 35, 50, 55, 70, 75, 90, 95. The pilot and F/O VOR radios do allow the whole range in .05 increments. Unplugged all controllers and unlinked most of my community folders.

PW Freighter - when pushing the TO Config Test button, I often receive an "Oil Temp Low" message, even though the temps for both engines are in the green. In this case, it was for the left engine, which was at about 67 degrees, while the right-hand engine was about 80 degrees.

Latest update feedback I tested the latest update and found a few issues worth reporting: AIRAC / FMS arrivals AIRAC appears to be current, but when selecting an arrival in the FMS, all STAR and runway information disappears. This happened to me on an EBBR–LIMC routing, and the same issue also occurred for edwardthepilot during his stream. I have attached a screenshot taken from the stream. Sound balance The overall sound mix feels off. Reverse thrust sounds are significantly too loud and sound distorted. Cockpit / exterior sound transition …

Up until this last update, I had LVARs mapped in Axis and Ohs to control the windshield wipers. But, after this last update, they stopped working. I checked the code and nothing seems to have changed. Has something changed with these?

This is a general question, as of the 14th of May KCLT has renumbered 36L/18R to 1L/19R and within the airplane the option to select these runways is not with the plane anymore at all, not even the previous runways. Would this be the new Navigraph AIRAC issue or just the plane issue?

Hi everyone, I am experiencing an issue where both the trim wheel movement sound and the touchdown sound are completely missing in the iniBuilds A300. Here are the details of my situation: The trim wheel moves visually, but makes no audio. Touchdowns are completely silent upon contact with the runway. All other cockpit and environment sounds work perfectly. EFB volume settings are all set to 100%. I have already cleanly reinstalled the aircraft multiple times, but the issue persists. Has anyone encountered this or found a fix? Any help would be appreciated! thanks and greetings

I’m having a serious issue with the A300 where several overhead panel clickspots, especially critical ones like fuel pumps and pitch trim, are either extremely small or not working at all. In some cases, I briefly get a clickable “hand” cursor, but it’s inconsistent and unreliable. Most of the time, I simply can’t activate the switches, which makes the aircraft essentially unflyable. I’m aware an update has already been promised, but I’m wondering if anyone has found a workaround in the meantime?

Flaps, Spoilers and the Thrustlevers are broken. If i try to select Flaps or arm the Spoilers they jump wildly between the positions. Same if i move the Thrustlevers. I have a video but its to big for the upload. I dont have any problems with other Inibuild Airplanes for example A350 or the A330. Hardware is working fine.

I can't start either engine - this just suddenly started happening. I have the APU and bleed air on, but the N2 won't go past 25%. It just hangs there.

Fuel doesn’t seem to transfer to the trim tank on climb with wing (inner and outer) tanks full and center tank empty. Is this intended or is the fuel meant to be pumped back like in the A330 upon reaching a certain altitude?

Whenever I go into a flight it’s fuel is set to 11% despite the fact I have unlimited fuel on. Is unlimited fuel incompatible with the a300?

I saw a different forum regarding the WASM crash upon selecting ONLY the STAR/ARRIVAL and runway in the F-PLN in the FMC. I'm currently facing the same issue, except I don't have a solution. Everything else works besides the selection process. I've tried every possible way: deleting the WASM folder for a fresh restart, reinstalling the aircraft, selecting the STAR before and after inits 1 & 2, importing the SIMBRIEF flight plan, or manually entering the route. Pretty disappointed with the recent WASM crashes, but curious if there is at least a temporary solution. Flying the plane freely feels really nice, but I could never complete a full flight with this inevitable f…

Hi! Thanks for the great Update!! 😇 Unfortunately since this latest Update my Autobrakes won't work anymore during landing: I can arm them on approach, but as soon as the aircraft touches down they immediately disarm. I experienced this on several flights and made sure that there are no more "Autobrake" Keybinds remaining from my hardware... Can someone confirm this fault? best regards, Benni T.

Hi there, I downloaded the lastest version of the A300. I inserted my API Key (ACARS ID) from SIAI but even with that it does'nt work. I checked the acars dump from SiAi but I don't see any of my request. Can someone help me to do it right 🙂 Cheers Pelgrims Jean-François

Hello ! First of all, thank you for the 1.0.7 update, performances are much better and I can finally fly the plane on Vatsim ! But now I'm having issues with the CPDLC, everything seems to be fine, except for the WILCO messages, which make it impossible to use 😕 I had multiple issues on VATSIM because of that : - The other day a controller gave me a DIRECT TO, and I responded with "WILCO", but then he called me 5min later on the radio saying that he didn't saw my response (even though I could see it on the Hoppie log page) - Today I tried to request a PDC clearance to the ground controller, I responded to it with WILCO, but then it was rejected, saying that I…

Searched this forum for this bug but to no avail — however there are plenty of reports of it in the official MSFS forums. Two flights so far (only purchased it today) and both resulted in all screens turning bright orange shortly after TOD. As it stands, I can't do any flying in this aircraft because of the risk of being unable to complete the flight. What's going on?

Please see attached below. Routing: EGKK/26L N0450F350 NOVM1X NOVMA L620 SAM M195 LORKU DCT POZOF DCT BALDA DCT ABUPI DCT MOMAS DCT SOTEX DCT LPFR/28

Despite this now-closed topic saying it cannot be reproduced, it is in fact still a bug: https://forum.inibuilds.com/topic/31619-land-button-not-illuminating/

The ground handling on takeoff and landing during the rollout is still extremely exaggerated after today's update, making it feel like the plane is maneuvering on ice.

Two things I noticed tonight: The "push to sync" the heading knob is reversed (it's now pull to sync) The console flood lights are on at the beginning of every flight (originally reported as an issue with the 2020 version)

I have installed, uninstalled and then reinstalled. Every time I load into the 600F Premium, I have to service both engines, hydraulics and the APU even though I have the option turned off. If I don't, everything is at 0%. I turn all 3 batteries on but can't get the External Power button to illuminate even after servicing the APU and attaching the GPU, although that button doesn't stay lit when I click it. There are other problems too like sunshades and the instrument panel is illuminated every time I load in. I'm at a loss and don't know what to do.