alstr

Looks like I was red lining the engines.

I bought this today and really like the look of it. The only problem is I haven't been able to get beyond a 1 mile radius of the airport yet... I've followed the checklist exactly, getting everything set up and ready for takeoff. Shortly after I take off though the left engine loses torque and fails, followed by the right. I have enough fuel, battery power, etc. What stupid thing am I doing wrong? replay_compressed.mov

Is there meant to be a discrepancy between the brightness of the cockpit screens and the pop-out ones? It makes reading difficult without excessively fiddling around with brightness controls. (And of course this screenshot shows the now regular issue of the hydraulic summary having gone crazy). Maps in particular are very difficult to read at times. I find brightness of displays/lighting quite a challenge to manage in general compared to other aircraft. The overhead panel lights on bright look like the aurora borealis. I'm sure some of this is X-Plane.

I thought I tried that and it didn't work, but I'll see next time.

I have noticed on a number of occasions that walkaround goes into a weird state where it is constantly moving and you can't stop it. Moreover, the directions seem to get inverted, to the point that whatever you're looking at you're actually moving away from. Take a look at the attached video. That's not me walking drunk; that's the sim going crazy, with me just spinning the camera around trying to find some semblence of control (thankfully walls do stop you). You can see I immediately backed out of the FBO on entry, because of it moving in the opposite direction. It's a battle to get any kind of control, and the only solution I've found is restarting the whole sim. When I reach the FBO exit to main menu, you can see the camera keeps moving. X-Camera is disabled. This admittedly may be a Laminar camera bug, but thought I'd see. It seems to randomly trigger when leaving the captain seat. 80% of the time walkaround is fine, but this does happen every few flights. walkaround_compressed.mp4

Fair enough. Hoping for full native Mac support one day.

I just did a flight LSZA - LXGB with 7,000lb of fuel which exceeds the block fuel stated in Simbrief. I paused for a short while mid flight, but not a huge amount of time. When I came back, I nudged the X-Plane flight config time backwards to carry on from where I left off. I flew a little longer, and I noticed it looked like I had a lot less fuel than I remembered on the summary screen. The prog page of the FMS was still showing a roughly correct number though. Shortly after landing I got APU pump fail and mid way through the shutdown everything just went. I have no idea what happened. Screenshots below. Also see the crazy hydraulic numbers that seem to happen every other flight now. (Extra weirdness: after switching back from replay mode I fell through the floor into outer space. The aircraft livery also reset mid flight). Edit: looks like calc fuel was wrong, I thought it was sensed fuel. My mistake. This is resolved.

I'm not using Rosetta, I'm using https://benrussell.gumroad.com/l/gizmo64-lts

By the way, to anyone who looks at this thread in future, I figured out a way to resolve the hydraulics issue. If you keep pressing the brakes until the brake pressure values match the system pressure value shown above (~3000) then they stay that way. You could probably use a Lua script to repeatedly toggle them to resolve it quicker.

When I turned the aircraft generators and battery off after landing the sim crashed. Admittedly I was not following the checklist to the letter, as I was in a rush. 2025-12-13 16:36:39 CL650[fo_actions.c:1371]: FO actions: rwy exit 0:04:40.603 I/TEX: Target scale moved to 4.000000. Texture usage is 2.69 gb out of 6.00 gb available. Memory headroom is 3.46 gb 0:05:02.000 G64: warn: Undefined function: ProcessKeyPress RawKeys_OnKeyHold 0:05:39.646 I/TEX: Target scale moved to 8.000000. Texture usage is 3.00 gb out of 5.51 gb available. Memory headroom is 2.65 gb 2025-12-13 16:37:43 CL650[fo_actions.c:1439]: landed: false 2025-12-13 16:37:43 CL650[libturbine_solver.c:183]: assertion "( sizeof(cpr) == sizeof(float) ? __inline_isfinitef((float)(cpr)) : sizeof(cpr) == sizeof(double) ? __inline_isfinited((double)(cpr)) : __inline_isfinitel((long double)(cpr)))" failed: 2025-12-13 16:37:43 CL650[except.c:120]: Caught SIGABORT: abort (0x191a8e388) Backtrace is: 2 libsystem_platform.dylib 0x0000000191b016a4 _sigtramp + 56 3 libsystem_pthread.dylib 0x0000000191ac7848 pthread_kill + 296 4 libsystem_c.dylib 0x00000001919d09e4 abort + 124 5 systems.xpl 0x0000000401c254cc asn1_check_version + 1740720 6 systems.xpl 0x00000004010f70c0 XPluginReceiveMessage + 4251232 7 systems.xpl 0x00000004010f6d90 XPluginReceiveMessage + 4250416 8 systems.xpl 0x00000004010f4bc4 XPluginReceiveMessage + 4241764 9 systems.xpl 0x0000000400d74058 XPluginReceiveMessage + 568824 10 systems.xpl 0x000000040108027c XPluginReceiveMessage + 3764252 11 systems.xpl 0x000000040138f98c wfETC1_DecodeImage + 341304 12 libsystem_pthread.dylib 0x0000000191ac7bc8 _pthread_start + 136 13 libsystem_pthread.dylib 0x0000000191ac2b80 thread_start + 8 --=={This application has crashed!}==-- (Art controls are modified.) --=={FILE: ...X-Plane 12/Log_ATC.txt}==-- 2025-12-13 16:37:44 CL650[except.c:117]: Caught SIGSEGV: segmentation fault (0x1e0) Backtrace is: 2 libsystem_platform.dylib 0x0000000191b016a4 _sigtramp + 56 3 systems.xpl 0x0000000400e1945c XPluginReceiveMessage + 1245692 4 systems.xpl 0x0000000400e195c4 XPluginReceiveMessage + 1246052 5 libsystem_c.dylib 0x000000019197f944 __cxa_finalize_ranges + 480 6 libsystem_c.dylib 0x000000019197f704 exit + 44 7 systems.xpl 0x0000000401365490 wfETC1_DecodeImage + 167996 8 libsystem_platform.dylib 0x0000000191b016a4 _sigtramp + 56 9 libsystem_pthread.dylib 0x0000000191ac7848 pthread_kill + 296 10 libsystem_c.dylib 0x00000001919d09e4 abort + 124 11 systems.xpl 0x0000000401c254cc asn1_check_version + 1740720 12 systems.xpl 0x00000004010f70c0 XPluginReceiveMessage + 4251232 13 systems.xpl 0x00000004010f6d90 XPluginReceiveMessage + 4250416 14 systems.xpl 0x00000004010f4bc4 XPluginReceiveMessage + 4241764 15 systems.xpl 0x0000000400d74058 XPluginReceiveMessage + 568824 16 systems.xpl 0x000000040108027c XPluginReceiveMessage + 3764252 17 systems.xpl 0x000000040138f98c wfETC1_DecodeImage + 341304 18 libsystem_pthread.dylib 0x0000000191ac7bc8 _pthread_start + 136 19 libsystem_pthread.dylib 0x0000000191ac2b80 thread_start + 8 --=={This application has crashed!}==--

@Pils That did help with the navigation issues, but there were still significant fluctations in the speed/altitude/bank angle on load that took a while to correct itself.

@Pils 2 hours into a long flight I got a MAIN BATTERY OFF warning (all generators running, everything switched on) and noticed the circuit breaker had tripped. It coincided with these hydraulic values going crazy. Is it a related bug or am I doing something wrong?

Thank you, I will give that a try next time.

Cockpit view after loading last save. All navigation has vanished and AP has gone crazy. MSG appears in FMC saying low position accuracy.

Moved topic to here: https://forums.x-pilot.com/forums/topic/53930-crash-when-shutting-down-aircraft/

After a bit more flying I've noticed the camera refusing to work properly seems to be a repeated issue when loading saves. Update: Looks like it's X-Camera starting automatically and interfering with things.

I completed half a flight today without issue but had to stop before I could finish it. I created a manual save but also left the game paused with the monitor turned off. When I came back to it, several hours later, I first tried to pick it up from the paused state, but the plane had seemingly lost its current position and I couldn't set POS INIT again. I reloaded the save instead, but then the route on the PFD had disappeared, as had my location on the Navigraph charts, even though the FMS route was still correctly populated and I could see my location in AviTab and Navigraph Charts externally. I reloaded again, and this time, I had the route back. Everything proceeded normally until a 'MAIN BATT OFF' warning popped up, despite the battery still being on. Landed, then tried to get out of the seat, but the camera was stuck in free move mode and it refused to snap to the corridor and go into walking mode. When I tried to set my position via the menu it put me inside the overhead panel, then back to where I was. I thought I'd try reloading a recent save to see if that would fix things again, but I couldn't reload the last autosave as the button was greyed out. Presumably because it was the 'current state' (technically slightly earlier), but even when I reloaded the aircraft I still couldn't pick up from that. I reloaded an earlier save, it warned me about loading the position/trajectory, so not fully understanding what the alternative was, I tried loading without, and it put me below the earth with alarms going off. I'm assuming most of this relates to or stems from leaving the flight part way through. It was all a bit weird. Not really expecting a fix, just reporting my findings. (Side note, started a new flight, then got caught up in the left hand side of the stairs and couldn't get out without changing position from the menu).

I noticed the values in this section looked odd. Obviously they are too long for the space provided, but they seem to be references rather than actual values?

Thank you, here is the direct link if anyone finds this in future: https://www.ncei.noaa.gov/products/world-magnetic-model

I noticed in the log file: WARNING: the magnetic model WMM.COF is out of date. The model is valid for years 2020.0 -- 2025.0, but according to our internal clock, the year is 2025.9. Please contact Hot Start for an updated magnetic model, or download a new model file from NOAA (https://www.ngdc.noaa.gov/geomag/WMM/wmm_rdownload.shtml) I followed the link but can't see an updated model. Is there one available?