LukeFF

When configuring Stanstead, button for Nool doesn't respond correctly - it just renders some half transparent tooltip text that is unreadable. Also results in the airport having both Nool and GSX screens rendered on top of each other.

Also, to add: with the current configuration, it looks like the GSX VDGS screens conflict with the ones that come with the stock scenery. I experimented with this at gate 14, which gave me a purpleish looking number on the screen and info from what looks like the GSX screen. Scenery index clearing did nothing. Looks like there is some sort of issue with configuring this properly in the app.

You can also see the problem here on your store page, upper right-hand portion:

Also checked to ensure there is no other installation on my hard drive, and it does not exist anywhere else that I am aware of.

Double-checked, also uninstalled and reinstalled the scenery, and deleted the scenery indexes. Problem still persists:

It seems the Nool VDGS installation option in the app doesn't work (the black button). When clicking on it, some sort of tooltip text vaguely flickers, but nothing more.

Still there after this latest update 😞

Disable the stock scenery.

If I click the Line Select key next to Zero Fuel Weight on the Init-B page, it is populated with a value that does not match what is on the EFB. This often results in the MCDU saying the cruise altitude is above the recommended maximum.

Yes it's unfortunate it's not like with the Fenix.

nope

As with some other sceneries out there, the taxiway signs are blurry and unreadable until you are practially passing them in your aircraft.

Agreed, this one is strange with stop markings with BATC.

I do that as well but it's still a problem in my opinion.

Yes, it works fine.

Unless I was hallucinating when I read those patch notes initially, I distinctly recall it being there in the list. Was it removed? 🤔

Bump

This seems to be a widespread problem with numerous sceneries across multiple developers right now.

Bump

Bump

Bump

Doesn't really answer my question - if the plane is importing wind data from the Simbrief flight plan then something is wrong. If it's coming from MSFS, then sure, yes, maybe it's right. Would be nice for iniBuilds to clarify.

Disable your fuel mixture commands.

SU4 beta issue

This also extends to the MCDU - on the initial loading screen, the engines are listed as CF6s.