skiselkov

This is indeed normal. The reason is quite simple: the ATS needs an N1 limit target to operate. Otherwise, it would have no idea what the maximum allowable thrust is. This value is supplied by the FMC. The FMC uses performance tables made by the aircraft manufacturer to determine what the takeoff thrust limit is supposed to be and if I show what the table looks like, you'll immediately see the source of the problem: Your SAT is +35 C. At that temperature, the FMC has no data to compute a takeoff N1 target, so the target blanks and the ATS goes to FAIL (and cannot be re-engaged). Take the cowl A/I off, FMC goes back to the normal takeoff tables and voila, ATS is back in business.

Thank you, fixed. Will be in next update.

Fixed, will be in next update.

Fixed, will be in next update.

Fixed, will be in next update.

Please don't file multiple reports into a single topic. Makes it difficult keeping track of what was fixed and what wasn't. Having trouble reproducing this one (doesn't crash for me). So I'll try an analytic fix without verifying it.

Excellent report. Reproduced & fixed in next update.

Resolved, fix will be in next update.

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.