Pils

I’ll pass it on and hopefully will be considered for a future update when the pop up feature is looked at again. Thanks for the suggestion!

Unknown at this time.

I think that’s Cycle 2003 vs. Year 2018, they’re not directly comparable. If you want to know what cycle is in use by X-Plane’s default nav data you can check the files in Resources/default data (if I remember correctly). The header will say the cycle number. You may be able to change Simbrief to match.

What we’ve been told, and this is from a small number of operators but it sounds reasonable to me, is that if the principal owner is onboard then an attendant isn’t necessary (though they may want one anyway, if they had guests, for example) unless the flight is transatlantic (if I remember correctly). However, if it’s charter passengers then an attendant will usually be there to help them with any questions, service, and well, to make sure they behave.

When a cabin attendant is not onboard the pilots have a version of the panel on their iPads hooked into the cabin WiFi. For now this can be emulated by using the pop up, available via key bind.

It uses X-Plane 11’s Custom Data. Process for enabling in the sim is in the FMS Primer document.

Unfortunately that may be an error in the document (we are checking), of the two I know that Fin Number is supported. The location in Simbrief is highlighted in the primer document. It may or may not be part of the OFP format you use. That’s up to you, but it’s not necessary if everything is working correctly with the uplink. If you mean in Simbrief, then no.

This specific issue has been fixed by the developer and will come with the first update. Thanks for helping improve the product!

You can refer to my Honeycomb Bravo profile to see which I’ve been using with success. Feel free to post a more useful Xsaitekpanels configuration to the forum and I will feature it.

It is currently not possible to make the multi panel display work for autopilot data. The knob may work if the correct default commands are used.

Could you post a Log.txt please so we can get your specific desktop arrangement, thanks.

Are you familiar with DataRefTool? If so can you see if your hardware is somehow overriding the dataref for battery/avionics that Xsaitekpanels is using? It sounds like it’s being forced off, but just a guess. My .ini specifically disables the battery switch on the Saitek so I haven’t tested this scenario.

I tested my ini again with latest beta and the radios work fine (both com and nav, even one of the ADFs!). That panel turns on when the main battery is on. I suspect you have another issue, such as with USB power management (Google it). But I'll try to test in the retail version just in case there was a regression before release.

There’s a workaround for the issue with xPilot but unless other addons correctly set the “weight on wheels” dataref for TCAS if/when this workaround is removed they’re going to have problems again. You’ll have to speak to the authors of those addons.

Using the menus should allow checklist to be reset, including F/O.

That’s a pretty common baseline these days tbh.

Press Update Licenses Now and reload? Also may want to redact your email.

Please post Log.txt after a failed attempt

In non-persistent mode there’s no FBO to tell how many pax there are so you use the X-Plane weight & balance interface to set the payload (and only payload, don’t touch fuel!). In real life you don’t magic people into existence by typing into the FMS so you don’t in this simulation either.

Thanks. I think there’s a piece of the puzzle missing because I set up this curve like yours, tested it in the default 737 while watching datarefs you mentioned and it worked, however the same dataref changes didn’t happen in the 650. Hopefully there’s some obvious switch in Plane Maker that they can find.

I'm sure that's because most addons are using default systems so get this "for free". I imagine the developer just didn't consider someone using a setting that seems made for turboprops not jets (it has "beta" in the name, and forces you to have a beta range in the curve, even if it's tooltip mentions jets, no-one looks at tooltips, including me until now...). But if I can figure out how it works then I can request support. No promises. As such, how did you get the second column of numbers to change? Every time I do it resets to 0.17, 0.33, etc. Don't worry, I figured it out and it's messed up, stupid X-Plane. But I still can't figure out how this is meant to work on the backend. Of course it can but it's going to take custom support because this addon isn't using any default LR systems unlike every other addon in X-Plane.

In the meantime a Lua script can be used to set the dataref.

You're referring to the toggle command pedestal/gear/nws? Yes, there are a lot of switches that have only toggle commands. Adding more discrete position commands is something I will be discussing with the developer for a future update. In the mean time, every switch also has a dataref that can be used to manipulate the switch position, e.g. for the nose wheel steering switch setting CL650/pedestal/gear/nws_value to 1 will move the switch to ARMED. A Lua script can be written to do this via custom command (along with one for the corresponding OFF position). I hope that helps in the meantime.

After the current work in progress is done I’ll ask the developer, no promises however.