Pils

Post your Log.txt, and read this: https://support.torquesim.com/hc/en-us/articles/360057635513-Steps-to-resolve-plugins-not-loading-Error-Code-126-

Shocked. (Not shocked.)

It’s all in this thread…

I'm with Ben on this one, tbh.

Multiple people have watched these videos and none of it makes sense. We are going to have to "go nuclear". You'll need to try removing all third party plugins except Gizmo64.plugin, and also unplug all additional hardware except basic controls for roll/pitch (because no-one wants to use mouse yoke!). We can also offer access to the V1.8 beta to see if it's reproducible there, if you'd consider joining the Hot Start Discord server. Please let me know. Thanks.

Sorry for being curt, not my intention to express anger. What I meant was we have discussed this with the Hot Start developer, they are very aware of this issue, and I'm almost 100% certain the CL-650 is using the XPLM SDK in a perfectly acceptable and normal fashion. I am no such confidence in DataRefTool; it is well known to use "hacks" to do its job (I agree, the result is very useful!).

You’d have to ask its author.

https://forums.x-pilot.com/forums/topic/22996-wow-even-without-a-proper-manual/?do=findComment&comment=181548

Please capture the value of this dataref over time during one of these “upsets”.

Personally I think not allowing any wiggle room is poor software design myself.

https://discord.com/channels/397379810067742721/397408003348889600/983476367909871676

https://discord.gg/FW7Khpwe

There’s a checkbox on the right hand side of the Graphics settings in X-Plane. It may have been automatically enabled, if so, I can only apologise on Laminar’s behalf as I believe this is a premature decision.

Don’t use experimental features, i.e. Zink, until official support is published.

Using the custom baro_up and _down commands may be more effective. (When in doubt use custom over default.)

You’re using a hardware display rather than looking at the virtual cockpit displays?

Was already requested 14 months ago. I have no problem setting barometers using the X-Touch Mini personally.

Challenger does not use the default altimeter gauges in any way, as with almost everything, they are implemented custom within the Pro Line 21 avionics. Some things are bridged back for read access by third parties, but are not synced two-way in order to cleanly maintain the state inside the aircraft.

Disable Zink.

Once LR and/or AMD fix their driver bugs, Zink will be supported in the next version of the Challenger (V1.8; a beta of which is available via the Hot Start Discord). Unfortunately there’s nothing else to be done in the meantime.

Don’t use Zink.