Pils

Please don’t assume your crash is the same reason as another person’s. Please always make your own post in the future.

Please don’t assume your crash is the same reason as another person’s. Please post your Log.txt here.

Please don’t assume your crash is the same reason as another person’s. Please post your Log.txt here.

@MrScott There was a bug with the pop out window position saving in 1.0, I believe it’s fixed in 1.1, but if not it will be for 1.2.

Sorry I missed this post until now. I don’t think this is anything hardware-related to I’ve moved this thread to a more appropriate sub-forum. However, it’s possible the nose wheel steering isn’t armed, it needs hydraulic pressure to function. Secondly, it’s possible it won’t arm due to the wheel angle, in which case use differential braking or BetterPushback to realign the nose wheel so it’s straight. You should then be able to use the twist grip yaw to steer.

Yes. The developers worked with consultants who fly the CL-650 as their job.

And what was the approach into KATL?

Please provide full flight plan inc. runway and approach selection.

Possibly. But it would require a means to swap between AviTab and the panel, which has some design complications. I’ll pass on the suggestion.

We’ll discuss it with Toto.

Unfortunately much higher and it would be more likely to intrude on hangar roofs. Which is a more likely place to park a business jet than an airliner stand.

Unfortunately, and I know this isn’t what you wanted to hear, but to my amateur eye (not an X-Plane developer, etc.) these crashes all seem to be caused by X-Plane itself, not code within the CL-650 itself. Without more detail in the log there’s not much the addon developers can go on. Maybe @Cameron has some tricks up his sleeve? But in the mean time it might be worth contacting Laminar Research’s support: https://www.x-plane.com/support/

It has been, and continues to be, considered. As you can tell, the developers don’t do something unless it can be done right. So that’s where we are.

Both of these datarefs should be set correctly in 1.1. If you can provide more detail on Pilot2ATC’s use of datarefs in X-Plane we can investigate more. Otherwise the workaround above seems to me that they have accounted for this situation already.

That’s correct, it’s not currently supported. Request has been logged with the developer. Monitor below thread for updates.

What exactly did you type in the scratchpad? Thanks.

I set up my TCA Airbus on my beta copy of the 650 (which is basically identical to 1.1r1 that you have) and had no problems using the binds/curves as attached. Please provide more information about your control profile.

This’ll have to be looked at by the developer at a later time of the day. In the meantime the last thing you can try is backing up and then deleting the CL650 directory from Output. This will reset all saved state.

Can you provide a Log.txt too so we can see the exact monitor configuration that X-Plane sees, thanks.

No, if you’re going to do it, do it when on the ground during preflight.

Should be fixed in next update if I recall.

Or there’s still pressure in the aircraft!

Despite the name this website has nothing to do with xPilot the Vatsim client. You want their Discord for support via https://beta.xpilot-project.org/

It was brought up within hours of the release, and hilarity ensued. It’s fixed in the upcoming update, keep an eye out! Thanks for the report.

I’m pretty sure that’s just a label… the G1000 navigation is mostly Laminar’s and it uses the custom nav data just fine. If you don’t have missing approaches or waypoints then don’t worry about it.