Goran_M

The airways in the flight plan are built using the default G1000 code. ie. Always been there. V speeds require far more calculation on Saso's part, due to having to take into account several factors and implementing a boat load of more math. Making it compatible with Vulkan/Metal is taking priority at this time. As for your other comments. Taking the yaw away? We had people screaming for it to be reduced, as it was deemed too unrealistic and exaggerated. We consulted a TBM pilot and engineer and we received feedback, which was implemented. Some people don't like it, and some people do. What can I say...we can't make everyone happy. Absolutely no texture resolution was sacrificed in exchange for improving framerates. Framerate improvement came from further code optimisation. I don't think I've seen anyone ask for WORSE framerates and higher texture resolution. The whole point of a TBM 900 is to actually make it less difficult to fly than, say, a TBM 850, by way of more automation and less clutter on the panel. It's supposed to be easier.

X-Plane 11/Output/preferences

Does the joystick show up in your hardware calibration screen?

Will need to see your log.txt file. Also, make sure you’re not using 11.50.

I'm suspecting something in the script is interfering with the joystick. There is nothing special associated with the controlling of the aircraft, so I doubt it's something associated with the TBM. Have you tried temporarily disabling or removing flywithlua, and then testing it again?

Without access to your computer, there is nothing more I can do. Something on your end is definitely preventing the install. We've had many people download the new update and install it, as you may have already seen in the forums, and they have had no issues. You can try installing on a laptop or some other secondary device you own, or, if you choose to, ask for a refund from X-Aviation support. As a last resort, are you perhaps trying to install it on some kind of virtual machine?

An update just came out. Did you try that yet?

Support is very limited on X-Plane beta's, but this looks like an OpenGL issue. The best I can do right now is forward this to Saso and he'll look into it for when X-Plane gets out of beta. For now, I would recommend to staying with 11.41 with the TBM.

Not that one. It simply reads log.txt.

Could you post your log.txt file (found in the root X-Plane folder.)

This section of your log has me very concerned, as it appears to be a hardware issue (specifically, RAM). I can't say for sure. I've referred this to Saso, and maybe he can make more sense out of it. Someone will post back soon.

You have something trying to connect to some kind of server but it's failing to connect. This is when the crash happened. Not sure why the TBM is involved. I'll pass this one to Saso and see what he makes of it, but in the meantime, can you double check what plugins you might have that are trying to connect.

We're not quite there yet in supporting an internal beta build.

We'll need the log.txt file from the root folder, also. Usually, an engine fire on load is caused by faulty terrain data. You might want to try again at a default airport to see if it happens again.

http://forums.x-pilot.com/forums/topic/14834-general-aviation-hot-start-tbm-900-paint-kit/

Check if you have accelerated wear turned on

The installer will uninstall the old version for you.

Catalina user right here. Toolbar visible. If your other plugins have stopped working, that is an almost 100% certainty that the problem is on your PC. Gizmo does not interfere in any way with other plugins. So if they have stopped working, it looks like some kind of permissions issue on your Mac.

Do you have any kind of anti virus running?

It is impossible that the installer is causing this, otherwise we would have complaints of this happening every single day from new customers. The only reason an install would be interrupted, that I can think of, is something blocking the download. We do know that many anti viruses block Gizmo (false positive). This has happened to me. In your case, I honestly can not think of what is causing this. Even Cameron is puzzled. If you want to wait for the update, you're more than welcome. Here is an invite to our discord server, so maybe you can ask Saso (username totoritko) for any help regarding this. I've already shown him this thread, and he's also puzzled, but perhaps you can go through a few steps with him. https://discord.gg/m3qRsz

You didn't delete the state folder. Are you sure it's not in X-Plane 11/Output/TBM900/state ? If it isn't, the install didn't complete. In any case, there is something definitely on your system preventing this install, and without access to it, it's difficult to diagnose. Do you have a laptop you can install it to?

X-Plane has always had issues with pop ups, in some cases, about co ordinates on scaled resolution. The only solution to this for now would be to set scaling to 100%.

Can you post screenshots of what you're seeing? Also, a screenshot of the resolution of each monitor would also be helpful.

The G1000 in the TBM uses the underlying default G1000 for flight plans. So anything to do with that would need to be sent to Laminar, as it's very likely a bug they need to take care of.