skiselkov

I've had this happen once and found it's one of the master WARNING|CAUTION buttons getting stuck. This sometimes happens if your mouse push & release happens on the same X-Plane frame - X-Plane then doesn't deliver the mouse-up event to us and thus we continuously think you're holding the button pushed in.

This also produces a while "EXTERNAL DOOR OPEN" CAS message, which alerts pilots to the fact that some service panel isn't closed and locked.

The ENG BLEED line on that page is only informational. The engines will readjust lower after a bit to try and pull out of the red. If that doesn't happen, you can set a lower N1 target in "TGT" (LSK R3). Then push LSK R3 to activate the reduced TGT value and that will get the ATS to pull back even further.

Thank you, I've managed to reproduce this bug and fix it. Fix will be in the next update.

Folks, I've identified what the issue is with xPilot (I don't have IVAO or the LiveTraffic plugin). xPilot is setting the weight-on-wheels dataref for all aircraft contacts to permanently '1', causing the CL650's TCAS computer to exclude them from display or computing TAs or RAs against them. I've submitted a bug report to the xPilot project, so fingers crossed, this will be fixed soon on their end. It's likely possible LiveTraffic and IVAO have the same bug.

If you are seeing this message, the most likely reason is you attempted a flight plan fetch from simbrief, but didn't enter a valid simbrief ID in User Settings. To correct this, log onto Simbrief and grab the number from this data field: Enter that number into X-Plane under Challenger 650 > User Settings > Networking > Simbrief Pilot ID. This should take care of the issue.

Here's the problem:

The MFD with the EICAS on it cannot show charts, as EICAS must always be displayed *somewhere* - the avionics enforces this. You can use the other MFD for charts, or move the EICAS off the MFD to some place else using the "EICAS" knob on the reversionary panel.

Excellent bugreport. Will fix. Thank you!

Great report, shouldn't be difficult to fix with a repro case this precise. Thank you for that.

Needs updated data from Navigraph or Aerosoft NavDataPro to show a secondary database. Otherwise, you will only see the X-Plane 11 stock nav database.

Please be sure to enable a VPN on your computer. The aircraft needs to talk to https://navcen.uscg.gov to download a GPS almanac - this is needed to simulate GPS satellite positions.

Don't reload while the simulator is paused. Due to the sheer number of sound events we have in the plane (>2500) FMod gets itself bungled up. Unpause, then hit reload. That should work.

Well in that case, it's probably as a consequence of the ground impact. I'll close this for now, as it will not reoccur unless the aircraft hits the ground.

To avoid this: Do not use groundspeed acceleration Do not drag the airplane around using the map after the avionics is powered on To reset alignment on the IRSes, we need to use a debug menu. Select Challenger 650 > Study > INS > Realign IRUs Immediately and confirm:

When the APU encounters a fault, you'll need to hop out of the plane and reset the APU ECU to clear the fault. Go to the tail of the aircraft near the cargo door, pop the latches and pull the little door open under the left engine nacelle: Inside you'll find a panel with 3 buttons. Push the "RESET" button, close it up and you should be good:

Can you please temporarily remove all plugins from Resources/plugins (except Gizmo). Something is really messing up view positions and that is tripping an internal check in the HUD visibility code.

This log doesn't show a crash from within the CL650. Please be sure to upload the log right after you get the crash, so we can see the exact last one.

Investigating!

Yeah, Centos7 may be just a bit too old on the libs being shipped. Looking at the release info, it came out in 2014, which means the lib major revisions are from that year. Afterwards Centos only ships bugfixes & backported security patches, not new functionality. I usually test as far back as Ubuntu 16.04, but really 18.04 (i.e. around 2018) is the cutoff for how old of a distro we support.

What distro are you running? The issue is in missing symbols in some basic libs: OpenGPWS.xpl: undefined symbol: _ZTINSt6thread6_StateE X-TCAS.xpl: undefined symbol: _ZTINSt6thread6_StateE systems.xpl: undefined symbol: __cxa_thread_atexit_impl _ZTINSt6thread6_StateE is normally found in libstdc++.so (the standard C++ library) and __cxa_thread_atexit_impl is found in libc.so (the standard C library). I build & test on Ubuntu 18.04 LTS.

Looking at the log, I believe you're hitting the same scenery as the user on our Discord. The issue is VirtualDesign3D's SCEL because of this nugget of a great airport name encoded in the apt.dat: "Arturo Merino Benítez International__de X-plane octubre-2016" You can temporarily work around this issue by going into the scenery, there should be a subfolder named "Earth nav data", inside which you'll find "apt.dat". Open it up in Notepad and near the top should be a line that looks like this: 1 1555 1 0 SCEL Arturo Merino Benítez International__de X-plane octubre-2016 Just trim down the name at the end by deleting the "__de X-Plane..." stuff and save it. Then it should load fine.

Hey CJ, thanks for the input. I checked this with folks who consulted for us during the development - the landing lights switch takes precedence over the PULSE system, so if you set the switch to LDG, you will get steady lights, regardless of what the PULSE system is selected to. To get pulsing, you need to select the landing lights switch to either TAXI or OFF and then select the PULSE switch to on.

Cannot reproduce. I tried both normal point-to-point navigation and OBS mode. As you can see, I have BRG1 selected to GPS and it's showing the correct target.

Looking at that traffic global screen, all the contacts are more than 10,000 ft away from your altitude. TAS/TCAS only shows contacts that are within +-2,700 ft in normal more or +-10,000 ft when in UNREST (unrestricted) mode. Can you check if they appear when they're within 2,700 ft of your altitude?