Pils

The nose wheel bay door pin you mean? That’s what’s in the screenshot. Make sure the door switch is in the down position.

Under DISP MENU on the CDU, change WINDOW to ON.

Find the one that says IAPS 1 (I think it says) on CB1 (behind Pilot’s seat). You may have to pull it (click and hold) and then push it back in.

Can confirm as a past user.

Also acceptable. There are different real world SOPs. The hints will be updated to reflect that in the next update.

Punching in 90-91% is fine. The “trick” is you have to then press the same line select key to activate it (goes magenta). Try it out next time.

What are you setting? And are you activating/selecting it afterwards?

For charts or nav data?

You can use the same URL until it expires.

https://discord.gg/TRbdUhmD

Thanks. That’s sufficient for now.

Would you be willing to create your own post with your own video, please?

Indeed. Will be added eventually.

If you can’t use the xPilot standalone app window when connected to Vatsim then that’s not a problem with the TBM and you have bigger problems with your install. But I have no idea what might be wrong. Sorry. :-(

I’m not sure why it’s not working for you. Are you manipulating the radio/com panel in the sim cockpit? As a work around you can force xPilot to listen, send, and tune the radios using its text command interface: https://beta.xpilot-project.org/#/client?id=dot-commands

Not really, no.

This just isn’t how the ATS on the Challenger 600 works. The TO/GA button doesn’t engage ATS, it’s not a Boeing 737.

https://hotstart.net/cl650/pins.html

Do you have HDR enabled under Visual Effects in X-Plane graphics settings?

Other aircraft don’t have as many audio samples and as complex a soundstage as the Challenger. It’s really pushing X-Plane 11 to its limit. The developer has been in direct contact with Laminar on this issue. Maybe they will address it in 12. As Ben surmises, these paths are baked into the error messages as part of the executable by Laminar’s build (compilation) pipeline. They are nothing to do your local system and can be ignored.

Wouldn’t the default commands be sufficient?

As you know, but for the benefit of the developer, the Bravo doesn’t have any real detents in the sense of it being part of the lever’s axis, it’s just a “gate” before going into the button section of the lever movement range. I don’t have the Mu-2 but my understanding is the “detent” described in the documentation assumes an axis with a detent in the range of the axis, as some more “professional” hardware does.

If you’re talking about what I think you’re talking about then the problem is X-Plane’s shadow rendering and you can’t fix it, only Laminar can.

https://discord.gg/HHbJ6ECr