LukeFF

BATC has a new update where the aircraft's radio is controlled by the COM1, 2, etc volume and reception /transmission knobs. This does not work correct with either radio stack right now.

I'm going to be as civil as I can here, but still, I feel the need to say it: the Premium version of the A300 as it is marketed right now doesn't deserve the tag of being called a "Premium" plane at all. I originally bought the A300 for 2020 not long after it was released, and so I went through all the hassles of the random crashes on loading, issues with sound, etc., etc. On the eve of 2024 releasing last year, though, it was a reasonably stable plane, with WASM crashes being mostly eliminated. Enter the 2024 "Premium" version. It has been plagued with issues since day 1, such as: WASM crashes are more frequent than the last version I played on 2020 Freezes on exiting every single flight Has major reflection issues with the windscreen, especially at night. Has various audio issues, like missing sounds from the landing gear when taking off, engine fan blade spinning sound playing with the covers on, missing AP disconnect switch sounds, etc. An issue with importing wind speeds that was originally reported in 2020 is still present in the 2024 version. And so that all leads me to tonight. As for a lot of people I'm sure, it's a work night, but hey, I had enough time to get in a short flight. So I go through the normal startup routine, get to the Progress page, start to type in my airport information and...WASM crash. Exit out (but first, of course, having to force-close the sim because it freezes up), restart my flight, make sure to avoid the Progress page and we're looking good. We complete the engine start, I shut off the starter switch and..."Low Yellow Hydraulic Pressure." Eww, okay, never seen this one before. Bunch of error messages but the plane's still controllable on the ground, we got this. Take off no issues, go to engage autopilot and...oh, that's wonderful - low yellow hydraulic pressure means the autopilot won't engage, i.e., this plane would have never even left the ground in reality. At this point I've had enough and punch out (after, of course, force-closing MSFS 24 once again). So, that was about an hour and a half of my time wasted tonight with a WASM crash and a borked hydraulic bug that I see was reported long ago but still hasn't been fixed. I'm not going to go back in now and try again, as it's less than an hour til midnight and it's just about time to head off to bed. iniBuilds, you have some major quality control issues you need to fix with your planes if you expect me to buy any more aircraft from you in the future. It bugs me to no end that things like this persist after this long, even though they are marketed as these wonderful things with tags like "Premium". They aren't. The A300 right now I would call an early-mid beta plane with issues that still are in urgent need of attention. Fix your stuff already so we can enjoy them like they are meant to be.

Oh, and this is wonderful as well: when this issue pops up, the autopilot is INOP, i.e., the plane wouldn't be able to be dispatched in reality. Wow, just wow.

I encountered this same issue tonight. GE freighter version.

A300 GE freighter, Memphis, attempting to enter airport information on the progress page. This is really getting old for a plane being sold as "Premium."

The captain's DH button has to be pressed several times before it will turn green and the player can enter a decision height value.

Cheers, thank you!

Per the title, the APU can run with the required fuel pump shut off.

So why was it released with this issue? This isn't some minor texture bug - it's quite literally in the player's face, 100 percent of the time.

It's broken right now.

Acknowledged as an issue when it was released CTDs on exit).

In 2024 there are double windsocks all over the airport, including these two.

There is some grass coming up through the concrete at 01L.

At gate 76 the jetway did not connect to our aircraft properly. FBW A32NX

The two vehicles parked in front of the fire station have doubled-up models, i.e., there are second, duplicate models placed on top of the first ones.

With the engine covers on, you can still hear the engines spinning, as if they are open to the wind.

That's up to Microsoft.

Default LOWI confirmed disabled, too.

There are a lot of issues with snow coverage along the perimeter roads and along the approach path, plus I spotted a buffalo wandering the ground as well. 🙂

Hi, I've only tested it with the GE freighter. It seems to be an issue only when the rudder trim is zeroed out (or perhaps it's just really faint).

Take your complaints to MS. They are the ones responsible for updating these aircraft, not iniBuilds.

It appears the rudder trim reset button has no sound right now.

To add: this also seems to extend to the takeoff performance page too.

Tonight I flew a flight where I set the clock back about 12 hours. After importing my flight plan I checked the A300's EFB (not the MSFS one), and the QNH was given as 30.00. However, when I requested a weather report at the same time from the IDC, it said the altimeter was 30.13 (the actual value in the real world at the time of the flight). So,it looks like the A300 EFB is reading the historical QNH but the IDC (and BATC for that matter) is showing the current QNH.