Leaderboard

View File Hot Start Challenger 650 NetJets Livery This repaint is made for the payware Challenger 650 by Hotstart. This paint was taken from a variety of close-up photos of the aircraft. Installation: To install, just extract the liveries file to: .......\X-Plane 11\Aircraft\X-Aviation\CL650\liveries Optional if you want netjets specific extra's extract plugins folder content to: (WARNING IT WILL AFFECT ALL LIVERIES, BACKUP THE FOLDER OTHERWISE A FRESH REINSTALL WILL BE NEEDED TO REVERT) .......\X-Plane 11\Aircraft\X-Aviation\CL650\plugins Start the simulator and enjoy!! Side notes: If you have any issues missing the QS, on the FMS on the Tuning page 2 you can add the QS in Flight-ID If you want to use aspects of the livery in your paints you must credit this one or myself & John if your will be publicly downloaded. If you like the livery, feel free to leave some feedback and if you spot any errors, please do point them out! Matteo & John Submitter pilot_matt Submitted 01/11/2022 Category Hot Start Challenger 650 Livery For https://www.x-aviation.com/catalog/product_info.php/take-command-hot-start-challenger-650-p-212?osCsid=redmukm7he79lo2ou63juv11s1  

Note: this is already integrated directly on Simbrief (see above) so the link below now only exists as a backup. LINK HERE Note: aircraft name is clipped to 12 characters for custom airframes, sadly (limit does not apply to default profiles). Fixed by SimBrief Based on the already-accurate default CL60, with the following adjustments: equipment codes and extra flight plan remarks kindly provided by Graeme_77 here: OEW/BOW updated to match the Hot Start airframe without passengers (12,315 -> 12,556kg, includes two pilots) passenger weights updated to somewhat more closely match the randomized weights as simulated, going with 74+15kg so you can still carry 5 passengers+luggage and full fuel at MTOW if you are flying Kim Dotcom around (supposedly ~141kg or thereabouts), sorry, you will have to make adjustments, or just count him as two passengers see below for more information: Don't forget to add extra crew (anything above the two included in OEW) as passengers when planning your flight! Cheers, Tim

I'm hoping to have it out by midnight Friday 14th GMT+10. This will give everyone a weekend update and hopefully "peak enjoyment".

Might want to think about replacing or re-charging the cockpit fire extinguisher. No-go item

Please do not redistribute our cockpit object file, or any other files in the CL650. The obj files undergo constant changes through updates. Please, just post the self made vrconfig file, with instructions on how to implement it. I don't have any issues about vrconfig files being created, as long as there is a disclaimer stating that the file is not officially supported by X-Aviation, Hot Start or LES. If you want to modify the cockpit object file, please contact me directly, either though these forums or on discord, and I'm happy to work with you to help create one. If I have it in my blend file, I can export it with each update, so your one doesn't get overwritten. The very first update will have major changes to the cockpit object file.

Hello, Thank you for bringing this to our attention. I have reproduced this behaviour on my system and will log for fixing. Kind regards,

When the fueler comes into the cockpit and ask how much fuel is needed, I sometimes accidently clicked "Tanks full" or "Pump this many liters" (before selecting an amount). Therefore, I think it would be nice if confirmation was required. This is already the case when calling the FBO for example and asking to prepare a van after arrival.

Nose wheel steering only controls the nose wheel up to 55 degrees of deflection. When steering is not engaged, the nose wheel can castor up to 99 degrees each side. If the nose wheel is deflected further when the “NOSE STEER” switch is set to ARM, it will not engage and the CAS will display an amber “STEERING INOP” message. In order to recover nose wheel steering, the nose wheel must first be brought back within 55 degree deflection. This can be achieved by taxiing forward a bit. Steering can then be engage by cycling the NOSE STEER switch to the OFF position, then back into the ARM position.

As promised (in case anyone still cares), here's links to the profiles I developed while beta testing this aircraft. These were my personal choices, and you're free to do with them what you will. For example, I really only use Xsaitekpanels for the radio panel and the trim wheel on the multi panel, everything else is on the Bravo. Edit 2022-01-21: I’ve added the AP buttons (not lights!) to the Xsaitekpanels by request. Edit 2022-01-22: Added AP lights and knobs to Xsaitekpanels. Displays are not possible at this time. https://github.com/pilsnerish/Xsaitekpanels-Configurations/blob/main/CL650_xsaitekpanels.ini https://github.com/pilsnerish/Honeycomb-Profiles/blob/main/CL-650.json However, I suggest referring to the following thread for a much more complete Honeycomb profile kindly provided by @Goodfixins.

A few pilots are having issues with AUX TANK HEAVY messages. This is totally understandable as (A) we didn't tell you how to work the refuelling system and (B) Good grief - never let a pilot near a refuelling truck! The docs will be reviewed to see if something better can be written, in the mean time... Refuelling - Easy Method Tell the fueller how much fuel you want. He's going to say "I'll start up the pumps". Wait for him to go downstairs, then only switch the L WING and R WING shut off valve (SOV) on. Check the OP lights (OPen) indicate. The fuel values are pressure operated, no refuel pump pressure, no valves open. The open setting on the switch can also "time out" and the valves won't open even when pressure is applied, so watch the panel until the valves indicate open. The wing tanks will fill, the HL (high level = full) lights will indicate and the fueller will tell you he's done. If you don't have enough fuel, tell him to keep pumping, and this time open the TAIL and AUX valves together (always together - note the white line on the panel between TAIL---AUX indicating they work together. Again, watch the panel until the valves indicate OP. If you don't have all the open lights on, the fuel balance between aux and tail will be incorrect. When the fueller finishes this time and you have enough fuel, close the SOVs and switch the fuel switch off. You cannot defuel in the simulation, it's virtually impossible in the real world outside of maintenance operations. If you want to help the fueller out, you can work the pump yourself using the menu Challenger 650 \ Ground Services \ Refuel \ Refuel Truck. It's fairly simple, like a fancy gas pump! The pump symbol at the top left of the display indicates the pump is running. Start and Finish are the only buttons you need for basic operation. But I've still got AUX TANK HEAVY when refuelling on the ground! Did you land or start refuelling with a significant amount of fuel in the aux tank? You may need to balance the aux and tail fuel when refuelling to keep the aircraft in trim. To do this, ask the fueler to start the pump, on the refuelling panel switch only the TAIL SOV to open and then press and hold the override button. With this button you have great power, but also great responsibility - be very careful! Refuel with the override button pressed until the AUX TANK HEAVY message disappears, then resume normal fuelling if required.

Hello Everyone, I think I set up everything for the approach, but for some reason I'm getting a NO APPR error on the PFD and the plane would not pick up and follow the LOC and GS. Am I missing something? According to the FMS guide it should be automatic. B the way, where can I find the Quickstart guide? In the documents forlder I have 5 PDFs neither of them is a QS. Thanks in advance

Edit: SimBrief now has added MACH 0.74 and MACH 0.72 cruise profiles to their CL60 profile, so the discussion below is mostly irrelevant now. I've requested that SimBrief add an LRC cruise schedule to their CL60 profile if possible, to make it easier to plan range-topping missions such as London to New York westbound: https://forum.navigraph.com/t/cl60-cruise-schedules/7076 In the meantime, the most economical profile available is MACH 0.77. For those who have access to the actual fuel tables for the CL60, is there a way the LRC cruise could be expressed as a fuel factor relative to MACH 0.77 cruise, let's say over a ~3,500-3,600nm air distance? SimBrief's fuel factor will also apply to climb and descent, but over longer ranges this matters somewhat less. I guess, for planning purposes, we would have: a fuel factor that applies to a specific air distance we would scale said fuel factor based on actual air distance (either linearly or using another recommended method) Regards, Tim

Whilst shutting down this evening, the First Officer was diligently reading the checklist aloud and I was completing the required items. At the point in time where the APU generator was turned off and the aircraft was running only on battery power, the First Officer just... Stopped. Whilst I understand that the checklist was displayed on the FOs MFD and that this is unpowered from the battery, it seems a but abrupt that the FO would just 'stop'. Surely he would have a paper copy of the checklist for the remaining items..?

I'm sure this is because I don't understand something! Was flying EGBB > EGPB, FL270. Selected ILS27 as approach whilst on ground at Birmingham. During the cruise, looking at the EGPB approach charts, I decided to add a hold at SUM at the end of the route before the CI27 from the start of the approach sequence. I wanted the aircraft to calculate a TOD to get me to SUM at 5000' so I put 5000A in the scratchpad and added it to both SUM and the hold at SUM. I expected that the MFD VNAV window would therefore show me SUM as it was the next waypoint in the flight plan that contained a altitude restriction, but it seemed to only want to show me what it had shown originally which was the FF27 altitude of 2100'. As I passed KOKAL I did get a magenta 5000 in the PFD so I set 5000 in the MCP and made sure VNAV was armed. Got a TOD chime and a magenta diamond on the glidepath indicator showing that the desired path was above me - however the diamond never descended and then I noticed the green TOD marker was behind me on the map so I went manual at that point and VS'd myself down. All a bit of a mess - where did I go wrong?

If it happens again, I'll try my best to give steps to reproduce, but I'm honestly not sure how I did this. The only way I can reproduce this is to manually set a PCU jam failure and reset that failure through the failure menu. I restarted X-Plane and that removed the CAS message associated with the failure menu, but not the indications on the synoptics page. To remove the entirety of the failure (CAS and amber synoptics), I had to shut down the aircraft fully, removing AC and DC power. Once I powered on the aircraft again, I had normal indications on the flight controls synoptics page.

With the help of severniae, the VR config file has been modified to allow for better VR manipulation of switches, knobs and a few additional hot spots. I have attached the updated VR config file to drop into your CL650 aircraft folder. Should you want to have the pressure manual alt 3 way switch to work properly in VR (overhead panel top right of the aircraft red switch), You will need to go into the Cockpit OBJ file and change the following. locate the similar text and replace it with the one provided here. (The x/y/z was changed a bit to allow for the proper manipulation) ATTR_manip_command_axis hand 0 -0.050000001 0 CL650/overhead/press/man/alt_up CL650/overhead/press/man/alt_down Manual Altitude Select. If you don't do this, you will get a VR config file error, but it won't impact anything. You can just click understood and keep it moving. Please note the DISCLAIMER, the file is not officially supported by X-Aviation, Hot Start or LES CL650_vrconfig.txt

Let me explain why I think this mode should be kept and expanded to allow saving states: Yesterday, I was doing some practice approaches using saved career mode flights. Today, I wanted to fly a "real" flight. But my career mode state was set in the weird way the plane was left after my most recent practice approach. If non-persistent mode worked the way I would argue it should, then these different uses could be totally separated.

She is not present in the product. We just can't get over how bad people look in X-Plane, and until the following are supported it probably won't happen: 1) deformable meshes 2) skeletal animation 3) subsurface scattering

Yes. That's how it happened on the TBM too. The community helped Goran and Toto a lot.

Since we are all trying different things it might be good to compare two different files. I develop on Linux but fly VR on Windows so was looking for something similar to what I use on Linux. I use Notebook++ to look at files on Windows and found that there is a plugin for it called compare that seems to do what I was looking for. Hope this help in our quest to make this a even better VR aircraft.

I am definitely not an expert, but I think hitting FLC will tell the plane to descend immediately. When I setup for VNAV, I simply set the desired altitude that I want to descend to (the plane will honour restrictions, so I usually set it to the base altitude on the final approach if I am offline), leave everything else alone (plane is usually LNAV1, ALTS or similar with ATS on and VANV button activated) and one the plane hits TOD, it begins to descend. Very similar to the 737 behaviour in my experience. Again, I think the FLC will cause it to descend to the dialed-in ALT immediately.

Hi Ed! Thanks for the report. I believe your issue was that you entered "5000A" -- "at or above 5000ft". Therefore, the VNAV solver starts at your most restrictive constraint (the @2100ft one for CF27), then projects the 3° profile back. 5000A doesn't require the solver to put you at 5000ft, but anywhere above that, so it won't show in the VNAV window, because VNAV is not aiming for 5000ft, just checking that whatever profile it comes up with passes SUM above 5000ft. If you want to make sure that VNAV gets to SUM at 5000ft, you can just enter "5000" as the constraint, and once you do so it will show up in the VNAV window. I hope that makes sense!

You are in SPEED mode which is indicated by the blue marker on the speed tape and SPEED in the ATS display, it’s also only set to 127knots. The ATS display should show N1-TO if you were in the correct mode. edit I’m too slow too lol

How do you start the TCAS test? Thanks!

Ok found it. On the CDU: TUNE and then click on the squawk code with nothing in the scratchpad. Test is on the upper right of the page.

With respect to audio I am seeing a special thing with the CL650 as well. Often (not always) when I load a saved state volume is at zero, when bringing it back to higher volume all is fine. This only happens with the CL.

Move the Field Of View slider until you are happy with the view, it’s just at the bottom of your screenshot where it says field of view.

In non-persistent mode there’s no FBO to tell how many pax there are so you use the X-Plane weight & balance interface to set the payload (and only payload, don’t touch fuel!). In real life you don’t magic people into existence by typing into the FMS so you don’t in this simulation either.

that's hilarious, they modeled a bad fire extinguisher.

Thanks. I think there’s a piece of the puzzle missing because I set up this curve like yours, tested it in the default 737 while watching datarefs you mentioned and it worked, however the same dataref changes didn’t happen in the 650. Hopefully there’s some obvious switch in Plane Maker that they can find.

After some consideration, and after reading your post, I’ve decided to allow it. Feel free to edit your post and re-attach the file. But please add a disclaimer that we don’t officially support it for now. For more permanent changes, please get in touch with me so we can collaborate.

Thank you!

When I hear the gong for TOD, usually 1 minute out, I simply activate VNAV, FLC, and set the Altitude to the base of the descent (where the approach alt starts). Once you do that, then if ATS is on and profile is setup for approach, it will throttle back to M.72 (default) and start the descent.

Avionics switch on Honeycomb Alpha fixed this exact issue for me.

Excellent report. Reproduced & fixed in next update.

Uploaded a new version as someone brought to my attention the throttle reverser and idle/shutoff bindings were missing from the original. See post above

Yes indeed. Will be fixed, sorry for not spotting that before release.

"Pressure altitude" is the altitude on a standard pressure setting, i.e. what the altitude would indicate if the QNH was 1013 hPa. https://skybrary.aero/articles/hot-and-high-operations

That's not your "electrical connection" door - the AC GPU plug-in point is further up the fuselage near the nose. That's your fuel, there is no way to close in the air. It is your responsibility to ensure all doors are closed prior to departure.

No, not necessary for the IRS to be aligned, it's just a radio link. If you find yourself somewhere with no VHF datalink, you will need the GPS system to be working in order to utilise the Inmarsat datalink, as the antenna inside the vertical stab/tail has to actually steer to track the satellites, but this is a bit of a fringe case. (And yes, it's simulated too!)

Not an error. When you press the start switch the pack valves close automatically, and reopen when the start cycle is finished. Just like an Airbus. You can also see this behaviour on the Study window for the Bleed system.

I agree. At the moment the FO is essentially tied to the MFD checks. Future enhancements to the FO reading the checklists are being discussed, but no promises or timeline. The paper checklists are available in the documentation folder and via the Avitab plugin.

Fixed the blocking issue with dev branch just now. Need to sleep on it, then review for packaging... Shouldn't be too much longer.

Thank you for the reply, I wouldn't look down on someone reporting things and keep them as simple sim pilots. I have flown sims for 20 years and professionally in real life over 10. None on the aircraft that I've flown IRL doesn't behave like that. None. FD shouldn't be part of pilots movements but the other way around to be were APFD-system wants it to. I haven't flown with ProLine21A plane but I highly doubt that it should work like that.

View File Hot Start - Challenger 650 - Bombardier House Livery This is the Bombardier House livery for the Challenger 650 by Hotstart. The reg use is the C-GZKL. Some details are missing, see it as a WIP. Happy Landings Submitter Meilstroms Submitted 01/09/2022 Category Hot Start Challenger 650 Livery For https://www.x-aviation.com/catalog/product_info.php/take-command-hot-start-challenger-650-p-212  

You're welcome. For anybody else wondering what is actually being discussed here, it's the flightplan equipment codes that indicate the aircraft navigation and communication capabilities. M-SBDE1E2E3FGHIJ1J4J5J7M3RWXYZ/LB1V1D1 M Medium Wake Vortex Category S Standard Com / Nav Equipment B LPV SBAS D DME E1 FMC WPR ACARS E2 D-FIS ACARS E3 PDC ACARS F ADF G GNSS H HF Radio I Inertial Navigation J1 CPDLC ATM VDL Mode 2 J4 PDLC FANS 1/A Mode 2 J5 CPDLC FANS 1/A Inmarsat J7 CPDLC FANS 1/A Iridium M3 ATC RTF Iridium (Aircraft Number on FPL) R PBN Approved W RVSM Approved X MNPS Approved Y VHF 8.33 Channel Spacing Z Other Equipment L Mode S Transponder with ES B1 ADS-B Out via 1090 ES V1 ADS-B Out via VDL Mode 4 D1 ADS-C with FANS 1/A PBN/A1L1B1C1D1O1S2T1 A1 RNAV 10 (RNP 10) L1 RNP 4 B1 RNAV 5 all permitted sensors C1 RNAV 2 all permitted sensors D1 RNAV 1 all permitted sensors O1 Basic RNP 1 all permitted sensors S2 RNP APCH with BARO-VNAV T1 RNP AR APCH with RF (special authorization required) DAT/1FANSER2PDC 1: FANSER Primary: CPDLC-DCL and en route clearances. 2: PDC Secondary (will be used if primary is not available) SUR/260B Compliance with RTCA DO-260B (Minimum Operational Performance Standards for 1090 MHz Extended Squitter ADS-B and TIS-B RSP180 Aircraft is authorized for Required Surveillance Performance RSP180

For me the flickering comes and goes. I've found that a view change (exterior then back to interior) can "reset" things for you so that the flickering may go away. I've also found that manipulating screens can cause the flickering to go away.

Yes they are, and we should have put them in the Operations Reference doc. Sorry about that. PBN/A1L1B1C1D1O1S2T1 M-SBDE1E2E3FGHIJ1J4J5J7M3RWXYZ/LB1V1D1

Before this turns into another FS vs XP thread, I'll say we've got the FS2020 SDK, and we know what is going into it. And that's where our information will stop. All I want to say about this is that FS2020 is a flight sim. X-Plane is a flight sim. Both have lived and grown alongside each other for the better part of 2-3 decades. MSFS development has stopped once or twice in those 20-30 years, but it has never had an effect on X-Plane to the extent of "Laminar will go out of business." Use whatever you want to use. It's up to Laminar and the X-Plane developers to keep people interested in X-Plane to the point where the community will show enough interest in it to keep using it. We all have our own, individual preferences. And rightly so. Let the products speak for themselves.