Pils

Please capture the value of this dataref over time during one of these “upsets”.

Personally I think not allowing any wiggle room is poor software design myself.

https://discord.com/channels/397379810067742721/397408003348889600/983476367909871676

https://discord.gg/FW7Khpwe

There’s a checkbox on the right hand side of the Graphics settings in X-Plane. It may have been automatically enabled, if so, I can only apologise on Laminar’s behalf as I believe this is a premature decision.

Don’t use experimental features, i.e. Zink, until official support is published.

Using the custom baro_up and _down commands may be more effective. (When in doubt use custom over default.)

You’re using a hardware display rather than looking at the virtual cockpit displays?

Was already requested 14 months ago. I have no problem setting barometers using the X-Touch Mini personally.

Challenger does not use the default altimeter gauges in any way, as with almost everything, they are implemented custom within the Pro Line 21 avionics. Some things are bridged back for read access by third parties, but are not synced two-way in order to cleanly maintain the state inside the aircraft.

Disable Zink.

Once LR and/or AMD fix their driver bugs, Zink will be supported in the next version of the Challenger (V1.8; a beta of which is available via the Hot Start Discord). Unfortunately there’s nothing else to be done in the meantime.

Don’t use Zink.

Post the Log.txt from the X-Plane directory. Check if your X-Plane directory, or part there of, is read-only.

I think you may want RealSimGear support.. https://help.realsimgear.com/en/. I assume they provided the ini file.

Not sure why you have so many duplicate entries in the data manager, but look at the top one for X-Plane 12, its cycle matches the one shown in the plane’s secondary data base. You need to fix what nav data is being installed and where, then it’ll work.

For future visitors; this is no longer the case.

Can you post screenshots of the tabs in the Data Manager software, please? Also of the STATUS page on the plane’s FMS? thanks.

Then the plan is invalid in some way. If you post the FMS file and Log.txt (after attempting to load it) maybe we can figure out why.

Just looks like X-Plane 12 standard reflections of the displays. The reason they might not look like it is because the lighting reflections are only updated every few minutes in V1.7. What do you think @Goran_M?

I've let the developer know, thanks. In the meantime, I'm not saying this is the cause, but just a couple of things I spotted from the log: 1. You seem to have uncalibrated axes assigned to throttles, but maybe this is for a different control profile? 0:00:19.769 E/JOY: UNCALIBRATED AXIS DETECTED: BU0836X Interface (VID:7634PID:4097) Axis #0, assigned to joy_use_sbrk, has an expected min/max range of [0.000000, 4095.000000], but is calibrated for [0.221490, 0.795116]. You should recalibrate the device in the Settings menu. 0:00:19.769 E/JOY: CALIBRATION OVERRIDE: BU0836X Interface (VID:7634PID:4097) Axis #0 forced to be treated as calibrated due to a user pref. 0:00:19.769 E/JOY: UNCALIBRATED AXIS DETECTED: BU0836X Interface (VID:7634PID:4097) Axis #1, assigned to joy_use_thro4, has an expected min/max range of [0.000000, 4095.000000], but is calibrated for [0.175824, 0.787546]. You should recalibrate the device in the Settings menu. 0:00:19.769 E/JOY: CALIBRATION OVERRIDE: BU0836X Interface (VID:7634PID:4097) Axis #1 forced to be treated as calibrated due to a user pref. 0:00:19.769 E/JOY: UNCALIBRATED AXIS DETECTED: BU0836X Interface (VID:7634PID:4097) Axis #2, assigned to joy_use_thro3, has an expected min/max range of [0.000000, 4095.000000], but is calibrated for [0.143101, 0.724786]. You should recalibrate the device in the Settings menu. 0:00:19.769 E/JOY: CALIBRATION OVERRIDE: BU0836X Interface (VID:7634PID:4097) Axis #2 forced to be treated as calibrated due to a user pref. 0:00:19.769 E/JOY: UNCALIBRATED AXIS DETECTED: BU0836X Interface (VID:7634PID:4097) Axis #3, assigned to joy_use_reverse, has an expected min/max range of [0.000000, 4095.000000], but is calibrated for [0.083272, 0.715751]. You should recalibrate the device in the Settings menu. 0:00:19.769 E/JOY: CALIBRATION OVERRIDE: BU0836X Interface (VID:7634PID:4097) Axis #3 forced to be treated as calibrated due to a user pref. 0:00:19.769 E/JOY: UNCALIBRATED AXIS DETECTED: BU0836X Interface (VID:7634PID:4097) Axis #4, assigned to joy_use_thro2, has an expected min/max range of [0.000000, 4095.000000], but is calibrated for [0.159707, 0.785348]. You should recalibrate the device in the Settings menu. 0:00:19.769 E/JOY: CALIBRATION OVERRIDE: BU0836X Interface (VID:7634PID:4097) Axis #4 forced to be treated as calibrated due to a user pref. 0:00:19.769 E/JOY: UNCALIBRATED AXIS DETECTED: BU0836X Interface (VID:7634PID:4097) Axis #5, assigned to joy_use_thro1, has an expected min/max range of [0.000000, 4095.000000], but is calibrated for [0.166300, 0.770208]. You should recalibrate the device in the Settings menu. 0:00:19.769 E/JOY: CALIBRATION OVERRIDE: BU0836X Interface (VID:7634PID:4097) Axis #5 forced to be treated as calibrated due to a user pref. 2. You may want to set the control response and stability augmentation to zero (full left on the sliders), this is what the plane has been tuned for. But if this is deliberate, whatever works best for you, of course. 1:38:40.460 I/JOY: Control response for axis joy_use_ptch: 0.500000 1:38:40.460 I/JOY: Control response for axis joy_use_roll: 0.500000 1:38:40.460 I/JOY: Control response for axis joy_use_hdng: 0.500000 1:38:40.460 I/JOY: Stability augmentation for axis joy_use_ptch: 0.200236 1:38:40.460 I/JOY: Stability augmentation for axis joy_use_roll: 0.203190 1:38:40.460 I/JOY: Stability augmentation for axis joy_use_hdng: 0.197283 Thanks.

The manufacturer’s abnormal and emergency QRH is over 300 pages. It’s not really practical for a solo developer like Hot Start to reproduce that, and would be potentially illegal regardless.

Create a new airframe. You have to transition the bleed air onto engines from the APU first. Use the checklist and hint images to guide you.