ois650

Logged

Unfortunately your log comes to an abrupt end rather than a backtrace, meaning we can't trace this crash back to the Challenger. Make sure to post any further crash logs.

Logged for investigation Brgds

Thanks, will take a look into this.

Oh dear! If that happens again please post a log to this thread.

This is intended and most operators use ABV/BLW mode.

Interesting backtrace, just cruising and it crashed or were you doing anything in particular?

Hello, Which procedure is this? Thanks

Hello, Please detail the exact steps you took which led to CTD. This will aid in reproduction. Thanks

Hello, this CTD was un-reproducable in the current beta version so you can consider this issue fixed for 1.6 Brgds

Hi, please provide a full flight plan so we can attempt to replicate this. Thanks

Hello Cam, Thanks for your report and sorry to hear about your experience so far. The first log indicates a crash due to an FMOD error. The second and third logs are X-Plane crashes (as in, caused by X-Plane itself). I would recommend running X-Plane on one monitor and seeing if that prevents the crashes. Brgds

Will be included in upcoming 1.6 release. Brgds

Rudder effectiveness has been improved in a recent beta update as well as general V1 cut handling (acceleration with OEI). You'll see this in 1.6 release in hopefully not too long...

Do you have night vision enabled?

Additionally if you're flying offline the Challenger is doing it's own thing with the atmosphere - disregard XP11's output.

If you followed the checklists there shouldn't be any problems. If you send a screenshot maybe we can figure out what's going on.

From a 650 operator. CL60/M-SACDE1E2E3FGHIJ1J4J7RWXY/LB1D1 PBN/A1B1C1D1L1O1S2

Makes total sense ^^^ Spot on

My European brain can't fathom routes with discontinuities in them! Direct direct direct with no airways please! FMS-6000 doesn't allow this and the 605/650 manual words it almost identically to Textron's PTM. Filed up for fix, nice one!

After some discussion I think we're gonna put this down to a "vatsim-ism". Though it was nice of Moncton to give you a clearance, that isn't how the real world works and therefore the oceanic clearance will not work. Unfortunately there is a limit to the "vatsim-isms" that the Challenger can accommodate and we recommend that you revert to voice in the event of receiving an oceanic clearance off a non-oceanic controller. "Problem on the controller's end" probably most appropriate!

Can we have the full log please?

Just a "vatsim-ism" I guess Will take a look

Turning the HDG selector and taking off - sounds like correct behaviour. Changing selected altitude shouldn't kill managed speed. Will take a look at this

Autorouter only works for Europe. You'll need to use Navigraph for the Middle East.