skiselkov

@Claus87 That's an X-Plane crash, not something we caused: 0:00:21.612 E/SYS: THREAD FATAL ASSERT: PING-FILE ERROR! <- crash due to a texture load error 0:00:21.612 E/SYS: THREAD FATAL ASSERT: setjmp(png_ptr->jmpbuf 0:00:21.612 E/SYS: THREAD FATAL ASSERT: Aircraft/X-Aviation/TBM-900/objects/CP_Top.png

When you use the MFD mark T/O mark, you'll end up almost perfectly in trim:

Please don't second-guess how built the plane by looking at the raw dataref output. T/O trim doesn't mean "center trim". That is a deliberate decision. The real aircraft doesn't have a "center trim" button, so neither does the model. That is a normal tendency with high power and negative angle-of-attack, which is a common state in cruise. On a clockwise turning propeller, you will encounter a left-yawing tendency at positive AoA and a right-yawing tendency at negative AoA.

@Claus87 Your machine's real-time clock seems to be somewhat erratically skipping back-and-forth. I've built an experimental version of the GPWS code and I'd like to ask you to give it a try. The ZIP is attached. Unpack in the plane under "plugins" (move the old "OpenGPWS" out of there and back it up somewhere). OpenGPWS.zip

This is definitely a bug in our code. It's being triggered when LOC mode is armed without a localizer being received. As a temporary workaround, make sure you are receiving the localizer before arming LOC mode. We will have a fix for this in the next build.

Can you please post the Log.txt generated by the simulator while attempting to load the plane? Any time you post a support request, the log file is a key piece of information we need to even begin the process. Please be a bit more specific. What did you try and what did or didn't work?

Apologies for this, the server infrastructure that supports shared airframe functionality has a fault that is causing this message. We'll get this fixed and let you know.

Must be a livelock somewhere in the multi-threaded charts UI renderer. I'll investigate. Thank you for the report.

@ilankrt Ignore those messages about drivers. You have a Mac. You don't update your drivers manually, Apple manages drivers for you inside of macOS.

I'm afraid this one's not one of ours. It was caused by some other plugin doing something related to "DownloadAirportFiles". I can't tell you which plugin it was, except that it wasn't us. The filename "mac.xpl" is a non-specific plugin name, which means the plugin doesn't use modern v3 fat packages (otherwise you'd see the exact plugin name there, which in the case of the TBM would be "systems.xpl").

We're aware of this one. It's caused by X-Plane UI scaling (set in graphics settings - UI scaling above 100% causes this).

The buttons are push-on-push-off and are persisted between reloads. Also, the right button is independent of the left, so be sure to check you didn't depress it as well. Display backup mode turns on if EITHER of the buttons is pressed in.

I'm thinking you might need to scroll the little FMS knob to make the altitude turn blue on the pre-programmed waypoint, then hit ENT. I believe it's a quirk in the Laminar G1000. Nothing we can do about it, unfortunately.

@the_papy I'm not familiar with the Global Traffic plugin. What our TAS computer looks for is the following datarefs: sim/multiplayer/position/plane<N>_x sim/multiplayer/position/plane<N>_y sim/multiplayer/position/plane<N>_z As long as Global Traffic populates these datarefs, TAS will detect these planes and provide traffic advisories. So it's more a question for the Global Traffic authors to add proper traffic position integration.

Here's the issue: 2019-10-11 10:09:18 xtcas[wav.c:224]: Cannot init audio system: device open failed. You have something weird going on with your audio setup in Windows that is causing OpenAL to fail to open your audio target device. Are you using some kind of software audio router like Voicemeeter?

Also, are you by any chance running a debugger attached to X-Plane?

What's weird is that only very rarely (once in your logs) do we seem to visibly crash (as in, we actually get told there's a crash). In most other instances, the application simply quits without a trace, truncating the log file. That leads me to suspect something else might be forcibly causing us to exit. Do you have any kind of anti-virus software installed? Thinking if it might be triggering a false positive. If you do, try disabling it and see if that changes anything.

Good point, we'll add the option as well.

This is an assertion failure inside of X-Plane's FMS code. Please report to Laminar with the log attached. They seem to have a bug in there that is setting the GPS course variable to an invalid angle.

From the best guess, this looks like a crash inside of X-Plane's core code: EXCEPTION_ACCESS_VIOLATION <--- This means X-Plane attempted to read invalid memory Backtrace is: 0 00007FF641E9DA30 C:\Users\GregR\Desktop\X-Plane 11\X-Plane.exe+0000000000A6DA30 () <--- This is the offending code that caused the crash If it were caused by our code, it would say "systems.xpl" somewhere in the stack trace. Since I only see X-Plane.exe there, I suspect it's been caused by X-Plane itself.

We'll add this feature. ATM the "random" location is actually given by your mouse cursor location. Popup windows are designed to appear right underneath your mouse cursor. But we'll add the ability for them to simply retain their previous location.

We are investigating if this might have been caused by XP11.35.

Sorry for the late response. It's an issue we're aware of. Will fix in next update.

@Chris5353 The issue you are seeing is caused by your GPU driver being extremely old, probably somewhere around version 314. Drivers this old cannot load the TBM's complex rain effect shaders due to lacking support for OpenGL async compute. Go to https://www.nvidia.com/en-us/geforce/geforce-experience/ and install that program. That'll make sure you have the latest driver installed (checking on nvidia.com, that should be version 430). After that, the aircraft should load without issues.

@2Fat2Fly Sorry for the delay in delivering this feature. Navigraph charts support is absolutely in our TODO for the MFD. The AviTab solution was just an interim "quick fix" until I have time to sit down and crunch through the complexities of the Navigraph integration API. However, rest assured, we will be adding it.