Pils

Reported to developer. Thanks!

Anything that isn’t part of the core “pilot job simulation” is probably going to be at the bottom of the backlog but you never know.

Eventually, yes.

Yes. One hopes minor, but going to depend on how the weather addons synthesise their injected weather.

Appreciate the feedback and desire to help make the product better!

I understand, I’m just explaining why they’re different; one is LR logic, one is Toto logic. If a change is going to made it’ll likely be made to every knob that uses the latter, so will need to be considered with care.

Direct from real world sources.

Yes, due to integrity checks, but maybe replacing it wholesale could work? Very unsupported though! And we only give supported answers.

Read closely you’ll see IVAO clients are not supported as there is no way to determine whether one is connected to the network or not. Once the authors of the clients provide this mechanism then we will look into supporting it.

You are the only one to report this issue, unfortunately for you. I’m sorry it’s happening. Can you provide screenshots of the Plugin Admin window, the tab with the pie chart, for steady state vs. the “stutter”, please?

No, I think “developers” in this context are the X-Plane developers; the response is being written from the point of view of the technical support person. They still provide no actual reason to think it’s Hot Start’s code, they just don’t want to deal with their own bugs. Plus Librain is not part of the addon at this time.

Default commands? They have their own behaviour. Mouse wheel acceleration is tuned per knob at least. Setting minimums should be quicker in the next update.

Ok I've confirmed this behaviour and reported it to the developer.

Could you provide your Log.txt from a sim session where this fails. Thanks.

We will pass this feedback onto the developer.

Thanks to some dogged investigation by @oisin650 it seems that the FAA only retain charts for the current and previous AIRAC cycle, e.g. at time of writing, 2201 and 2113. The CL-650’s digital charts function uses the AIRAC cycle associated with installed custom nav data (if present), or default nav data otherwise, to fetch the charts from the FAA. (Which makes sense, one would want charts to match one’s nav data.) However, this means that if one only has default nav data then the FAA chart function is unavailable, because X-Plane ships with nav data from 2018 and these charts have long ago been removed from the FAA’s digital chart service. The solution right now is to have up to date nav data, this is available to purchase from Aerosoft or Navigraph. (I highly recommend the Navigraph Ultimate subscription that gets one access to global Jeppesen charts in the avionics instead! #notsponsored)

The latest version accidentally triggered unexpected behaviour in Rosetta that really does a number on the aircraft systems. A fix is in the works. Appreciate the understanding and patience.

Are you on an M1 Mac running Monterey?

Yes, it can be landed with ATS engaged if you desire, and is done in real world ops regularly.

Try in non-persistent mode for greatest reproducibility, please.

Thanks for expressing your support, the more people we hear from the more it helps prioritise. In the meantime, can you set datarefs with that tool? Because if so just use those and force the switches to match your hardware on load? Or does it not change the value until the switch is moved for the first time?

CL650.lua Throw this into your FlyWithLua scripts directory. With DataRefTool one should be able to implement basically any switch one would like based on these examples.

It was changed to be more universally applicable, feel free to edit the checklist.xml and do your own SOP.

Interesting. I’ll have to try that.