Hallo Zusammen,   folgendes Update v. 05.12.2025 habe ich soeben gefunden:  

Please login to display this image.

  Gruß Reiner C.

What is the full path of your simulator folder and your community folder ?

You could emulate a faster trim with some programming. Measuring the time between two pulses and if the the time is shorter than a certain threshold, increase the trim position by 5 instead of 1 for instance. This could be maybe achieved with Axis&Ohs addressing the trim Lvar. But overall, the decision by Honeycomb to make the trim an encoder instead of an axis with limits was for compatibility and ease of use. 

Nachmeldung:   Ich hatte in 'Resources/Plugins' noch einen Eintrag bezügl. Navigraph/Simlink. Nach der Löschung der Datei war der Fehler behoben.   Problem solved!!!   Hallo XP-Flusi, hallo Horst,   Sorry, hatte es eben etwas eilig. Danke für eure Hilfe.

Hallo Horst,   da ich auf Navigraph nur ein- oder zweimal im Jahr zugreife, habe ich jetzt Navigraph deinstalliert. Das hat auch keine Lösung gebracht. Allerdings finde ich in meiner log.txt noch immer diesen Eintrag:   [NavigraphSimlink_64.xpl]: Dataref 'sim/weather/barometer_sealevel_inhg' has been replaced. Please use the new name. Loaded: D:\X-Plane 12/Resources/plugins/NavigraphSimlink_64.xpl (Navigraph Simlink for X-Plane).   Wie kann ich diesen entfernen, soweit das überhaupt möglich ist?   Gruß Reiner C.

Im Link ist die Lösung leider nicht zu finden, da die Seite von 'HALYX' leer ist.

I'm pretty sure, it doesn't have an acceleration feature. You said I could multiply up the number of events. How?   Rotary encoders are fine, I don't have a problem with them as I worked with many of them as an engineer. You could easily map an axis to the encoder and set limits. And the autopilot just does its thing without having to set the hardware. But I admit that this doesn't work when absolute positions on the hardware side are important. Then motors or servos come into play.   It gets even worse. When using it in VR, the number of events is even smaller. And a lot smaller If I turn up the resolution in VR. Then the trim wheel in the 172 is barely moving... I'm assuming that the UI and graphics are processed in one thread (or task?). I'm sersiously thinking about building my own trim wheel...

I don't have this product, so I can only comment in the general case. A major benefit to using a digital encoder for trim is that it is compatible with an autopilot. The autopilot takes over the trim, and if you use an analogue (absolute-positioning) control then obviously it cannot change this unless it is motorised. This means when you switch off the autopilot the aircraft trim will not match the setting of your analogue control. You won't notice this until you touch the trim (although this may be sim-dependent), at which point you may get a violent excursion if the trim is set far from where it was when you engaged the a/p. (This will also be impacted by which vertical autopilot modes you have used in the meantime.)   If the Honeycomb device has a driver, it may be that the driver is controlling the pulse rate. If so, I would expect it will also have an acceleration feature, so if you spin it fast you should get faster pulses. You could probably circumvent that by not using the driver, although that may remove other functions (the gear lights being the only obvious one). It ought to just send pulses as button-clicks for two independent buttons, which you could program some other way. In the simplest case you could just multiply up the number of trim events you send from each pulse.

Moin Reiner,   hast du denn die aktuelle Version von Simlink installiert? Aktuell ist bei mir die 1.1.40.1707.   Gruß Horst

Im Org Forum wurde mal von einem ähnlichen Problem berichtet.   Problem war Navigraph Simlink.   https://forums.x-plane.org/forums/topic/168607-windows-file-explorer-opens-with-xp11/#findComment-1648514