LukeFF

As the title says, the terminal building is entirely empty of passengers, unlike other iniBuilds airports. Surely a few could be spared. 🙂

Don't have time for a video right now, so I'll try to explain: - Was too high on approach, so I raised gear and flaps, then increased speed via the front panel back to green dot speed. - Approach mode was kept active - Flew the go-around procedure as directed by ATC - When the localizer diamond showed on the display, it went right past the centerline without capturing - Disengaged and then re engaged approach mode, flew back towards the localizer, and now it was captured

So what's the status of this? I was almost to the end of my flight when this stupid bug popped up again. Really, really unacceptable that this has been allowed to go on this long.

The scenery data is assigning AAL flights to taxi to Gate 10 via BATC, even though the official GSX profile shows that AAL flights don't use this gate. Pretty much every AAL flight from to and from this airport goes through Gate 4 instead.

Any update on this? It's been six months since the last post on this issue.

Not sure if this is a bug, but here's what I have been seeing: If you capture the localizer with Approach mode but have to execute a go-around, the plane will not capture the localizer on the second landing attempt. The only way it will recapture the localizer is if you disable and then re-enable Approach mode. Is this the correct behavior?

On the instrument for the port oil quantity gauge, GE freighter, if you drag it all the way to the right, it becomes stuck and you cannot drag it back.

Yes

I activated the VGDS via GSX at gate 32A, but instead of that, the sign was floating in midair above gate 32 and as such I ended up parking very strangely.

Thanks, fixed now. 🙂

Just like in this topic, it never moves past the main loading screen: https://forum.inibuilds.com/topic/23171-inimanger-not-launching-even-after-new-installation/ I uninstalled and rebooted my PC, and reinstalled from the latest file available, and the problem is still there.

Check your EFB settings.

Right now, with Beyond ATC, it will send you to the K intersection to take off from 31L, as the scenery data doesn't recognize the full length of the runway.

Secondary Flight Plan was noted as being inop by iniBuilds when the last update dropped. The TOGA clickspot moved. Watch the latest A300 video from iniBuilds to see where it went.

Wait, so lightly tapping the brakes is supposed to send the brake temps into the red, every time? That seems odd.

Apron A is not configured as a cargo parking area, which means when Beyond ATC asks for the cargo ramp you want, the spaces on this apron are not a choice. Secondly, passenger aircraft are being populated in the Apron A area by FSLTL, which leads me to believe there is a ramp assignment issue.

The A310 manual they created is much more comprehensive than the A300. If you have a look for it in your installation folder I think you'll find it to be very helpful. But yes, the included A300 manual is pretty minimal. Makes me wonder why they shortened it from the A310 edition.

Yes, it was noted in the last update.

They aren't making an A220; they're providing support to the team building it.

It's for sale right here on their website.

-

Yes, I have.

This is at Gate 59: there are overlapping sets of numbers

Nothing wrong with that - its flight computer doesn't respect departure restrictions in reality.

South parking, stand 614, some textures are very low-res even with HD textures enabled: