Leaderboard

Hello All, This will serve as a formal forum announcement that we have released the version 1.1.13 update for the TBM 900. All customers who have purchased the TBM 900 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the TBM 900 from today forward, your purchased download will already be updated to version 1.1.13 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php  2. Find your original TBM 900 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: Improvements / New Features: Aircraft will automatically default to the X-Plane experimental FM Performance improvements to panel rendering code should result in less CPU time being eaten up every frame. Integrated new GCU478 keypad commands for stock G1000 integration. Migrated to new OpenAL 1.21.0 build to resolve some issues with the Default audio device sometimes not being detected properly on Windows. Added option to disable popup clickspots in VR under "Configure Visual Effects". Added support to blink the MIC light on the audio panel when using xPilot. New command mappings INI for RSG hardware. Bug Fixes: Window centering would sometimes cause a window to appear off-screen. LOC/VOR arming could crash due to a NAN value being attempted to be filtered. Additional hardening against somebody engaging stock X-Plane autothrottle. Reduced engine oil quantity life, because we should be burning oil a bit faster. Increased engine oil quality lifetime, the oil should last a LONG time. TAS system hardening in case NAN values are returned by X-TCAS. Bottom TCAS antenna wasn't touching the fuselage. Engine torque display on EICAS wasn't correcting for X-Plane TP engine model quirks. Nav data parser wasn't compatible with new X-Plane 11.50 navaid format, breaking the localizer receiver. DME range wasn't being displayed AoA indicator was black Rain effect should work under Vulkan (might require selecting "Low"). Incorrect logical inversion could wreck havoc in autopilot CDI switchover logic. MacOS: Bumped macOS deployment target to 10.13, since 10.12 is no longer supported. Fixed rain effect not appearing in the right eye in VR under Vulkan Fixed the HUD bleeding through the glareshield. UI scaling would break rendering in the Maintenance Manager. Mac build would crash due to querying non-existent OpenAL context for error information Mouse interaction with the oxygen mask wasn't correct when using UI scaling. Librain fix for ice effect flickering in the left eye in VR. Climb/cruise torque bugs aren't supposed to go away when gear deployment signal is missing. Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.

O dear, I tried loading it five times. Four times directly from X-plane menu: Immediate CTD before loading; Fifth time, first load scenery with default Cessna, then load TBM9: Immediate CTD. Attached flies are X-plane's Log.txt and the mac os x crash report. Further specs: Mojave 10.14.6 on an iMac Retina 5K, 27", end2015, 4GHz i7, 32GB, AMD Radeon M395X 4096MB (no "TBM900_Log.txt" because of early crash) --> Log.txt --> macosx_crashreport.txt edit: The 6th time I repeated loading the Cessna, then disabeling plugins: Terrain radar, World Traffic, WorldTrafficRadar, XRAAS to check out if multiple TCAS-using plugins might be the culprit. Result: with all those plugins disabled also: Crash to Desktop. __ All the best,

Thanks, I did not know about the apt.dat file, that was the piece of missing info I needed. Looking into this solved an other problem, turns out the Toliss A319 did not had a database problem, it looks if the runway is long enough, if not you can not program the mcdu. I just tried the beta version of gizmo, but It did not solve the gizmo crash. But I leave it like it is for now, before I change things to get worse I am very good at that

Here my vote too for p-factor +1

At the risk of starting a flame war, my 40 years of experience as an IT guy taught me that in terms of reliability & compatability, AMD's "walk" never seemed to quite match it's "talk". Personally, I run X-Plane on an Intel 10700K (not overclocked) on a Gigabyte Aorus MoBo with 64GB RAM - no plugins - and ... everything just works (with the exception of the occasional glitch). Take that as you see fit.