Cameron

The hope is to eventually bring it in with XP 12 if it allows, but we don't know if that's possible yet. As the EVS could be retrofitted after delivery, it wouldn't shock me if they shipped it on the panel, but I don't actually know if they do. I just know that we originally intended for it and couldn't make it work with X-Plane 11, so the controls were modeled. @Goran_M will know more about that.

Hi there, This error is a result of you not running the latest version of the Challenger 650. You'll need to download and update the product from your account.

Hi @Paul_P28A, It's almost definitely this: https://support.torquesim.com/hc/en-us/articles/360057635513-Steps-to-resolve-plugins-not-loading-Error-Code-126-

There are intentions for this, but as to when is unknown for the moment. We have been in contact with the team though.

On the first page of this topic

Please attach your log.txt file in your X-Plane folder after opening the M20 in sim.

https://discord.gg/J56w9t2g

It was not forgotten. That is an optional add-on, and is not on all 650's from the factory. A google image search of the 650 will probably show you right away that most any 650 does not have this. The camera is infrared for the EVS (Enhanced Vision System), and It provides images of the approach, runway lighting, and of terrain scenery that's viewed on the pilot's HUD and on the co-pilot's multi-function display. It was considered for the add-on, but determined not something that could be implemented due to limitations in X-Plane.

Can run at 30Hz, yes. But the actual MONITOR max refresh rate being 30Hz? Rare as can be in the X-Plane user world, or really even in general. Most monitors are at least 60Hz.

As I remember, I had originally told you about V-Sync being a likely culprit. Gotta be honest, you're the first person I've met with a 30Hz monitor. I think you're going to find yourself in a pretty slim group.

X-Plane does not draw the avionics in full screen mode, and so the simulation pauses. You must be in a 3D mode view. You cannot do what you're trying to do here. You can use the 'w' key to look ahead, and then adjust the height of the camera up or down to only show the bottom glare shield.

I should add, that usually happens on AMD cards when using Vulkan. It's an issue in their drivers. Switching to OpenGL will resolve it.

I'm not familiar with that. What is it?

Matt, Can you ensure that you have the properly desired speakers set as your primary/default in Windows Sound management? I have seen Windows get weird with that before.

@jcmc1405 Those settings are WAY too high for a 1070, especially with the 650. You are absolutely asking for trouble there with your AA, Filtering, and Texture Quality settings. Reflections also take a ton of compute time for little gain. It is no wonder at all you're having issues here. I suggest you move Texture Quality to High, AA, Filtering, and Reflection down to none, and gradually work your way back up. This is just way overloaded.

I mean that the decision to re-visit this when we feel appropriate will not change. That was our answer. You need to accept it, or move on some other way. I answered that. We don't know. At the least a couple of months, as already explained above.

Not quite accurate, but I don't care to get into it. We'll just call it a matter of experience. Honestly? In the context of this conversation and our answer, It really doesn't matter. There's no sense in hashing this out because the decision is not up for change. Na, not really. We're talking less than 1% of the customer base here. Just being honest about it.

How did I know you were going to ask this? You're just predictable, I guess. Honestly, we don't know. There's no time on any of this stuff, and we certainly didn't make promises to it as a feature. The time comes when we feel the 650 is fully stable for everyone and bigger code base changes are appropriate. That's definitely not right now, or even likely in the next month or two.

It's honestly not the priority right now. As @Goran_M said, it'll be revisited at the appropriate time in the internal roadmap. Now is not that time.

@Orlando Cuesta You have not purchased this product. Enough said.

The only versions allowed active at this time are 1.1.2 and 1.1.3 for the TBM. Anyways, we definitely will not be supporting going "back in time" on versions. Supporting older, buggy software is not helpful to progression. Bugs you then find could be associated to other bugs already squashed in a later version. The whole point of version numbers is to move forwards, not backwards. Eventually everything gets worked out.

That's actually not true.