Cameron

Hello All, This will serve as a formal forum announcement that we have released the version 1.1.0 update for the CL650. All customers who have purchased the CL650 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the CL650 from today forward, your purchased download will already be updated to version 1.1.0 for you. IMPORTANT! Some customers have experienced performance issues where FPS in sim got very low or unflyable. If this has happened to you, please read the following on how to handle the situation: NOTE: This update brings the simulation of gear pins and probe covers. Be sure to conduct a proper pre-flight check of the aircraft to avoid issues with retracting the gear or air data. For more information, please watch the following videos: https://hotstart.net/cl650/pins.html https://hotstart.net/cl650/covers.html https://hotstart.net/cl650/chocks.html What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php  2. Find your original Challenger 650 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: New Features: 2264: Added oxygen refill feature 2263: Added oxygen service gauge 2266: Implemented fire extinguisher bottle servicing 2334: Implemented replay support of doors and switches 2339: Implemented animating chocks during replay 2375: Implemented gear pins 2375: Added physically simulated probe cover flags 2393: Added downscaled texture version for GPUs with less VRAM 2404: Added a new hint window at the top of the screen to help with potentially missing preflight 2418: Added and animated window shades with drag manipulators Documentation: 2383: Included training scenarios document in release documentation package 2384: Updated "Expanded Normal Procedures" and "Operations Reference" docs with latest copies from Graeme 2385: Engine start checklist hint image needs to instruct pilot to push boost pumps back in before starting left engine 2386: Flight compartment checklist hint image 42 needs to mention combined IGNITION message, not two separate ones 2387: Flight compartment checklist hint image 66 needs to mention ATS and NAV arming 2388: Auto-install stock failure scenarios into Output/Failure Scenarios Bugfixes: 2239: Setting landing lights to on should also turn on the taxi lights 2240: Don't allow manipulating probe covers mid-flight 2242: Ice detector wasn't taking its cover into account in determining ice accumulation 2252: Truck hoses and cables weren't showing up in sim 2249: Cabin Environment Study window, text error. 2245: Ground elec power access panel sometimes didn't close when removing ground AC power 2255: Activating a new SID in the air can crash if the departure waypoint is an airport and has the DIR-TO-FROM flag set 2259: ASU hose wouldn't disconnect if the ASU was shut down and the airplane moved 2260: AFCS VS PID needs to respond a bit more slowly, to avoid overshooting the VS target 2261: Airframe manager was reporting spurious distances when reloading a nearby state 2269: FL alert must avoid triggering if a baro switch causes a bump-up in altitude 2273: Do not exclude non-IFR airports out of the airport database 2281: FMC aiport database shouldn't exclude airports with only grass runways 2284: Airportdb could crash if it encounters an airport with no name 2285: Typo on refuel-defuel study window labeled left main tank as right main 2287: HOLD page FIX ETA line should be populated any time we have an ETA to the waypoint 2288: PAX DOOR STOW should show when T-handle isn't stowed, not when T-handle cover is left open 2293: IRS units fail crossing antemeridian / international date line 2304: TSS isn't resetting X-TCAS output ops resulting use-after-free crash during soft reload on boot 2312: Crash due to phys lock assertion fail 2316: When an airport is part of an FMS flight plan or simbrief route, the route parse will fail 2317: Regmark object needs to be separate with Outside lighting mode to allow the logo light to illuminate it 2318: Bus short circuit failures weren't working 2322: Wind component indication on MFD DATA NAV STATUS page was reversed from actual components 2330: Need to control X-Plane default light datarefs to get the beacons to show spills in sim 2328: CDU LW =/= MFD LW 2291: CBP-4 No animation on line C 2333: Entering a distant waypoint into final descent could crash due to bad altitude computation 2340: ALT hold function shouldn't be affected by baro setting changes 2344: SPKR volume button on ACP isn't lighting up when pushed in 2345: FAA charts provider didn't work on Windows due to CA list not being configured 2338: Crash when entering FBO: assertion "mgr->filenames[active] != ((void *)0)" failed: 2305: Crash after deleting a standalone HOLD at the end of a procedure 2342: Crash during datalink upload of flight plan. Crash occurs in error reporting code 2336: DEP/ARR crash 2325: BRT and OFF labels are in the wrong positions on lighting controls 2313: Entering excessively low ISA deviation on PERF INIT page will crash due to negative fuel burn 2314: Nose light spill missing 2354: Don't lock out 112.00 MHz, it's VHF channel 57X 2352: ISI is still prone to "toppling" 2359: Refueler should also be using US gallons in US territories outside of the contiguous States 2360: Takeoff and landing computer should round weights to nearest 100s to avoid non-obvious VSPEEDS DISAGREE 2361: Automatic transition from ALTS CAP or ALTV to ALT captures the wrong altitude 2358: NRST APTS page crashes when it encounters a non-ICAO airport 2364: LNAV might turn the wrong way on a course or heading intercept leg 2366: N1 split or overspeed should put ATS in DISENG'D, not FAIL 2376: Duplicate dataref registration in abus wire is causing a crash when datarefs are accessed in DRE 2380: APU hobbs isn't set on initial load if the APU ECU is powered down 2381: Using default X-Plane checklist command binding crashes 2394: If IAPS breaker pops due to FCC overload, it can enter an inescapable excessive power-draw-reset state 2395: FMS elevation should be using GPS HYB INS elevation so LPV approaches work correctly with misset altimeter 2398: AC UTIL BUS 2 was labeled as "UTIL BUS 1" on AC synoptic page 2400: Operating the T-handle shouldn't be possible while the locking handle is up 2349: CTD when starting new flight. 2401: libswitch can crash on init if replay worker thread isn't initialized before first floop call 2367: Modifying SEC LEGS causes crash when PRI has legs 2410: FREQ CONV breaker was permanently popped out and couldn't be manipulated 2411: Hidden not-yet-functional oxygen flow indicator on cockpit oxygen mask panel 2412: Reanimated main door curtain to avoid clipping through its cover door 2413: Left ACP integral lighting was non-functional 2414: Closed up holes around control columns on cockpit floor 2415: Fixed animations for right side ADF1 and 2. Fixed VHF3 on left side 2416: Added PA selection on ACPs 2417: Removed extraneous latch from lavatory door 2419: Re-animated misaligned rudder pedal on Pilots side 2421: Fixed manipulator not animating for door pull-up assist handle 2424: Fixed white halo around text on cabin side panels Improvements: 397: Missing cabin speaker chime for SEAT BELT and NO SMOKING signs. 2244: Engine start hand signal should check for the presence of probe covers 2253: Write back to X-Plane to override windshield icing datarefs to prevent spurious windshield icing 2251: Ship a default outdated GPS almanac for people who are in geo-blocked countries and cannot fetch new almanacs 2256: Fueler should knock if he's trying to get in but the door is closed 2258: Added rudimentary XP systems bridge to force avionics_on and avoid network client sound issues 2262: Increased ground effect a smidge to match closer to real life landing attitude 2265: Yokes need to be upscaled by 15% 2271: Sync up X-Plane barometer setting to ours, so Vatsim clients like xPilot report correct baro altitude 2270: After detecting online flight, don't revert to temperate effects until landing 2275: Disable checking the weight-on-wheels flag in X-Plane TCAS data as libxpmp doesn't set it right 2294: TEMP COMP should default to OFF on a new airframe 2319: Increased the size of the beacon spill to 4m 2341: Need PA position on ACP mic selector 2343: Added support for simbrief PBD waypoint specifications in XP11 flight plans 2346: Regmark appareance editor needs an option to hide the automatic regmark for custom painted ones 2348: Tires take too long to spin down on their own 2357: Write back engine running status into X-Plane ENGN_running dataref 2382: Implemented CAS takeoff and landing inhibits 2390: Drop AFD and HUD drawing priority to low on Windows to help prioritize X-Plane on overloaded CPUs 2391: Apply texture downscaling to objects that got missed in authoring 2399: Implemented remaining fuel on NRST APTS page 2402: Prevent parking brake from being selected without first pressing down the pedal brakes 2405: Surrounded cockpit and cabin in null manipulator to prevent clicking through to exterior manipulators and vice versa 2406: Made all manipulators on exterior panels simple click toggles instead of drag 2407: Hide main door pop-out clickspot when the outer door handle is rotated 2420: Added black areas behind external service panels when the door is closed to prevent light shining through 2422: Fixed Wood texture having excessive grain and increased glossiness 2423: Added current customs sticker 2425: Added animated door locking indicator next to T-handle Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.

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.