LukeFF

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. 🙂

I downloaded the scenery this morning and enabled it through my mods manager and deleted the default one before starting a new flight, but the new scenery isn't showing.

PC

Hmm...it might be worth it then to make that more clear on the store page, as it says: "Custom maintenance functions: Engine oil levels, APU oil level, Hydraulic fluid level, wheel brake wear and tire wear." That makes it sound like it's more than just visual, and I know all along people on various sites have been under the impression that it physically changes the performance of the plane.

When we reached the next waypoint, instead of continuing on towards the next one we starting flying around in circles. It was then I realized the plane was no longer in heading or nav mode and needed to be manually steered back on course.

I'll try to remember the next time I see it, yes. In the meanwhile, it's the text in the DME readout area - it looks like a Z-fighting issue, where multiple layers of numbers are trying to be rendered at the same time.

Maybe, but it's been so long now I don't remember. 😄 But I've made a mental note to keep an eye out for problems with this in the future.

When starting a new flight from your typical parking spot, there is typically an excess of ground service equipment around the plane - 2 GPUs (the one that spawns by default with the plane, plus the one that is part of the airport scenery), etc. If the player is using GSX, it would be nice if these "extra" pieces of equipment would be culled out somehow so there isn't this cluttered mess when I start a new flight.

The other problem with this is that when I look for an available parking spot, all spaces are listed as too small. So, while I've disabled the message from appearing, this other problem remains.

After I activated my secondary flight plan and reactivated NAV mode, the FMC went into Manual mode when we reached our next waypoint. I had to input a Direct To Waypoint procedure to get us back on course. Is that how it should be?

In both aircraft.cfg files, there is a typo in the following line: icao_manufacturer ="Aibus"

I've noticed the following buttons have no associated sound with them: Glideslope warning test (just to the right of the captain's altimeter) The VHF 1-4 buttons on the pedestal

I've noticed in some videos that some people have inHg on their EFB takeoff performance page, while I cannot get it to change from HPA to inHG via the Settings screen. Is this issue still being investigated?

A few of your temperature knobs are set almost all the way to the Cold setting.

When landing at KMEM on runway 27, I received no DME signal from the ground. The frequency is supposed to be 108.7, course 273 degrees. Could someone check and see if it is working properly or if something is indeed wrong with it?