LukeFF

This is how close I have to get from Gate 34B to see all the details of the tower. Any further than that, and then the details start getting chopped off very quickly. Zoom back to behind my plane, and this is what it looks like: This is entirely unacceptable for an "Enhanced" airport:

. Never mind, issue likely found.

Per the thread originally started here, the clock is still missing a lot of details: https://forum.inibuilds.com/topic/21164-issues-with-the-clock/

Not so with 2024. With all other planes, once you set up your controller profile, it will remember your choices, so you don't have to manually choose them every time. With the A300 it's not doing that and reverting to default on every startup.

@Eddie, I just noticed in a recent announcement post that N692FE is shown in one of the images. However, if you type in "FedEx" in the app, the only one that shows up is N667FE. Has this one not been uploaded yet? And please, again, we need PW liveries for FedEx too. 🙂

Thanks Also, it looks like "Register" is misspelled as "Regisrer"

Okay, thanks

Max turbulence setting Route: DUCKZ5 HELAR DCT KOMMA J6 DWINE RIFFL3

Okay, good. Yes,it's been working as expected, then.

The clearance frequency comes up as "Clearance Clearance" on the radio in BATC. Their developers said they cannot do anything about it and it must be fixed by the scenery developer.

No, I have all damage settings turned off.

Yes, no issues here - I can keep the en route map open the entire flight without any flickering, after the latest updates.

After parking, the emergency exit slides are deploying for some reason (auto slide arming is enabled). I've seen this happen 2 times now since the last update.

It appears the Flex Temp pushbutton above the righthand ECAM display does not make a sound when it is pressed.

Lol no, you aren't going to be banned because of a motherboard change.

Also, when I cleared everything out of the WASM folder, I noticed I had a "inibuilds-aircraft-a300" subfolder and a "inibuilds-aircraft-a300-600" subfolder, even though all my installation files are under the latter folder name. There are no WASM files in the "inibuilds-aircraft-a300" subfolder.

@haza2, cleared the WASM folder and it made no difference.

Never mind, I see now where it needs to be done. I will try this when I get home tonight.

Not yet. Where is the folder for that?

Thanks. The flight tonight went fine, so hopefully these crashes are a thing of the past now.

Descending into KOKC, RIFFL3, through ~FL180, the AP just randomly disconnected on me for some reason, and when I reconnected, it was trying to go back to our previous waypoint. Was roughly between DWINE and DIMPL.

The bumping sounds - they are noticeably absent on takeoff and landing. While on the subject, the thrust reverser sounds also seem to be missing/much diminished.

As the picture shows, half of the landing elevation display can't be seen at night now.

For a while now, Simbrief has been giving cruise altitudes that are above what the MCDU recommends, i.e., tonight it generated FL320, but the MCDU gave a max of FL310 and an optimum of FL285.

Seems I forgot that an active flight plan needs to be filed in order for it work, is that right?