LukeFF

Having been a flightsim beta tester for over 10 years now, I can tell these things are not tested all that thoroughly.

Thank you. It also happened just now when taking off from 25R. Framerates dropped down to the single digits, causing me to veer all over the runway. TLOD and OLOD again at minimum.

Yes, I have the same problem here. FPS are nice and smooth coming in to land, and then about 2 miles out, the frame rates drop through the floor and thus make a proper landing impossible. Something just isn't right with this scenery.

The ILS 04L localizer is entirely misaligned with the runway when trying to land with the A300. It's displaced far to the left of where it should be.

Would be nice to have this as an option.

Seconded. This is a great piece of hardware that needs to be made functional with the 320.

I changed my frame generation to FSR3, and so far that has yielded much more stable performance.

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.

You're talking to a spambot.

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