Pils

You mentioned selected an arrival, but you didn’t mention selecting an ILS approach/runway, just want to be clear of the situation. Assuming yes, you need to make sure both Pilot and copilot side are in FMS navigation, and the nav source preset is set to VOR1 and 2 (or LOC1/2).

CDU -> MFD DISP -> WINDOW to ON (VNAV is the default)

Reported to developers, thanks.

Not currently, as it’s basically considered useless by real world pilots, and even if it’s installed it’s never used more than once, and would be a non-insignificant amount of work to implement. Never say never.

Correct.

I don’t work for TorqueSim so I don’t know what their packaging strategy is, but maybe they considered some libraries to be standard on their target distribution (probably a specific version of Ubuntu). https://linux.die.net/man/1/ldd

You’re missing a shared library so the systems plugin won’t start dlerror:/home/tim/X-Plane 11/Aircraft/X-Aviation/TorqueSim SR20 Entegra/plugins/sr_systavi/lin_x64/sr_systavi.xpl: undefined symbol: ASN1_ANY_it

Yes, still planned.

OP wrote (in a misplaced user report): JudyS Submitted April 7 Apparently I did not provide enough information. i purchased a navigraph subscription and installed the data in X-Plane. when I start X-Plane and select start a new flight, I can select airports with detail from anywhere in the world because the navigraph data is there searchable and selectable. however when I select the torquesim Cirrus g1000 ( latest version from x aviation) and start the flight, the plane is sitting at the selected airport. However when the FPL is selected on the MFD, the airport data is different than the Navigraph data and does not have all the details it should have. The aircraft is not even geographically located at the right place based on the map on the MFD. clearly the data are not in Sync. would appreciate some help resolving this.

Cam would be the authority, but yes, I believe so. Each computer is authorised as a whole.

Forward of the thrust levers, centre left.

Forgive the obvious question, but have you turned the nose wheel steering switch on? The nose wheel must be mostly straight before doing so.

Can you provide a link to this previous report, please? Also, please provide the full Log.txt and specific examples of airports/runways. Thanks.

Can you please use non-persistent mode to test the procedure? Just to eliminate an airframe issue. A video starting from before you got into FAIL would also help.

Please make another video? To be safe, do not use the default TOGA command binding, use the custom ones, if you’re using a keyboard or joystick button.

The ATS button isn’t the “I want to get a thrust rating armed” button, it’s the “I want to engage auto thrust and fly right now” button, kind of like the TO/GA button on a Boeing.

Double check the thrust limit page.

You should see an improvement.

Sorry to hear that. Good luck. I hope you’re into the virtual skies again soon.

Ok, then you should disable whatever blocked that file from being installed and run the CL-650’s installer again. If you’re generally concerned about PC security, reasonably so, run the subsequently installed XPL file through VirusTotal before starting the sim, you’ll find it’s “clean” and safe.

Patience, please. There’s another big update coming.

Can you check if this file exists …/X-Plane 11/Aircraft/X-Aviation/CL650/plugins/systems/win_x64/systems.xpl ? I’m guessing your antivirus has blocked the install or loading of this code.

Most likely you don’t have the Gizmo plugin installed or running. Please check your Log.txt.

Can you provide screenshots so we can better understand the scenarios, please?

Ah. Unfortunately that really only works with default/basic aircraft addons, not complex third party ones with custom systems like the CL-650. You’ll need to use the 650’s own state saving system via Airframe Manager.