LukeFF

When using GSX, I have both the GPU as provided by GSX and the one that comes with the A300, at the parking stand. Is there a way to remove the GSX one so only the A300 one is rendered?

This was with an FSLTL-inserted plane:

Huh, that is really weird. Not that I'm trying to change anything, but I was just curious what sort of parameters had been set for the cargo area.

In the screenshot below, the Agent 1 and Agent 2 switches can be moved up and down without moving the red guards out of the way first.

I just noticed the A310 manual is twice as long as the A300 manual because the former has the (very helpful) expanded procedures checklist but the latter does not. Whenever a manual revision is done, could this please be added?

Bump! 🙂

It was with the default GSX profile that can be downloaded through the iniManger app (the full-detail one, not the "lite" version). The error message showed up in the cargo area, namely in the ramp spaces marked 601-609 (can't remember the exact one, but it was one of those).

When opening up the GSX editor, I see an error message about "parkings not being found in navdata."

West of Terminal 2B, this parking garage has trees growing through it. Also, the signage for it is very low-res:

It remembers tire, oil, and brake status but not where you landed. Little NavMap is helpful for that.

That's up to Microsoft.

The north cargo parking area - where FedEx parks - is extremely dark at night. It needs a lot more lighting intensity.

As noted here, there is still a typo on the plane's name for both models: https://forum.inibuilds.com/topic/21975-typo-in-aircraftcfg-files/

The last time I checked, all three liveries for FedEx are missing the registration and SELCAL info in the cockpit. In other words, the panel on the pilot's side of the cockpit is blank.

I've seen this too.

Yes, at this point, what is the purpose of the wear and tear if I can just slam the plane onto the runway and use the maximum braking possible every time, and there is no negative consequence?

When using the clock in chronometer mode, it shows only 2 digits instead of three. I was over an hour into this flight, but it was showing only 2 digits, not three.

When checking the DC battery voltage, the animation of the indicator needle is jumpy - it doesn't smoothly increase and decrease as the pilot moves the selector knob.

Yes, I'm going to live on the edge and see if deleting both the landing challenge and the airport causes any issues. 😄 I think that all along that was the problem - since the airport wasn't installed the game was wanting to download all this extra content that was missing.

I do see that is a thing with some of their marketing materials, so maybe it is alright:

It looks like the signage on one of the jetways is partially cut off:

Finally got my copy of MSFS up and running again, with the iniBuilds airport in place, but I am not touching anything with the Asobo one for now. I did a check and didn't notice any issue with having both airports installed at the same time, so there is at least that - the iniBuilds one is fully rendered as expected.

So, the thing is that I did uninstall it from Content Manager, but it's still giving me problems. Would the associated landing challenge also cause issues if that is installed but the Asobo airport is not? I am just trying to get out of this cycle of downloading content when everything else in the game is up to date.

So, after I installed this airport yesterday, MSFS has suddenly decided I need all of these mandatory updates. What happened is the following: Downloaded the iniBuilds JFK airport and enabled via Addons Linker. Uninstalled the stock Asobo JFK airport. After that, suddenly MSFS said I needed these mandatory updates and after I downloaded several gigabytes of them, I was told on the main screen there were essential updates I needed to add, even though my content manager shows no such updates needed and my game updated to the latest version. Long story short, I performed a clean reinstall of MSFS and everything looked to be back to normal, until about 30 minutes later it started over with the same original problem. So, right now I am in the midst of reinstalling another 130 GB of updates. So is it coincidental or would the uninstallation of the stock JFK cause all these issues?

Thanks guys - I've not tried again, but I did use the Layout Manager tool suggested on Discord and that fixed the problem. 🙂