akatham

Either turn off zink (in x-planes graphics settings), it is now enable by default in xp12.1. Or join the hotstart discord and ask totoro for the cl650 beta, which works with zink.

It looks like Gizmo is not yet compiled for the ARM architecture of the latest macintoshs. dlerror:dlopen(/Users/Shared/X-Plane 12/Resources/plugins/Gizmo64.plugin/mac_x64/Gizmo64.plugin.xpl, 0x0006): tried: '/Users/Shared/X-Plane 12/Resources/plugins/Gizmo64.plugin/mac_x64/Gizmo64.plugin.xpl' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/Users/Shared/X-Plane 12/Resources/plugins/Gizmo64.plugin/mac_x64/Gizmo64.plugin.xpl' (no such file), '/Users/Shared/X-Plane 12/Resources/plugins/Gizmo64.plugin/mac_x64/Gizmo64.plugin.xpl' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')) You might need to run x-plane in rosetta mode.

From your log: dlerror:dlopen(/Users/yyz342/X-Plane12/Resources/plugins/Gizmo64.plugin/mac_x64/Gizmo64.plugin.xpl, 0x0006): tried: '/Users/yyz342/X-Plane12/Resources/plugins/Gizmo64.plugin/mac_x64/Gizmo64.plugin.xpl' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')) Gizmo is not yet compiled for Apples new CPU architecture, you have to run X-Plane in Rosetta Mode for now. Probably during the update it got disabled or so...

You need to update the plane. You are using X-Plane 12 and version 1.6r1 of the plane. Only version 1.7+ is compatible with x-plane 12. Download a new installer from the x-aviation site and reinstall it.

What confuses me is that when you look at the apt.dat in "Custom Scenery\Global Airports\Earth nav data", it knows both runways: 1 496 0 0 ZHCC Zhengzhou Xinzheng 1302 city Zhengzhou 1302 country China 1302 datum_lat 34.51833333 1302 datum_lon 113.84 1302 gui_label 3D 1302 iata_code CGO 1302 region_code ZH 1302 state Henan Province 1302 transition_alt 9842 1302 transition_level 11811 1302 flatten 1 100 45.00 2 2 0.25 1 3 0 12R 34.5251835 113.8240699 0 60 3 1 1 1 30L 34.5135365 113.8582806 0 60 3 1 1 1 100 60.00 2 2 0.25 1 3 0 12L 34.5395420 113.8405590 0 120 3 1 1 1 30R 34.5271950 113.8768420 0 120 3 1 1 1 But the apt.dat in "Resources\default scenery\default apt dat\Earth nav data" does not: 1 495 1 0 ZHCC Zhengzhou Xinzheng 1302 city Zhengzhou 1302 country China 1302 datum_lat 34.518333333 1302 datum_lon 113.84 1302 iata_code CGO 1302 icao_code ZHCC 1302 region_code ZH 1302 state Henan Province 1302 transition_alt 9842 1302 transition_level 11811 100 39.93 2 2 0.00 1 3 0 12R 34.52516285 113.82401520 0 60 3 1 0 0 30L 34.51350724 113.85825800 0 60 3 1 0 0 And even when download the latest scenery from the gateway (which also has both runways) it still won't load the stars, so it still reads the obsolete data from the second file?

Getting the same error, and it is a problem with the default G1000, so not TBM specific. It seems that x-planes default navdata/scenery has a rather old version of that airport, which does not contain RW 12L/30R, so it does not know that runway. And having navdata with arrivals/approaches that contain said "unknown" runway seems to confuse the G1000/x-plane.

The airplanes you have mentioned all have different avionics, could you try to load the star into a default plane with the G1000, for example the Cessna 172 G1000?

Well, the fuel man is covinced that Alaska belongs to Canada. Known bug.

Don't use time acceleration, it messes up the systems of this plane as it calculates many things in real time. If you want to cheat, instantly realign the ins by study->ins->realign irus immediately in the challenger menu.

Press this switch:

Another user had similar problems, he fixed it by setting the visual effects to high (in the x-plane graphical setings, the hud needs hdr to function correctly).

Another user had similar problems, he fixed it by setting the visual effects to high (the hud needs hdr to function correctly).

It says in your log that you are using ShadeX. (It and reshade are known to screw up custom rendering). Can you try and remove it temporarily (not just disable it via the plugin menu, move the folder out of the resources/plugin folder to a temporary position with x-plane closed and start x-plane)?

Is this the new "my ashtray is full, i need to buy a new car"? Bloody throwaway society...