Pils

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.

Thank you. Appreciate putting in the time & effort. I only wish you'd looked around more, at the overhead, at the pedestal, at the thrust levers, shown those PID windows on screen, etc., so we can get a good picture of the state of the aircraft. But the description above is good to have in its place. I assume this is V1.7? @airforce2 Can you provide the Log.txt from X-Plane, please?

I'm sorry, you need to find a way to record a higher quality video. I suggest looking at OBS Studio and publishing to YouTube. Thanks.

You want the Disk Route menu.

If possible to replicate, having a video would be most useful, thanks.

As long as you can fully represent ARINC 424.

I, for one, am very interested to hear the roadmap/plans for the "remainder of the year" development.

Please provide the full flight plan, and attempt to reproduce it with full steps. I assume this is on V1.7?

It’s a 4-year-old Intel mobile processor in a laptop, I’m not surprised it’s a bit slow. Also what kind of drive is X-Plane installed on? An external?

Do you have brake pedals? Are they setup the same way in control profiles? Maybe the axes need to be reversed.

Potentially a permissions issue. Try deleting /Volumes/T7/Jeux/X-Plane 12/Output/caches/CL650 directory.

https://x-plane.helpscoutdocs.com/article/26-mac-xpl-not-starting

https://discord.gg/TqeDwEwh

WIP.

Might just be using the defaults?

Probably referring to the EVS control. It’s not functional.

That’s no different from creating and using a new airframe though.

It’s the opinion on discord the APU is broken beyond repair and you’ll need to create a new airframe.

Remove all third party plugins except Gizmo and try again. There’s no crash information here.

Please provide Log.txt file

Correct.

Can you post a screenshot please?