Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/02/2022 in all areas

  1. Hello All, This will serve as a formal forum announcement that we have released the version 1.5.2 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.5.2 for you. 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: 2690: Add a clickspot for inspecting wing surfaces during preflight 2708: Add support for xPilot’s SELCAL datarefs 2716: Implement FANS CPDLC support 2732: Implemented DEP CLX, OCEAN CLX and ATS LOG datalink subsystems Enhancements: 2691: Redesigned the overnight icing accumulation algorithm to use real METAR data 2688: Add support for detecting POSCON client for disabling realistic altimetry feature 2698: Implement workaround for FMod sound bug when loading the airplane with sound muted 2699: Implement dataref interface for libfail to allow 3rd party software to trigger our failures 2320: User request for dataref to indicate when in “walking mode” Bugfixes: 2683: ABEAM REF distance and time isn't working correctly 2687: V-bar FD vertical deflection & rotation stacking should be reversed so the V-bar rotates around the nose indicator 2692: Reduce landing and taxi light brightness to be a bit closer to reality 2648: KEUG I16R with EUG transition is handled incorrectly for the subsequent leg intercept off the procedure turn 2409: Shrink or hide manipulators for engine fire push buttons so they can’t be clicked by mistake 2685: Manual ENG BLEED setting isn't being cross-talked between FMCs 2693: afm_mgr has a potential deadlock due to locking inversion if a state load coincides with a state save 2694: THRUST LIMIT page 2/2 shouldn't be selectable in the air 2695: Smooth FPLN leg joins should anticipate turn radius changes due to climbs 2697: CPC PID derivative rate was still causing oscillations when reloading a climb state at higher ISA around mid-20 thousands 2487: CTD - CL650[chart_prov_navigraph.c:1086]: assertion "chartdb_add_chart(arpt, chart)" failed 2721: Receiving a ATIS datalink message should show green DATALINK advisory CAS 2730: Reduce initial engine parameter variance a bit to help avoid unusually high ITT deviations 2775: Fix radial are off by a few degrees 2776: ATS posts an FMC ERR when FMS3 is selected as active on the left side 2779: Descent altitude constraints can stick past the waypoint where they are applicable 2780: Compressor stalls should stop when the engine is shut down 2773: PFD SVS rendering distance too short 2768: Changing NAV SRC while OEI causes CTD 2784: Small amount of aileron trim causes persistent monitored AP disconnects due to servo misalignment alarm firing 2769: DCT fix in FMS followed by pressing NAV causes CTD 2767: CTD when attempting to use invalid AFCS data 2749: Hold exit followed by FPL disco. clear = CTD 2785: Newly created airframe has right hand side cabin window blinds closed 2786: Engine hydraulic SOVs were being ignored when determining engine-driven pump operation 2787: Manual date setting on STATUS page results in setting incorrect year 2789: Make tail refuel pump fatter by 1mm to avoid spurious AUX TANK HEAVY CAS messages 2791: PBPB waypoint entry when first WPT SEL has 1 option and second WPT SEL has more than 1, empty WPT SEL shows instead 2792: PBPB waypoint checker should be using the passed selection lookup type, instead of defaulting to database-only 2793: WPT SEL screen should return to the caller's subpage 2777: Fix page missing Lat/Lon Cross small text 2795: FLT LOG fuel used needs to allow entering DELETE to reset the value 2796: TERM WX should allow for non-ICAO station IDs 2794: Add a checklist menu item to manually stop the FO's go-around flow 2797: is_valid_icao_code should allow for numbers in IDs 2798: Invalid ICAO code in FPLN RECALL page isn't generating an INVALID ENTRY error Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.
    6 points
  2. Version 2.0.0

    439 downloads

    A blank, white livery for the Hot Start Challenger 650. Suitable for use with Photoshop, paint.net, gimp etc.
    1 point
  3. I should've been more precise. Yes I know there is no full autopilot, but it happens on the approach even at 2000 feet. As soon as I disconnect at around 1000 feet it stops (while I fly it manually). So it happens as soon as the GS is captured.
    1 point
  4. AFM limitations on A/P use
    1 point
  5. Figured it out. My X52 H.O.T.A.S. Pro throttles is querky on this aircraft. I cannot have the the x52 all the way down. It needs to be in the last position prior to being bottomed out. Then the red tabs function properly on the sim bring it to cutoff position. Thanks for your help.
    1 point
  6. Sorry for the late response. If are were no external factors 200->180 on base leg. 180->160 on glideslope intercept and 160->vref+5 at no later than 2000ft above the airport. You can obviously go closer in should it be needed, busy airports in Europe can request 160 to 4nm, which is possible in the Challenger. Also have a look at the included Operations Reference Manual, which has a diagram of this exact thing.
    1 point
  7. @zrh28 apologies for the radio silence here. At this point in time work is ongoing on new features and outstanding bug fixes. It is worth mentioning that any new features have been in the works for a long time and are not taking precedence over the start of VR work. As there is no official development roadmap I cannot give you a timeframe of when VR compatibility will happen. I can tell you however that it is most definitely on the list as a significant minority of customers are VR users. Brgds
    1 point
  8. Just goofing around..You are right!!!! regards
    1 point
×
×
  • Create New...