flightwusel

It is a setting in the beta version.

To persist the state and settings and then just change the livery?

Re: non-persistent mode Yes, it skips outside checks. I forgot about that one. Re: state saving You are right, too. One needs to de-select "Restore position and trajectory" to make them useful as a "ready for engine start" state for example and one needs to go through the FBO then. I had to play around with it just now to grasp that. Sorry. That's not really self-explanatory in my opinion.

I've had it sitting in the hangar for half a year until I had the guts to dive in... IMHO that initial step is steep not because of the aircraft's systems but because you have to learn the FBO, the walking (and ducking!), operating a door etc. Then you never know if you'll fall out of the sky if you forgot a step (do I have to do the flight planning in the FBO? Do I have to take passengers?). That might sound ridiculous but that was what intimidated me. Once you prepared the aircraft from the outside and fueled it this can be a very smooth experience even for newcomers. Now after many many great flights I just immediately click the door at the end of the FBO lobby, have configured the 650 not to overwrite my go-to-cockpit-button (W!) and can hop in directly. I never put on the chocks, pins and covers, discovered how to fuel from the inside and am now REALLY enjoying the stunning avionics and depth of the systems. Just sayin'. The FBO is a neat idea. But a "Skip to cockpit" and a "Perform walk-around actions" in the menu would be much appreciated. Re: Saving airframes: while gives you the state you left it in (which helps), it is not the same as being able to save and recall states.

I AM asking one of the authors. You don't have to be so mad.

I am very interested in the Entegra avionics, but I am unfortunately on Linux. Could it be added again without official support (just as Laminar does it for X-Plane with OS Support: Linux: Varies?)

Ah, by the way: Disabling DataRefTool in the PluginAdmin, then loading into the Challenger, then re-enabling it works for me.

I really love DataRefTool over DataRefEditor. But as mentioned here in the forums in several places X-Planes crashes to desktop with "--=={This application has crashed because of the plugin: Challenger 650 by Hot Start}==--" when the DataRefTool plugin is loaded. (DataRefTool 2.3.0, Challenger 1.7r1, Manjaro Linux) My question here is if we have any idea why that is the case?

I want to set the baro to a value, not manipulate it with a knob... I have a FlyWithLua script that sets the altimeter to QNH/STD when pressing a key. Will try the custom CL650 commands but would take me wonder if it would work much differently from the sim/instruments/barometer_up which changes by an arbitrary amount (it is 1 tick but it could be in inHg or hPa mode and I don't see a DataRef to find that out...). It is working with my slow naive feedback loop, but not very reliably (sometimes it overshoots although I wait 1s for the values to stabilize).

Ok, I am not able to do it reliably. Can we please get writable DataRefs for barometers? That seems to be kind of basic stuff and will not upset the aircraft.

Thanks, that works albeit relatively cumbersome for such an "easy" thing. It's not that easy to automatically turn it to a given value because sim/cockpit/misc/barometer_setting has hysteresis.

You still should set appropriate speeds. But I am also yet to understand the autotune (nav-to-nav) functionality. I've found this thread which contains many hints:

This is not exactly a hardware question but this section seems to fit well. I would like to change the barometer setting via DataRef by writing final values (e.g. 29.90 inHg or 1010 hPa). The Challenger does not react to changes in sim/cockpit2/gauges/actuators/barometer_setting_in_hg_pilot sim/cockpit2/gauges/actuators/barometer_setting_in_hg_copilot sim/cockpit2/gauges/actuators/barometer_setting_in_hg_stby though. Does anybody know how to change the altimeter baro setting from another plugin? If possible I would like to write STD on/off, too.

If I only knew that earlier... I've just meticulously tested all combinations of plugins, gamemode and mangohud until I arrived at the DataRefTool for a probable cause of my CTDs... Just when I wanted to post about it I found this thread. Could this be added to the documentation in a kind of install guide to help others? (Linux, XP 12.04r3, Nvidia RTX 3060)