Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/11/2022 in Posts

  1. Information in this post no longer relevant with v1.1r1, information remains for clarity. There is a minor issue with the altimeter information in the initial release of the 650, that is being corrected for the next version. It's also separate from the altimeter temperature effects, and doesn't change anything in the first post on this thread. Let me explain the issue first: In real life, traditional ATC "primary" radar has no way to see how high an aircraft is, so a system called "secondary surveillance radar" or SSR sends a radar pulse to interrogate the aircraft transponder. The transponder provides a Mode A code such as "4651" and a Mode C response encoding the aircraft altitude. Modern SSR does loads more with Mode S but let's stick to the basics. Real Mode C altitude responses are fixed to 29.92inHg for the encoder pressure setting - it's basically always reporting a flight level, even at very low altitudes. To present that correctly, the controller radar display reads the 29.92 altitude, and converts it into whatever the sector pressure is. So if a controller tells you "Palm Springs Altimeter 3014", their radar display is converting the 29.92 into the correct altitude for 30.14. Now, in online flying this doesn't work. I could be flying on my own fixed weather, another pilot could be flying real world weather, and yet another on another sim with a slightly different weather source. To make this work, rather than sending the altitude relative to 29.92, the “xPilot” VATSim client sends the actual altitude displayed on your altimeter. If it's right for the pilot, it's right for the network. (I'm not talking about the altitude to draw the 3D aircraft model here, that's something else, I'm talking about what shows on the controller's display). The advanced systems in the 650 operate entirely separately from X-Plane. On the initial release version, the X-Plane stock cockpit altimeter is not synchronised with the Challenger 650 cockpit, so when, for example, the Vatsim client asks for the cockpit altitude to show the controller it's linked to the X-Plane cockpit values and not the Challenger 650. This will be addressed in a future release, but for the time being the keyboard binding "Baro pressure selection 2992" can at least set X-Plane to the standard pressure setting. It won't fix the issues in every case, but is a workaround until the product is updated. Sorry for the inconvenience to online pilots - the Challenger 650 is pushing the boundaries of what X-Plane can do, so it's only natural these previously unknown issues are exposed as more and more people enjoy the Challenger 650.
    4 points
  2. At the request of users in the discord, here are my bindings for the throttles and reversers on the Bravo. Use the Commercial handles and map the following in the Honeycomb Configurator: Lever 3 Commercial Reverser/GA GoAround -Press-Event -Variable 1: sim/engines/thrust_reverse_toggle_1 -Release-Event -Variable 1: sim/engines/thrust_reverse_toggle_1 Lever 3 Detent: -Press-Event -Variable 1: CL650/pedestal/throttle/shutoff_L_down -Release-Event -Variable1: CL650/pedestal/throttle/shutoff_L_up Lever 4 Commercial Reverser/GA GoAround -Press-Event -Variable 1: sim/engines/thrust_reverse_toggle_2 -Release-Event -Variable 1: sim/engines/thrust_reverse_toggle_2 Lever 4 Detent: -Press-Event -Variable 1: CL650/pedestal/throttle/shutoff_R_down -Release-Event -Variable 1: CL650/pedestal/throttle/shutoff_R_up Remember to activate the profile in the Honeycomb software before you load up, and use the plugin menu to load the profile once you're in the sim. I haven't checked the indicator lights yet to see if they work with defaults or not, and the autopilot seems to mostly work with the default bindings, but once I get a more complete profile I can post it here for other users.
    3 points
  3. https://www.smartcockpit.com/plane/BOMBARDIER/CHALLENGER 605.html A source for some stuff Best Steff
    3 points
  4. Reference material - https://www.smartcockpit.com/docs/CL605-FUEL_SYSTEM.pdf Page: 16 Fuel tanks are expected to be within 400 lbs / 181 kgs of each other on taxi / takeoff / landing OR 800 lbs / 362 kgs during flight, to avoid Fuel Imbalance EICAS message. First, orient yourself on the overhead panel, we'll be working in the 2nd row (or middle row) of the FUEL panel area. (Fuel.PNG) All three of these buttons should be extinguished under normal operations. Gravity XFLOW Press to begin the process, there's a 1 second delay after pushing the button for it to illuminate OPEN. This will allow fuel to flow freely between both main (wing-based) tanks. There is no EICAS notification that this is open/occurring. (gravity.png) To observe what's happening in the sim. You can go to the Challenger 650 menu -> Study -> Engines -> Fuel System... You'll notice that whatever Main Tank (either Left or Right) has more fuel that this will continue to consume, whereas the side with less fuel will not. Thus balancing the tanks. L (R) to AUX XFLOW Press the appropriate button to begin the process, there's a 1 second delay after pushing the button for it to illuminate ON. This will remove fuel from whatever side is select and transfer it to the auxiliary tank. Determine which tank has more weight in fuel Left side? Choose L to AUX (L to AUX.png) Right side? Choose R to AUX (R to AUX.png) There is a lock out mechanism that does not allow you to press the opposite button when one is already selected. Pressing L to AUX, for example, then pressing R to AUX, will no longer illuminate the L to AUX button. Pressing the R to AUX button again will resume the L to AUX transfer and the button will illuminate ON again. Once you're done balancing the tank, make sure to deselect the previously selected L (R) to AUX button. The aircraft will now suspend fuel consumption from the two main tanks and pull from the AUX tank until depleted. *Edit* Thanks! @airforce2 As long as a main tank is below 93% full, the aux tank feeds the main tank to maintain the level at 93%. Once a main drops to 93%, the main quantity will remain constant and the aux level will drop. It will appear that the engines are burning from the aux tank, but in reality the engines are burning from the mains and that fuel is being simultaneously replaced in the main tank from the aux tank ejector xfer pumps. To observe what's happening in the sim. You can go to the Challenger 650 menu -> Study -> Engines -> Fuel System... Note: The plane will display an EICAS warning message: FUEL XFLOW SOV OPEN if either button is ON for more than 50 seconds and the tanks are balanced within 100 lbs.
    2 points
  5. Documents attached updated 20th December 2022. Latest versions are always available in ...\Aircraft\X-Aviation\CL650\Documentation directory. IMPORTANT: you must be signed in to download the PDFs below. Not a user yet? Head over to Sign Up. 1128340285_CL650FMSPrimer.pdf CL650 Operations Reference.pdf 1323904309_CL650ExpandedNormalProcedures.pdf CL650 Checklists.pdf CL650 Checklists - Printable.pdf CL650 Flexible Take-Off.pdf CL650 Shared Cockpit Quick Start Guide.pdf
    2 points
  6. For some odd reason they got deleted by youtube...and I don´t have them anymore . I plan on redoing them with XP12 when that one comes out - there have been a lot of changes to our model since back then and also the new simulator platform warrants a better looking video, so might as well redo them then! Cheers, Jan
    2 points
  7. I can see the same effect on my system. Will try and track down the issue further.
    2 points
  8. Hi , for the time being, I’ve found the MMEL….all the other manuals are quite hard to find ( for free..) Cl600_EASA-MMEL_Rev01 2.pdf
    2 points
  9. I've run a bunch of A B testing on Gizmo retail vs Gizmo dev branch and it looks like a bunch of this is on me. I'm seeing some pretty abysmal perf numbers out of retail. The good news is I'm seeing some significantly better numbers out of the dev branch... Will push harder to get you all something soon. Turns out Gizmo is NOT the issue. See last post in this thread.
    2 points
  10. 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
    1 point
  11. 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
  12. Great work on this plane - I am loving it. As a primary VR flyer, I wanted to give my feedback on my experience so far (I know there have been other threads, but they are closed before others can give feedback - understandably to keep them under control). I think the VR experience for a day-one release is fantastic. No issues with flying the plane. My only feedback would be: 1. The ability to communicate with the fuel truck, ramp worker, and use the cell phone inside VR (make the menus similar to the study menus that are usable in VR). This would only apply once inside the cockpit. 2. Several 3-way test rocker switches do not centre in VR. I *think* this might be an X-Plane VR controller limitation and not an issue with the plane. 3. Limit the knob rotation sensitivity (although this is something a user can easily accomplish to their own liking in VR config) In terms of movement inside the aircraft - for me it's not as huge a deal. Yes, VR hotspots would be appreciated (maybe even just one near the door so that it can be closed without having to leave VR). Again, just some items to add somewhere on a future to-do list. Nothing mission critical or immersion-breaking. This plane handles great in VR (the HUD is fantastic!) and I am having lots of fun. Thanks again for all of your hard work.
    1 point
  13. The Challenger 650 does not have FADEC, but there are engine controls and mechanical systems in place that affect how your lever position controls the engine. The most common issue seen reported with the simulation is the engines are not making "full power", or rather not achieving the rating on the N1 EICAS display. The reason for this is the engine has an N2 limit which varies based on total air temperature, which depends on aircraft speed and temperature. The TAT is shown on the PFD left side datablock, Don't climb at too low an indicated airspeed or mach, and keep an eye on the TAT. This chart shows what's going on, and will also included in the Operations Reference Document when possible. Keep i mind the chart shows Corrected N2, but gives you an idea of what is actually going on.
    1 point
  14. I inadvertently initiated L engine shutdown (by releasing a agent bottle) inflight, flying with one engine after this mistake, I could not for the life of me relight the L engine and also could not turn on the APU, I was at FL 050. So I landed with one engine and parked the aircraft. How do I service the engine and make it good again using the FBO?
    1 point
  15. 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
    1 point
  16. 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  
    1 point
  17. Resolved, fix will be in next update.
    1 point
  18. As discussed on Discord, this is due to OMAR not having any instrument procedures and therefore being excluded from the FMS's database. A fix for this will be in a forthcoming update.
    1 point
  19. I was able to modify the object file and create a VR config file which includes some teleport spots as well as the ability to properly control the yoke. I have not touched anything else as I think they will come with an update at some point and are not required as a needed item at the moment (ex. 3 way switches.). Just skip those items in the checklist and you'll be fine. Also, if you want to control any interior cabin lighting, you will have to do it outside of VR until they make some changes to allow for manipulation with the VR controllers.
    1 point
  20. I was able to figure this out. I had loaded an incorrect profile from the Honeycomb configurator and ended up with a double bind. Once I removed that, it seems all is well with the key binding for the park brake!
    1 point
  21. Thanks Ed, will check it out shortly and see what's happening there.
    1 point
  22. Personal I do export it with LNM as fms at X-Plane/Output/FMS plans/ and load it in CL650 via IDX(index) > ROUTEMENU > DISK ROUTE LIST > navigate to correct with PREV & NEXT and pressing appropriate Left LSK The same you can do with every third party flight planner. Hope that this help you.
    1 point
  23. Hi Robbietp1, Yes I read the messages. Thank you very much and looking forward to this! Cheers
    1 point
  24. Thank you Graeme, appreciated.
    1 point
  25. It's being investigated with the help of the project consultant pilots. If the FMS should show VFR only airports, then I'm sure a solution will be possible. The concern is having a total worldwide set of every little airfield could be less useful, as real aircraft databases are often a smaller subset of the full thing to minimise "clutter".
    1 point
  26. The clickspots for the Duct Test switch are the labels around the switch. Click the label (Loop A, Loop B, etc) you want to rotate the switch to and hold, you might have to zoom your view in and pop out the EICAS. Mouse scroll wheel is not supported because its a momentary switch. You have to click the desired position and hold.
    1 point
  27. Many thanks for this info. Have nice flights. Frank
    1 point
  28. Also, SimBrief has now added MACH 0.74 and 0.72 cruise profiles. Yay!
    1 point
  29. As I've learned recently, this is indeed intended behavior with very low TATs. To put it extremely simply, the maximum N2 the engines can achieve is limited with temperature, becoming less as TAT decreases. You can find a graph of the engine fuel control in the "Fuel Control Map" study menu. I believe there will be a graph put into the operations reference showing the maximum *corrected* N2 values for a given TAT. Make sure to keep an eye on the TAT during the climbout and keep the speed up to have an easier time accelerating once you reach cruise.
    1 point
  30. Hi, I have been downloading this into X-Plane for my FMS for free and it has been working fine. Download the Coded Instrument Flight Procedures (CIFP) (faa.gov) ---download the current CIFP file (Coded Instrument Flight Procedures) and extract the files. Copy the FAACIFP18 file, paste it into the folder "X-Plane 11 / Custom Data " and rename the file (FAACIFP18) to earth_424.dat ----- Then I get all the airport and info and charts from here. Lookup Airport | SkyVector But when I go into the FMS on the 650 it reads "WORLD", and will not show me a current database. Can you tell me how I can use the FAA data? Thanks Chris
    1 point
  31. At the moment this method of working is not supported - the Challenger 650 FMS has a complete navdata processor to avoid having to deal with limitations of the X-Plane navigation API, but the FAA CIFP data is not supported.
    1 point
  32. On a typical departure, where terrain or obstacles are not a factor, at 400 feet the pilot flying (PF) asks for vertical speed mode. This is typically done where you have a low level off right (KBFI) right after departure, if you use FLC, the pitch angle is too high and you will likely overshoot the level off. If you were on a departure in mountainous regions (KASE or CYLW) or terrain is a concern, at 400 feet the PF will ask for FLC 250. A typical after takeoff check: landing gear up, flaps up, thrust reversers off, ignition as required, 10th stage bleed transition (Right 10th stage bleed press in, 10th stage isolation press out, left Left 10th stage bleed press in, APU LCV press out, climb thrust set (this is done through the FMS CDU (press PERF, select CLB) - Thrust Limit page. N1 Climb is displayed on the primary EICAS page, ATS window. Pressurization would be checked (building diff pressure), and CAS messages would be verified as checked (nothing unexpected). Rob
    1 point
  33. It makes screenshots and videos look better. When the time comes perhaps give the option at least. You do have a pilot in the TBM. It would look weird without one. Thank you!
    1 point
  34. Agreed. A full manual that provides more insight to the location of buttons, sequence of checklist items, photographs, and a guide to various systems like the fueling system, etc. this provided documentation assumes the users are familiar with CL60 aircraft !
    1 point
  35. I’m sure Hotstart will start getting calls from training providers. I hope their licence has entertainment and pro pricing points.
    1 point
  36. Several years ago, I attended a 3-week initial maintenance training class on the Challenger 604 at FlightSafety. The animated systems graphics in the add-on considerably exceed the official training materials in both quality and detail!
    1 point
  37. It's work again, Thank you for your help
    1 point
  38. Just a note to my fellow VR users - I'm nearly finished creating a vr config file that makes VR even better. Also fixes the 3 position switches and makes then snap back to center again. PM me if you would like it when finished and I will send a link...
    1 point
  39. @Pils I know you are just helping out the dev team, so please don't take this as anything against you at all - but could you please impress upon Toto that these aren't just VR 'improvements' required - the CL650 as released does not support VR for a number of it's key features. And when in VR we are having to switch in and out again just to interact with 2d menus. The most frustrating thing being that Toto had all the 2D windows working beautifully in the TBM, I don't understand the need for a backward step here.. The aircraft is great, and we're all really grateful to have something this brilliant in the sim - but could you please impress onto the team how much a fully working VR integration means to a (ever growing) significant group of users. Many thanks, James
    1 point
  40. Took me forever to find out, but there it is:
    1 point
  41. The developer has told me the Challenger has Hydraulic Actuated Control Surfaces, and those Hydraulic Units gets their command from simple connection cables and pulleys between them and the Flight Controls. The Flight Control has no fancy ForceFeedback system for the pilot, just Springs, to make it heavier the more you displace from center. A side effect of that simplicity is that you will feel no need of increase force to move the controls across the entire envelope of speeds. Be it 100 knots, or 300 knots, they feel is the same. This makes the controls feels way more sensitive at higher speed, and is a realistic simulation of the real aircraft. Hope this helps explains how it all work.
    1 point
  42. Arguably you could/should be asked to file your flight plan without TCAS in your equipment code, but disconnecting because you do not support TCAS is not exactly a good solution. Were I you, I would complain to VATSIM about this controller.
    1 point
  43. I also would like to see a manual. I also would like to a cockpit guide for all the switches and buttons. When you use the checklist you have to know where everything is. jeffg
    1 point
  44. I have a small thing to add... The switches of the refueling panel are so black, I cant see which position they are... Only when i look from near 90 deg from the side.
    1 point
  45. Disable Vulcan in XPlane, in OpenGL the .acf file will open! Bruno
    1 point
  46. I have found if you click on the o2 mask can't seem to find a way to put it away in VR.
    1 point
  47. Has anyone with a WMR headset (like the reverb G2) figured out a way to get a VR session working properly? If I start x-plane directly to VR from within steam-vr, x-plane crashes when I start a flight with the challenger. I am starting using a non persistent flight to skip the FBO. (I reported this bug and sent the log file here in the forum.) If I start x-plane and the Challenger flight in 2D and then activate the VR hardware when I am in the cockpit, x-plane is extremely stuttery. This is not a Challenger problem. It's an x-plane problem I always have. Any information as to your workflow to get it working ok would be much appreciated. I have been mucking around for 3 hours now...
    1 point
  48. The CG value in the FMS Takeoff perf page is for pilot information only. It does not need to be completed, and has no effect on the performance of the aircraft. The developers are investigating options to display load and balance information in a manner that best simulates the corporate pilot experience as it differs substantially from scheduled air transport.
    1 point
  49. The passenger load you specify in the FBO is used to drive the passenger weight calculation. The weight is randomised, accounting for factors like seasons and even geographic regions. I will try and get the max and min weights possible and add them here if I can. Two pilots are accounted for in the operational empty weight. If you want to change the payload, you can freely do this in the X-Plane weight and balance menu. So you can match simbrief exactly if you prefer. On the FMS it calculates the performance based on the weight you enter. You can enter ZFW directly if that's easier than use pax/cargo fields for your particular operation. Some operators will add 500kg to the loadsheet or caluculated weight when doing takeoff calcs to make sure you've got some margin. At the moment a loadsheet is not provided - I agree that would be a very useful and authentic thing, and the developers already have my feedback on that. Business jet operations are not like airline operations with fixed seating ( "No, Miss VIP, you must sit on the Lav seat due CG limitations!" ), so some kind of range of CG needs to be calculated and displayed rather than a single point. Hope that makes sense?
    1 point
  50. WOW! Just purchased the CL650 and she is a thing of beauty. It will take some time to get up to speed with all the systems but that's ok as it will be worth it. Type rating in a bird like this is a process. POINT of SUBJECT: I have the following Hardware - RSG G1000XFD, G100015MFD, GMA350, GFC700, GCU47X and GTN750, WinWing F/A18A HOTAS Throttle Quadrant/Startup, Combat and Takeoff panels, Stream Deck XL as well as Brunner MKII Yoke and Peddles and a few Saitek items My goal is map/bind as many functions as possible to all. I'm putting this out there hoping others with similar hardware may wish to share/collaborate. I also have a Discord for Brunner Hardware but you will need to PM me for this info. I'm thinking online Google sheets might be the way to go. Any suggestions please post. Thanks
    1 point
×
×
  • Create New...