Leaderboard
Popular Content
Showing content with the highest reputation on 02/11/2022 in all areas
-
The Challenger can be hard work on the approach and landing, but when it all comes together it's very rewarding. All the beta testers had difficulty learning how to land, it's all part of the fun. On approach be aware that unlike aircraft like the 737, the pitch response to power is reversed, that means a power increase will see the aircraft pitch down for a moment. This can lead to an oscillation developing, so be sure to fly the pitch attitude accurately. If you find you're wobbling up and down, aim to make smooth power changes, and remember the HUD flight path vector is useful tool, but can get you into trouble too. A useful check is 0.6 on the AoA index on approach. If it's higher than that, you're too slow. Remember Vref +5, and check your weights on the approach ref page. For the landing flare, lift the nose to to arrest the rate of descent, starting at just below 40 ft. Make a smooth power reduction and fly the aircraft onto the runway. The pitch attitude in the flare is around 3 degrees, but look at the end of the runway, not the HUD! You'll have plenty of time for butter later, so for now put the aircraft down positively in the touchdown zone. If you go butter hunting, you'll only find little bounces - ask me how I know! Once you've landed, extend the flight spoilers (the ground spoilers are automatic, but the flight spoilers need to be raised by pulling the lever), use the reversers and you're down. And stay away from that HLIS button, it'll trick you into making your landings worse!1 point
-
Hi, I had an LUA script running crew callouts for another aircraft, I've expanded to include the Challenger and decided to release it to the world Challenger specific: Takeoff calls: setting power, vSpeeds, positive rate. Autopilot On Setting and calling Climb Thrust Approaching set altitude Intercepting the ILS Landing call for reverse, or no reverse if you forget to arm them... Available in the X-Pilot repository or direct from GitHub.1 point
-
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!1 point
-
Version 1.2
177 downloads
This livery is of the latest addition to the fleet of 412 Squadron of the Royal Canadian Air Force. The Challenger 650 is designated as the CC-144D in the RCAF inventory. The example that is the subject of the livery, 144620, was delivered to the squadron on 30 June 2020. 412 Transport Squadron is based in the Ottawa, Ontario in Canada’s National Capital Region. The squadron maintains a three-hour notice-to-move posture 365 days a year in support of Government of Canada and Canadian Armed Forces global transport requirements. Though primarily known for VIP transport, the CC-144 Challenger is also capable of command-and-liaison and emergency medical evacuation roles in support of CAF operations. The squadron operates two different Bombardier CC-144 Challengers: the CC-144C (civilian model 604) and the CC-144D (civilian model 650). The squadron is part of 8 Wing Trenton and is based out of the Pilot Officer John Gillespie Magee, Jr. Annex at Ottawa's MacDonald-Cartier International Airport (CYOW). The Annex is named for a 412 Squadron Spitfire pilot who wrote the highly popular poem “High Flight”. Check out the customization of the FBO reidentified as the PO J.G. Magee, Jr. Annex. If you don't want the custom FBO textures, remove the following files from the livery Objects file: FBO_002.png FBO_Decals.png FBO_Labels.png A YouTube video of the aircraft leaving the Bombardier factory in Montreal may be viewed at:1 point -
Version 1.0.3
606 downloads
This livery for the fabulous Hot Start Challenger 650 is based on a real world CL604 registered as VH-JII. I hope you'll enjoy it. To install simply copy the "VH-JII" Folder into xplane directory/Aircraft/X-Aviation/CL650/liveries Don't hesitate contacting me if you find errors or have suggestions in improving this repaint. Please do not redistribute this repaint without my permission.1 point -
Version v1.4
117 downloads
**Updated 01/04/2022** CrewPackXP is a FlyWithLUA utility designed to add some crew communications for aircraft in X-Plane 11. This includes basic callouts, and in some cases assistance from the PNF in high workload phases of flight. Settings can be adjusted to enable or disable the whole plugin, or just certain features of each aircraft. Flight Factor 757 / 767: - Virtual FO to pre-flight aircraft - Take-off and Landing calls by both crew members - Flight Attendant PA's - Ground Crew positioning of equipment - Virtual FO assistance with go-around procedure Hot Start Challenger 650: - Virtual FO to pre-flight aircraft - Take-off and Landing calls by both crew members Source Code https://github.com/N1K340/CrewPackXP/tree/main/src Documentation http://crewpackxp.readthedocs.io/ Changelog New features and bug fixes are listed in the change log. Installation Copy the Scripts and Modules folders into the main folder of FlyWithLUA: > X-Plane 11 > Resources > plugins > FlyWithLua Once enabled, the First Officer should announce his entry to the cockpit roughly 15 seconds after loading in. CrewPackXP settings can be accessed via the X-Plane menu bar: > Plugins > FlyWithLua > FlyWithLua Macros > Crew Pack Settings Prerequisite This plugin uses the FlyWithLUA plugin to interface with X-Plane. It is available freely from [X-Plane.org](https://forums.x-plane.org/index.php?/files/file/38445-flywithlua-ng-next-generation-edition-for-x-plane-11-win-lin-mac/) Luna INI Parser (LIP) is included as an additional plugin module for use with FlyWithLua. This module allows for the saving and reading of settings data within LUA. It has been included in this package under the MIT Licence offered by creator Carreras Nicholas. This is a common plugin; it may already exist in your modules folder causing a prompt to overwrite. Usage The CrewPackXP functions run autonomously based on in sim events, provided the aircraft is enabled within the CrewPackXP settings. Refer to each aircraft's entry in the manual for details on settings and features available. Disclaimer / Feedback This package is to be distributed as Freeware only under the GPL v3 license. This is the first time I have coded a plugin, any feedback is welcome. Bug reports, please include the x-plane log.txt file in the main x-plane folder for the flight in question. Acknowledgements Carreras Nicholas - Luna INI Parser (LIP) 'Togfox' - FSE HUD 'X-Friese' - FlyWithLUA Plugin 'mkultra44' - Documentation proofing Current Script Versions - Flight Factor 767 - 1.4 - Hot Start CL650 - 1.41 point -
1 point
-
Thanks, I think I get it now, where ever the CL650 is parked, the FBO will try to draw itself in that immediate area. Makes sense now.1 point
-
In the future please always create your own thread for crashes so they don’t get overlooked. I’ve done this for you this time.1 point
-
1 point
-
Right. Clearly people are assuming that I'm telling the author of the aircraft what to do. But I am not. What I am doing is pointing out that whether this is the best option or not is highly dubious. I shall stay away from it because its technical lead is a highly erratic toddler.1 point
-
1 point
-
you need to have commands.txt and datarefs.txt in your CL650 folder, so SpadNext can see the commands and datarefs for the CL650. datarefs.txt commands.txt1 point
-
DId I demand it be made to work? Or did I simply ask, why is this thing, which is supposed to be a going thing, seeming so not around and evanescent? It gives off well, an unpleasant first impression. You have heard about first impressions? They have them wherever you find yourself? The answer to this question is a bunch of loud-mouth idiocy from this Ben person. What a winner. Let's look at all the places where you were a jerk on this board. There's dozens of them. Guess what, when everyone else is the problem, it's you.1 point
-
I’d say it’s best to consider modifications to this file as “at your own risk” for the time being.1 point
-
There is no documentation for the file. As you've seen it's mostly self explanatory. The FO actions and checks are coded into the software and triggered by the XML so it's a case of copying the actions you want. You can see a text-to-speech checklist with the quick turnaround checklist, where the others have voice files.1 point
-
I need to re-upload the cockpit file to work with the VRConfig - won't get chance today but will do it tomorrow. The VR config will still work for everything apart from the 3-position switches until I update the file.1 point
-
1 point
-
Hello All, This will serve as a formal forum announcement that we have released the version 1.3.1 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.3.1 for you. IMPORTANT!: This build might not recover avionics & engine settings for saved states, so it should not be used to reload an in-flight state that was created by prior versions. On-ground states should be safe to load. You will need to re-create any in-flight states you previously had. REMINDER! 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: 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: 2503: Need a dynamically drawn placard on the MIP to show the registration, MSN and other info 2532: Implement direct wind component specification format on PERF INIT and LEG WIND pages 2616: Implement screen backlight bleed effect 2638: Add standard exterior placards and markings 2315: Add support for single combined forward/reverse axis (TCA throttles) Bugfixes: Visuals: 2509: MDC panel backlighting should be deleted 2510: Fix overhead annunciator text for APU PWR FUEL and MAIN BUS TIE 2448: LWD and RWD text on aileron trim panel is too close to switch and is hidden by the cutout in the panel 2450: Texture error on toilet door 2511: Fixed center pillar to cover top of sight alignment 2512: Smoothed out tablet holder 2513: Fixed Z Thrashing on screws of rear CB panel 2514: Darkened overhead annunciator textures and made the LIT's a richer color 2636: Overhead vent used for cockpit entry out of position 2639: Flipped direction of window blinds on all cabin windows except for the emergency exit window 2640: Enlarged manipulator for glass cover on fire buttons Simulation: 2470: ADG manual deploy signal cannot be reset on the ground 2462: Flashing STALL on PFD during STALL test 2491: OpenGPWS connection failure in phys_init causes a subsequent crash in error handling 2495: Map cursor doesn't account for magnetic variation in PPOS mode when copying coordinates to scratchpad 2477: Crash when entering a hold at a waypoint requiring the WPT SEL screen to show 2497: Doing a regular waypoint insert on the HOLD AT page should switch to the matching LEGS page 2500: Fixed protruding hinges on nose gear door 2501: Closed minor gap on fuel panel display 2505: Closed very minor gap between wingbox and fuselage 2494: Fueler dialog popup is lost if fbo phone is answered 2506: Forgot to delete GLsync objects after use, leading to persistent memory leak and eventual crash 2508: CA and VA legs mustn't be allowed to reduce to zero length to avoid sequencing issues from intercept legs 2517: Read back of speed limit value on VNAV SETUP uses incorrect feet-to-meters conversion 2518: MCT and APR should be selectable as normal thrust modes 2519: Selection of TGT on THRUST LIMIT should show in cyan 2524: AUX-to-MAIN transfer needs fatter pipes to keep up with single-engine ETOPS operation 2525: Leg join computation can fail on DF legs if the leg is zero length 2529: Increase wing tank ram air temp effect a bit to counter excessive fuel chilling 2531: APU NEG-G SOV isn't correctly inhibiting APU fuel flow 2534: In the air, FPLN PRAIM should show PRAIM CHECK CANCELED 2541: Idle thread prioritization appears to be dangerous in Rosetta on MacOS Monterey 2544: SEC PERF is not selectable on pages other than page 1 of SEC FPLN 2548: Right latch on APU service panel door isn't holding the door closed 2527: Crash on reselecting taxi lights checklist item after Shutdown checklist completion 2538: VFLC FMA speed needs to be magenta 2550: Engine oil pressure transducers weren't properly hooked up their electrical power inputs 2551: Deleting on a hold to an enroute DIRECT leg deletes the entire route line 2562: Boost pump INOP light shouldn't come on in flight on a running when pushed in 2559: Osrand issue generating auth request for Navigraph on Windows 2564: Switching EICAS reversion to BOTH PFDS, the CAS on the L MFD is not replaced by a red X 2561: Popouts don't restore size/position when reentering cockpit 2565: DC BUS 1 and DC BUS 2 CAS messages aren't being posted if the respective TRU is unpowered on the ground 2566: DC ESS BUS and DC EMER BUS CAS message trigger conditions weren't correct 2568: CAS trigger conditions for ESS TRU 1|2 FAIL were incorrect 2570: Incorrect trigger conditions for AC BUS 1|2, BATTERY BUS and EMER POWER ONLY CAS messages 2571: Trigger condition for APU GEN OFF message wasn't correct 2582: Database lookup page counter retained from sub-pages 2567: TCAS ALT TAG and TRAFFIC fields blank on new airframes 2585: FMS plan file containing a destination approach keeps throwing BAD ROUTE PARSE 2589: Retune CPC PID to be less susceptible to entering a self-amplifying oscillation 2557: VNAV misbehaviour when shortening an arrival. 2597: Navigraph chart common to multiple procedure variants might not be picked up automatically by the IFIS charts feature 2591: Overbanking results in erroneous RA readout 2516: Contrails still showing even with engine shut down 2599: Make the dialog tree popup window follow out of VR when the headset is removed 2603: SEL WPT page doesn't properly set up its subpage counter if the total number is less than 2 2607: Going direct-to an internal airway leg causes the subsequent airway legs to be dropped 2606: Connecting a STAR into an IAP starting with a hold duplicates hold turn direction into connecting leg 2608: Pushing YD DISC should trigger monitored AP disconnect with continuous cavalry charge 2609: Aural tones shouldn't be cancelable by pressing the Master Warning/Caution cancel button 2610: Once a monitored AP disconnect has occurred, the only way to silence it is using the AP DISC button on the yoke 2611: Shorten the AP disconnect cavalry charge to roughly two chirps 2621: FIX copy-back of the intersection off of VORTACs wasn't using the correct magnetic variation 2623: libhud is susceptible to crash on an internal assertion failure when a GL error was generated externally 2630: Modifying vertical constraint value shouldn't change constraint type if there's already one there 2631: Don't show VOR ID on PFD bearing data when associated DME radio is in HOLD mode 2632: Don't show bearing distance and ID on the PFD if it's the active nav source Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.1 point
-
Version 1.0.0
370 downloads
N604PS is a Challenger 604 previously operated/managed by Delta Private Jets until Wheels Up bought Delta Private Jets in 2019. The aircraft is now managed / operated by Wheels Up. Painted here for the superb Hot Start Challenger 650. Please do not modify and reupload/redistribute without contacting me.1 point -
That's an X-Plane limitation unfortunately. Because the aircraft is an "interior" object and the ground services are "scenery" the aircraft always takes priority. It's really annoying, and the developers did their best to find a way round it, but for now it's not fixable. If you use exterior camera you won't have this - it's only walk mode / interior camera that has this effect.1 point
-
another quick update. Not much has changed since the last report, except I'm a whole lot further along on my MU2 project than I was at last report. X-Plane is still full time work for me and I'm making steady progress towards returning to this guy. Jan is standing by for the aftermath of the MU2 release when we jump back onto this guy full time and work the FMC and other 3D for a good while I'm sure. I suspect we'll be back on the IXEG by the summer months. -tkyler1 point