LukeFF

Got it, and thank you for clarifying this. That was in contradiction to what I heard before.

Thank you, will try again when I have the chance.

I will have another look when I can, but I do know that already I have the sliders set the maximum level.

After updating to the latest version, clearing my scenery indexes, redownloading the GSX profile, and ensuring everything was configured correctly in GSX, I spawned into a freight position and went into the GSX options. Once there I was told there are "10 parkings not found in navdata."

The texture for the RAT turbine lever is quite low-res:

Two things: IIRC wear and tear was supposed to be per plane type, but from what I can tell the W&T value is shared among plane types. That is, after flying the PW freighter I loaded the GE model and saw the values were the same. Any way to change this? Just to confirm, is the wear and tear of the tires and brakes is just cosmetic, i.e, I could land with completely bald tires and shot brakes and nothing bad would happen?

It's also just cosmetic with GSX, i.e., freight is loaded instantly with the push of a button on the EFB. GSX will "load" freight but it actually doesn't do anything.

The chime when turning on the fasten seatbelts sign only plays once, i.e., if you turn it on during the cockpit prep it'll sound the chime but if you turn it off and then on again during cruise the chime sound won't play.

You have a fuel mixture command mapped somewhere in your controls.

When panning around with the camera, these two circled areas exhibit heavy texture flickering.

There is a mismatch between values like ZFW and ZFWCG on the EFB and the MCDU. Also, block fuel is in KG instead of pounds when using imperial measurement units:

Bit of a weird one: on the ground, 3-position switches like the strobes will jump straight from off to the on position while on the ground, but once in the air they will move incrementally, one position at a time.

Bump 🙂

Appreciate it. 🙂 Yes, sometimes it's hard to remember the procedure is slightly different from the A320 and just pushing the throttles forward.

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.

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.

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.