Leaderboard

I haven't reported it yet, but I can confirm that it manifested even before the beta. To temporarily restore FMC, just tap on the left menu or gizmo menu Then the problem comes back. I always fly always with Zink, I think Zink is the problem

I did notice a minor issue that I believe that I may have created by playing around with the new "Robust Contrast Adaptive Sharpening" (RCAS) setting. After setting it to 100%, the Captain's FMC display seem to layer one display over another, the more key inputs I put in, the more the screen layered on top of the old display. After a while with no further input the display started to clear on its own. I did another flight after restarting X-Plane and left the (RCAS) setting on 0% and the problem did not reappear. Not going to file a bug unless others experience the same issue. Also, the first officer's FMC did not display any issues at all.

I've been fighting with it for over a week now. I have hundreds of (mostly) problem-free hours with the CL650 on this exact machine. I took a little break recently, and now that I reinstalled my system I'm getting some weird errors. ------ MACHINE ------ i7-12700K, RTX3090 & ARC 310, 64GB DDR5, NVME SSD. I'm running Linux Arch (6.9.1), and Hyprland WM (Wayland). I have 2 GPUs in my system, I use ARC 310 to run the system on startup and for light work, the RTX 3090 if for heavy use in the host (Nvidia Prime) or in my Virtual Machines when need it. I can load and unload Nvidia kernel modules on-the-go and use the GPU when I need it. I know it sounds convoluted, but it works perfectly and it's officially supported by NVidia. X-Plane 12 runs very well on my system. When I run it via nvidia-prime it is the only process on the GPU, and I enjoy smooth 80fps+ graphics. I own multiple payware aircraft addons and they run perfectly fine (Felis 747, VMAX 767-400, X-Crafts E175) on this system. To be clear I've tried to run the CL650 on a vanilla XP12 installation first with the same results (crashes), so you can't blame the other add-ons. I have no extra Plugins installed in /Resources/plugins (besides what the installer puts there). ----- SYMPTOMS ----- (1) The aircraft (v1.7r1) loads just fine. I'm presented with the "Select Mode" screen. When I click the "Career Mode" i see the list of the Airframes, I can create/delete airframes and edit avionics options just fine. Now what's weird is on the right side (Saved States) the status is showing as "Parked" and Position "N00 00.00' E000 00.00' 0 KIAS at 0 ft. When I click "Enter FBO" the button changes to "Confirm?", and when I click that it hangs. It doesn't crash-to-desktop per se, just hangs. And as I later found out the X-Plane is dumping "--=={This application has crashed because of the plugin: Challenger 650 by Hot Start}==--" into Log.txt file at a rate of about 1GB per 10 seconds (yeah). Millions of lines. I have to issue a kill command to end the process and stop writing. (2) When I load the plane in "Non-Persistent Mode" it starts just fine (cold-and-dark). I did a couple of flights with it in non-persistent-mode and everything seems to be working fine... until it's time to shut down the sim (or change the aircraft) - when you press Alt+F4 (or select Exit from the menu) it hangs again just like in the Career Mode. ----- LOGS ----- I uploaded 2 logs - one from X-Plane (Log.txt) - I had to cut the end of it as it was over 500Mb of "--=={This application has crashed because of the plugin: Challenger 650 by Hot Start}==--". One thing I see right away is line 190: dlerror:/home/raf/X-Plane/Resources/plugins/Gizmo64.plugin/lin_x64/Gizmo64.plugin.xpl: invalid ELF header Then I get a bunch of sound FMOD errors, but the system doesn't' crash on that, it crashes after line 3927 "BOOT: pl21_fini" I also ran strace on the X-Plane-x86-64 (X-Plane.strace), once again I had to cut the file as it was over 1GB in size, but you can see X-Plane plugin requesting state.bin file located in /Output/CL650/airframes/<airframe-id>/state.bin but the file isn't there. I manually created an empty state.bin file inside that catalog to see what happens, and once I did that CL650 did NOT crash in Career Mode after clicking on "Confirm?". I was presented with another window stating "You have checked "Restore position and trajectory" but the state was saved very far ... from X-Plane's current location. Clicking "OK" will move you to that distant location." And after clicking OK - it hangs... Log.txt X-Plane.strace

I've tried that. No joy. I also tried removing the /Output completely and let X-Plane rebuild the files. Still the same. I went as far as installing XP12 and CL650 on my Win10 Virtual Machine and then copying the output of /Output/CL650 into my Linux host X-Plane/Output. That time I could actually see proper coordinates when selecting the airframe, but the sim froze after clicking "Confirm?" just like before. Now what's REALLY odd is the model works beautifully in "Non-persistent mode". I did 2h+ plus flight today, no issues. I'm suspecting the plugin or a function within that plugin responsible for creating and/or reading "state.bin" file is the culprit.

Disable Zink in XP graphics settings, and report bug to LR.

I've seen the TV series. There was a time when I was obsessed with AK. I still love that state.

Fix will be in the next release. A beta is available via the Hot Start Discord.

We already know, but thanks for the report!

Surprised to see this was not responded to. This is a very detailed aircraft, it is a shame you cannot use your georeferenced MAPS with it. Avitab was ok for its day (long ago) but have you seen the new tablets coming out with the new aircraft? A tablet with a performance calculator, balanced field length computation, and more is needed for such a high fidelity bird. Also it would be nice to have the engine sounds in the back with the speakers, and what little ATC there is to come through the headset...just saying...fine plane, but if x-plane won't do it, maybe HOTSTART will - it will only improve the product.

As the video shows, turn the big knob in the direction of the engine to fill. Eventually it will be modelled in 3D just as shown below.