Cameron

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.

This error is a clear indication that you are NOT running the latest version of the installer.

I'm sorry it's making you frustrated, and thanks for sharing your feedback.

It is in no way our intent to support or provide support for older versions in a new software release run. If you have issues, please use the forums to provide feedback and support to resolve any issue in this or a future release.

What aircraft will you be flying at your school? If you want a good trainer, I would recommend this: https://www.x-aviation.com/catalog/product_info.php/take-command-sr20-g1000-p-195

I think X-Plane sounds like the most suitable option for what you're looking for.

This actually sounds like an unactivated Challenger. Did you not update to the latest version?

That was in reference to some tests we did and discussions with Laminar about the use of DDS and PNG files, and how the texture pager differently interacts with them. PNGs are slower to process, and they must be re-fetched from disk. This slows things down and causes a stutter. It's a piece of the puzzle for objects that get "killed" when you're not looking at certain angles (like facing forward in the cockpit, but not at the engines). When you pan the camera in these situations, there is a momentary pause while X-Plane has to go all the way back to disk and fetch the files again. We solved that situation by providing DDS files, which are already compressed and contain mipmaps. In other words, no, he was not referring to Gizmo.

I think you're referring to something that was thought prior to our discussions with Laminar about the CPU/GPU texture paging situation. Gizmo is not at fault, as has been explained. There was a topic elsewhere here where someone suggested some other plugins can cause these stutter drops as well, like the Skunkcrafts updater. May be worth doing an audit on your plugins just to see. FlyWithLua and anything SASL based would be a good start.

You should be using '6'. All this said, the CPU core count is a workaround to a limitation problem in X-Plane, not a magic fix for a bug or hardware that's just barely getting by minimum specs (if that). You appear to be running the Challenger 650 on a laptop CPU, which is going to be throttled and have issues keeping up with anything trying to work it hard. A 1060 video card is further holding you back, especially as a laptop variant. I'm not even sure the Mobile version of the 1060 meets the minimum required specs of the GTX 970 we have posted on the product page. Your computer specs are simply probably not going to cut it.

Probably not for a couple of weeks, maybe 3.

Replay with custom datarefs requires work that has not yet been put into the product. This really isn't a bug. It's just not implemented for now.

Updating is fine and helpful. Frustration is understandable, but please don't take it out on the forums for people already trying to assist.

Let's settle down a bit. No one is ignoring this. Rome wasn't built in a day.