Systems

Inibuilds A300 Master WASM Crash Thread 1.0.11 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. …

Hi Team, I've been having a persistent issue for a little while now with the A300 in 2024, after touchdown the nosewheel steering pulls the aircraft left, despite the tiller and the rudder being centred. I've messed around with the rudder trim too, but it makes no difference. I have the NWS connected to the rudder through my joystick. The stick is also centred (I've checked the settings menu), and the flight controls page shows the rudder centred. On load in at the start of the flight there's no issue, it taxis in a straight line, it's only after landing. This has been the case for the last two versions of the aircraft.

Using freighter - the click zones on the switches in the cockpit are off. Many don't click at all, some only click at very specific points, some click normally. Issue is especially a problem with fuel pump switches. Does anyone have any idea?

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 am using the premium FS 2024 version of the A300-600r. I can only get LIDO charts to display in the EFB. I have selected navigraph charts in the options section. However, they do not display. I have reset my navigraph account details and then logged in. The navigraph logo appears for a second and then immediately they revert to LIDO. This also happens in the A340 and A350. What is the problem? I have a valid navigraph account and the AIRAC cycle is up to date. Please advise. Thanks

Just recognized, after using the 300 after a longer time, that I'm not be able anymore getting the landing gear lever up and in the middle position. I use HC bravo and I'm flying in 2024, beta 6. The softwarelever stays in down position while the hardwarelever of the HC went up. It vibrates and bumps in that down position as if it tries to go up, but it doesn't can do it. Fortunately in the plane the gears are going up, only the lever in VC doesn't go up. For that reason I'm not able to arm autobreakes. I know it works before; I put the lever in the middle position with the mouse, but for that the lever has to reach the up- position before. What can I do here?

There are still numerous issues with the F-PLN page that have been reported for a long time. The predicted speed for waypoints in cruise are still given in IAS rather than MACH. There are duplicate (T/D) pseudo waypoints. 3 way switches still have inconsistent scroll wheel behaviour. For example compare the BRK A/SKD or the LDG Light switches with the FD/FPV and CONSOLE FLOOD LT switches. For the first two if you scroll up the switch moves up, but with the last two, if you scroll up the switch moves down. It is really annoying. The level-off arrow and the banana on the ND also need work just like all the other airbus aircraft in your fleet. Clicking on the LSK…

Greetings, I just updated to the latest version of the A300 Premium for MSFS 2024. After the update, the APU will no longer start. Any suggestions?

As the title says, pulling the V/S knob puts speed in manual mode as it should. But it starts at 000 kts meaning you always have to put it back up to speed.

I was well into my flight. I switched from Nav to VOR. As soon as I touched the VOR tuning knob, I got a CTD. This is build 1.0.10

The volume control knobs seem to only work with the modern avionics cockpit panel and not the original when used in conjunction with BATC.

It seems the 1.0.9 Updates has broken the A300 .. Unclear status at loading Many clickspots not working at the overhead, buttons off Radio / Tuning Panel not working Startup impossible..... Guys, who has made QA for this update..... Reinstalled, cleared WASM etc... no changes ...

Hi, Lately I’ve been trying to do regional flights in my Airbus A300-600 and when I load into a ramp I can load my cargo etc. But when I push back and start my engines my fuel which was originally at 70%, which is what I set it to before I loaded into the flight instantly goes straight to 11% fuel which can hardly get me a few NM out of the airport. I have tried many solutions to attempt to fix this problem but none of them have seemed to work. Any suggestions?

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

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?

Just want to know if the Market Place version of the same aircraft (A300/600) for MSFS2024 is and does it have the same features as the one on Inibuilds website/iniManager called Premium Edition for MSFS2024? I see no mention of it on the Market Place as being "Premium" Edition, the reason I am asking. Simple question I hope someone at Inibuilds can answer. Thanks in advance!

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…

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

Hi, I see YT movies where people can activate FLT RCDR button but it's not working for me (flying the freighter). Am i forgetting something? Also at TO, my FD bars are not showing and after spooling up to 40% N1, the TOGA/Go Levers button on the glareshield is not working. Should I ever press auto throttle button? Capt Ini

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 …

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?