ois650

Hello, I've logged this now. For reference, your cruise was never FL190, your cruise is always the highest level specified in your flight plan. Don't take what Simbrief puts in the little box, take it from the OFP. TUPI1V TUPIX Y135 NAPES/N0464F380 UN747 AMOTA UT312 BAZAS/N0465F370 UM192 ROLAS/N0463F380 UN851 RUXET RUXE3N Thanks

Thanks for your report, it's likely the same thing happening to a number of users so I'll be closing this report without logging it as an individual bug. Brgds

Hello, your backtrace points to an X-Plane crash. If you find this is happening repeatedly I'd recommend you remove plug-ins to identify the offender. Thanks

Hello, This is the support forum for the Challenger 650, not X-RAAS. Unfortunately we can only guarantee support in the English language. I will be closing this report. Brgds

Forgive my ignorance, but what is "jxpnex"? I am unfamiliar.

Evening, Your new log enabled the developer to add some new code which should (fingers crossed) prevent this from happening, based on the backtrace. This will be included in v1.6 Thanks

Hi Rich, hydraulic system 3 must be pressurised to open the nose gear doors. Unfortunately there's no other way.

Hello, I spent forty minutes testing this extensively with 1.5.2 and ran into no issues. Tests were: Failure, no CAS message, HDG to NAV Failure, no CAS message, NAV to HDG to NAV Failure, CAS message, HDG to NAV Failure, CAS message, NAV to HDG to NAV All of the above with new directs Engine failure, HDG to NAV, HDG to APPR Looking at your log it's definitely the Challenger crashing but it's just the same as last time. I will refer this back to the developer.

Hi all, changes have been made to the beta build to eliminate this behaviour. This will be included in the next release.

This issue/request has been fixed/implemented/modified in version 1.5.2

This issue/request has been fixed/implemented/modified in version 1.5.2

This issue/request has been fixed/implemented/modified in version 1.5.2

This issue/request has been fixed/implemented/modified in version 1.5.2

This issue/request has been fixed/implemented/modified in version 1.5.2

This issue or request has been fixed/implemented/modified in version 1.5.2

Lassen Sie Deiner Motoren maximal laufen. Es ist schneller!

Hello, Thanks for your report and for going into good detail. I have logged this for further investigation. Brgds

Folks, this is not a Hot Start issue. You need to push IVAO client teams to work on this. You will notice that X-Pilot works perfectly.

Thanks all for approach examples. The oscillations here are related to glideslope guidance, so far we have not observed any issues with the climb.

10 minutes to landing is a good rule of thumb, though it can be completed at any point below FL150 (for APU start).

Use the CCP upper menu to navigate to Checklist and you'll be presented with this menu. Just click "push select" on the CCP and you'll open up the list of checklists. If your FO is running through the checklists hit escape on the CCP and you'll be back out in the menu.

The frequency is in the navdata anyway, I entered BSO into the TUN page and it correctly tuned 110.00 - there's just no DME.

That would be great, thank you. Please upload as either an MP4 or a YouTube link. Brgds

Unfortunately I was unable to reproduce this. If it happens again make sure to follow up here.

Logged for further investigation, thanks.