Danke für den Hinweis! 

Hallo, Horst,   danke für Deine prompte Antwort. Ich werde sehen, ob es was bringt und dann berichten! Gruß Hajo

To multiply the number of events you'd need to be using a third-party programming tool like SPAD.neXt, or anything that lets you map multiple events or actions to a button click. Then you'd just map two or more 'trim up' or 'trim down' events for each pulse. From memory, I think I have typically programmed five at a time. If you do build your own, have a look at MobiFlight, which is for programming Arduino devices. It is free, almost trivially easy to set up, and it has acceleration features built in for encoders.

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...