LukeFF

Yes, I'm thinking it was some weird one-off bug, because I've not had a problem since with my two ILS landings. Auto throttles were definitely on. Anyhow, will keep an eye out to see if it happens again.

Yes it's definitely disabled. The only culprit I can think of is Beyond ATC, but the app doesn't have any interaction with the plane at that point. Nevertheless, I will bring it up in their Discord.

Alright, I'll look at it again when I get the chance.

I had something happen to me today that I've never experienced before. Landed normally, 1.3 G landing rate, no bounces. Speedbrakes were armed and autobrakes were set to low, LAND mode engaged. When I went to engage the reversers as I always do, though, nothing happened. We just kept going down the runway, throttles stuck in the full forward position. Moving the throttle lever on my controller did nothing, trying to engage the reversers did nothing. Eventually the plane, with warning lights going off everywhere, careened and bounced back into the sky. I loaded up a new flight to see if I could reproduce the problem, but of course, it landed just fine, reversers engaged normally, etc. Totally bizarre.

Alright, I finally got around to checking this and there is definitely a bug with it. It also happens when using the red AP disconnect button on the yoke - the sound will play the first time but not any more after that.

With the modern radio stack, if you enter a frequency into COM1 in the active slot, it will change on its own after engine startup. Happens every time regardless of airport.

Alright, all is good now, thanks. I dunno if it was a server issue, but that profile attached here is/was definitely not what the iniManager downloaded.

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.