Rodeo

Like a 2-hour chat/investigation on Discord resulting in my best guess as to the hidden cause of the issue?

Because some aircraft and/or plugins don't bother to clean up after themselves, the following datarefs should be force-enabled when appropriate: sim/cockpit2/radios/actuators/com1_power sim/cockpit2/radios/actuators/com2_power …it's already done for e.g. sim/cockpit2/switches/avionics_power_on (which is perhaps a more common source of errors, but the above being set to zero can happen too). Regards, Tim

Or a Diverse Departure Assessment, or the airport is not charted at all (e.g. some private airports) and the pilot is on his own. Still doesn't answer the OP's question about which airspeed and/or climb configuration corresponds to the FMS-calculated climb performance though…

Good point. It's past my bedtime though, AP ON BRAIN OFF

Right, so I need to compute the peak delta-G somehow myself then, correct? Regards, Tim

Using version 1.4r1, macOS Catalina, X-Plane 11.55 I have code to print the HLIS dataref's contents after touchdown when passing 25 knots GS and decelerating: if (onground_any > 0) { if (25.0f > (XPLMGetDataf(flightmodel_groundspeed) * 3.6f / 1.852f)) { if (delta_acc) // XPLMFindDataRef("CL650/HLIS/delta_acc") { log("[info]: landing (detected): CL60 HLIS acc %.3f\n", XPLMGetDataf(delta_acc)); } } } Resulting in: [info]: landing (detected): CL60 HLIS acc 6.104 Compared to (HLIS button pressed for two seconds later on, i.e. soon after engine shutdown, checked on the display and crosschecked with the CSV log): HLIS % grep DeltaG HLIS-1.csv DeltaG,0.622 HLIS % The difference (6.x vs. 0.6x) seems significant. Questions: am I printing the wrong dataref? is it not a float (seems unlikely)? do I have to process delta_acc get to DeltaG somewhow? do I really have to print the dataref even later than I do now? is there a different issue I'm not aware of? Regards, Tim HLIS-1.csv.zip HLIS.nvram.zip

Ping; has this been logged anywhere? Regards, Tim

Ping; has this been logged anywhere? Regards, Tim

We can e.g. run to the FBO exit door to the apron and aircraft by using the dedicated click spot on said door; recently the option was added to walk to the opposite door to return to the main X-Plane menu, but no click spot was added for that one. Rationale(s): convenience, consistency Regards, Tim

In some instances, flaps control is a "pilot 2 action" in the checklists (after takeoff, after landing, possibly go-around?); but for people who have a hardware flaps lever, it would be interesting to be able to override this behavior so that all flap actions must be performed by the pilot flying -- without having to manually edit the checklist files. Rationale: avoiding a desync between the hardware and actual aircraft's flap lever position, which could possibly lead to confusion during an important flight phase Note: a checkbox to enable/disable this behavior would be more flexible than auto-detecting whether an axis is assigned to flaps in X-Plane. Rationale: non-standard hardware and/or situations where a custom plugin is used to read the axis value and set the flaps indirectly, rather than the native X-Plane flaps axis assignment. Regards, Tim

CL650/pedestal/gnd_spoilers_value It's a dataref, not a command though. I guess if you're requesting a command you should state so in your post? Regards, Tim

Indeed, in the CL650 you get a geometric path VNAV descent, rather than performance-based VNAV descent. Thus neither winds nor target speeds make any difference. You can manually change the vertical path angle via one of the VNAV setup pages to be steeper or shallower depending on the expected wind component during descent as well as personal preference.

Ping? Regards, Tim

For a moment I thought the airway intersections were working for Cameron

Example, for an OAT of +5°C: assumed temperature of +45°C already gives apparent "maximum reduction" for FLEX (N1 target 85.0%) increasing the assumed temperature to +50°C gives the same N1 target of 85.0% as the above… but V-speeds (here, V1) and especially required takeoff distance differ: …that over 100m of runway, which seems like a lot if it were caused by e.g. rounding (say, N1 target of 85.04% at FLEX 45 vs. 84.96% at FLEX 50)? It kind of looks like, possibly, the assumed temperature of +50°C initially results in an N1 target lower than 85.0 which then gets sanitized to a minimum target, but TOFL and V-speeds are based on the invisible, unbounded N1 target instead? Regards, Tim @Graeme_77