Goran_M

You might be surprised at the built in redundancies of the CL650. It simply won't let you do certain things beyond limits. There have been some people in our discord asking for failures, so we will likely revisit that some time in the next few weeks/months.

We're still considering that for a future update. The only thing is, the 650 is extremely reliable. And the vast majority of Challengers spend maybe 200-300 hours in the air, per year. Nowhere near enough to warrant any kind of major repairs due to wear and tear. We do have a very comprehensive failures module, where you can set failures in, if I recall correctly, several hundred different areas. But it's completely manual. But, like I said, we'll look into that more in a future update. Not complex enough.

Sure, you can if you wish. TBM900log.txt and log.txt. Would be handy, just in case.

I'll make a note of that and run some tests. If anything needs to be done on our end, we'll address it once the 650 is out. There'll actually be a few TBM updates we're going to tackle over the next few months. One of which will be XP12 compatibility.

Yes. But not in the initial release. Yes that’s all in the fully featured FMS, just as it is in the real plane.

The HUD and synthetic vision, and their compatibility with Vulkan, has been addressed in the last update and is now working. Are you referring to something in particular?

This is certainly something we haven't come across. It looks like you're loading some kind of space shuttle scenario based on your preferences. Try clearing out your preferences folder (X-Plane 11/Output/preferences) and reload X-Plane. Don't delete the contents. Just move them somewhere outside the X-Plane folder. Reloading X-plane will rebuild the files, bhowever, you will lose any calibration and X-Plane settings you previously made.

I’ll cover one or two initial liveries, with more following over the coming weeks. You’ll find this add on very beneficial. We consulted with three 650 pilots who were very particular about all the systems. I have plans for quite a few paints. Just to add to @Pils, all sounds were recorded off a real 650 by one of our testers. Thanks Ryan.

I’m making it on the same spec Mac you have, and it runs very well.

I'm also looking to make a Substance Painter file for the painters who want a little more control over certain areas. For example, matte or gloss. Metallic, non metallic, etc...

The REGA variant, including cabin, will come out as a free update after initial release.

Yes

There will be a free update for XP12.

Check that the CTOT is not armed. Other than that, I can't think of anything that would make it do this.

Nothing is sticking out at me in your log. If this happens again, check your maintenance manager for a list of damaged components.

SCIP is an airport on a small island. It's many developers "test" airport. I'm afraid you'll have to go to my final suggestion. Download another copy of X-Plane without scenery, and test in there. It's almost a guarantee that another plugin or plugins is not playing nice with the TBM.

This is definitely something to do with your VR setup. The textures for the panels are at their maximum size (4096x4096 pixels). I don't own a VR setup, but you could try checking to make sure all drivers are up to date.

Make sure you've activated the TBM. If it isn't activated, the crash bar stays down.

You have an awful lot going on in that log file. Here are some thing to try off the bat. Try these in the order I post and test after each. Run X-Plane in Windowed mode. (There is a bug in the AMD drivers on Mac's and Windows PC's that cause crashes in full screen mode. There is nothing anyone but AMD can do to fix this, and LR are aware and have also contacted AMD for a fix). Remove XJets and Skunkcraft updater. Test the TBM at SCIP. Failing all that, download another copy of X-Plane without plugins and scenery. Install the TBM and test again in windowed mode. Don't worry...this will have no effect on the activations of the TBM if installed on the same computer. Post back any findings.

You can quit the sim at any time, and it saves the state of the aircraft. When you load it up again, it'll ask you if you want to start again or resume. Keep in mind, you'll need to set the engine to "start with engines running". Sometimes, it can be a little buggy. We're working on that.

Please post a screenshot of what you see and a log.txt file.

Datarefs fall into different categories Indicators - (A heading indicator that displays the aircrafts current heading) actuators - (The knob on an autopilot heading dial that changes the heading bug and commands the aircraft to follow a specific heading) (Also some are writeable and some are not. Some are ratios...0 to 1... and some are booleans...negative numbers, 0, positive numbers) And then they can fall into the different types of systems air driven gyro electric AHARS Whenever you see a "TBM" dataref, it's a custom dataref that is code driven. a "sim" dataref is a default dataref that comes with X-Plane. In some cases, the TBM uses default datarefs, because many of those work very well. To answer your questions, 1. a dataref that is an actuator can absolutely trigger a sequence of events that trigger and activate indicators, and if there is code attached, they can also trigger other actuator datarefs. 2. actuators and indicators, yes. In most cases. 3. 1 triggers the next, and then the next, and so on. (I hope this answers your question).

I've passed this on to Saso (who coded the systems), and he or I will get back to you. This will require a little bit of figuring out, as we don't "officially" support this configuration.

You have quite a lot of plugins, and my suspicion is that those, combined with the TBM, is what is giving you performance issues via some kind of conflict. My suggestion is to remove all 3rd party plugins, then testing the TBM. Once confirming there are no performance issues, replace your plugins, one at a time (testing each time) to determine which plugin is causing the problem.

I just checked on my iMac, which also uses Monterey. Consistent 48fps (give or take an fps). Can you post your log file so we can get a closer look at what's going on?