Cameron

That might fly on a product that isn't essentially more than "if this, then that". But, as stated, the CL650 is essentially a 1:1 replica of a real aircraft, including how the computers communicate and come to the results they do. There are SO many variables at play in a scenario that can occur, that the training in real life is many weeks long to understand the systems. Summarizing 7,000 pages is edgy and even then not an easy task. We are happy the Smartcopilot docs exist, and hope that gets people by (in addition to the Reflected Reality video series and more to come). In the meantime, we are not willing to play with fire from Bombardier, and I hope you can come to respect that decision. Thank you.

I'm not deflecting if I'm sharing our honest feelings on the situation. Take it or leave it; that's up to you. You have our side of the story, and we're sticking to it.

Happy to help, @judeb!

Captains, In the days since release of the Hot Start Challenger 650 there have been concerns that Gizmo and even the Challenger 650 plugins were causing a major performance impact. We went investigating this, and even got Laminar Research involved to understand what was happening under the hood of X-Plane to try and sort this out. As it turns out, Gizmo is NOT the source of problems, and neither is the 650 plugin; not directly, anyhow. What's happening is somewhat complicated, but I'll do my best to be descriptive, yet brief. X-Plane is programmed to use up all of your CPU cores in order to try and attain higher frame rates. In doing so, there's some major texture paging going on. The problem here is that it leaves almost no room for the Challenger to get its CPU operations done in the process, and mixed with a ton of texture paging, everything goes bust and tasks get stuck in a queue where X-Plane drastically slows down, things pause/stutter, and the experience becomes abysmal. If you happen to have your Plugin Manager open in X-Plane while this happens it will present itself as if Gizmo or the Challenger are using up an insane amount of performance, but this is actually just a mean trick when looking at it from a user perspective. X-Plane slows down so much that it LOOKS like our plugins are to blame as their tasks are not yet performed while X-Plane does other things. Before I go further, I should note, this is NOT applicable to everyone! Most customers here seem to have a great CPU/GPU combination that can handle all of this, but if you're one of the people on the struggling end of the spectrum, you'll want to keep reading this post! Version 1.1.0 of the Challenger 650 introduces a new installer that has a selection for GPUs with more or less than 6GB so we can best optimize your install for you. This will help with some of the VRAM/texture paging operations. That said, there's still more to the puzzle. Because X-Plane is using all the cores/threads on your CPU, it is not saving "room" for the Challenger 650 to do its operations efficiently and the CPU becomes oversubscribed. Laminar Research is likely to fix this issue for developers at a later date after X-Plane 12, so in the meantime we have a workaround to use that Laminar has sanctioned to give out to those affected. If you are affected by this issue, please do the following (this is for Windows users, as the issue seems most prevalent with Vulkan): 1. First, find X-Plane's application and create a shortcut so that we can create parameters. Right click on X-Plane > New > Shortcut 2. Right-click on your shortcut, and select Properties on its contextual menu to open the shortcut's Properties window. 3. The shortcut's Properties window is the place where you can add command-line parameters for that shortcut. Select the Shortcut tab and look for the Target field. 4. You will see a place that has the path to X-Plane labelled Target. X-Plane's path will be in quotes. At the end of the quotes, make sure there is a space after the quotes, then type/paste: --num_workers=n <== Replace the red 'n' with a number equal to three fewer processors/threads than your CPU has (this accounts for X-Plane's "main thread"). For example, if you have a 6 physical + 6 virtual processor CPU (known as Hyper-Threading for Intel and SMT for AMD) for a total of 12 threads ("logical processors" as Windows refers to them), you should put the number 9 in place of the red 'n'. Also be sure you have the TWO hyphens/dashes in front of "num_workers"! 5. You can now rename this shortcut to something like Challenger 650 if you like. That way you can just click this one when you know you'll be flying the Challenger. If you are unsure how many processors/threads your CPU has, go into your About Computer setting and Google your CPU model number to find out. Be sure to use the total number with Hyper-Threading/SMT (if enabled) as your starting point! We know this is a bit unorthodox, but we're doing our best to make whatever solutions we can for as many people as possible. Hopefully this makes your flying more enjoyable!

Makes sense. There hasn't been an update released yet.

Why would you call a fuel truck in the first place if you don't need fuel?

I think people are able to read and comprehend quite well. It seems to be you who is not understanding the matter being explained to you here.

Run the file you downloaded from X-Aviation. It's an installer. Whatever issue you're having is not likely to be resolved by a re-install. You're better off creating a topic to get help about it.

The product is essentially a 1:1 replica of the real aircraft. The real aircraft has 7,000 pages in their manual. Volume and copyright issues are a large part of this equation.

Hi there @VirtualCPT! I saw that you ultimately plan Mac support. Is that still on the table soon? This concept seems great, and I'd be willing to buy the hardware if we can get rolling on a Mac build.

There are quite a few topics on that in these forums, and I suggest you use the search function on these forums to find them!

https://support.torquesim.com/hc/en-us/articles/360057635513-Steps-to-resolve-plugins-not-loading-Error-Code-126-

You made two accounts with two different e-mails. Activate with the e-mail account that has your purchase in it. You will also need to re-install the Challenger.

No, it's not the same account at all.

You activated using an account that does not have a purchase for the Challenger.

https://discord.gg/5xK5Zdsy

The pace at which passengers arrive is random, as is the case in the real world. Sometimes it can be short, sometimes it can be long. There is a status menu you can pull up to see when their arrival will be. Have you taken a look at that?

Yes, ice build up will still occur. Just call de-ice up from the Ground Services menu. Automatically picks a 1-stage deice when not in precip, or 2-stage deice + anti-ice when in precip.

An update to this issue... We thought we had this pinned down as definitely an issue with Gizmo, but we have realized that is now not likely to be the case. It's a long story, but the short version is what Ben thought was a perf issue he had seen between retail and dev branch wasn't so much the case. We have a couple of operating theories on what's happening right now, but we need some data points to prove the case. For those of you that had experienced this, please PM me if I have not yet reached out to you on my own. Thanks!

Just ensure Gizmo from your plugins folder moved with your aircraft (or just re-install fresh from the 737 installer).

Great, and you're welcome. Enjoy!

In your log: C:\Program Files (x86)/Steam/steamapps/common/X-Plane 11/Resources/plugins/Gizmo64.plugin/win_x64/Gizmo64.plugin.xpl : Error Code = 126 : The specified module could not be found. You'll likely need to install this: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

Please attach your log.txt file from your X-Plane folder.

I've read. It is you who created a tone for text that contains none. Anyhow, I've just gone through your Discord history and see that you linked others in Discord to an existing thread on this. In that same thread we stated we needed no further reports, so we can close this now. Thanks! In the future, the going operating instructions are to search your topic, and if it does not exist, create a topic. CTD's are the exception to the rule.

Who actually said I was being snarky? I asked you a question.