Announcement

Collapse
No announcement yet.

Problem binding rotary encoders to HDG and CRS switches

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Problem binding rotary encoders to HDG and CRS switches

    I tried binding rotary encoders to the HDG and CRS 2 way switches in the F-18, but looks like their standard DX pulse in each "click" is not long enough. Sometimes I see the switch in the 3D cockpit slightly moving, but the actual HDG or CRS value never increases or decreases.


    Then tried different DX pulse lengths with TM TARGET, where I can easily configure them. The standard 32ms pulse does not work and the maximum the GUI allows (50ms pulse) is still hit and miss. Sometimes it registers, sometimes it does not.


    Binding the encoders to other similar controls (COM channel, radio volume, RWR volume, etc) works just fine.

    Anyone has tried this?
    sigpic

    #2
    The switches for Heading and Course are spring-loaded 3-position switches in the cockpit, and the sim has implemented them as such. That's realistic. If they were implemented to work with rotary encoders, they would not work with spring-loaded 3-position switches.
    To make you happy, ED would need to produce an axis version of the HDG and CRS commands. But that would behave strangely when you try to command it with the mouse.
    LeCuvier
    Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

    Comment


      #3
      Originally posted by LeCuvier View Post
      The switches for Heading and Course are spring-loaded 3-position switches in the cockpit, and the sim has implemented them as such. That's realistic. If they were implemented to work with rotary encoders, they would not work with spring-loaded 3-position switches.
      To make you happy, ED would need to produce an axis version of the HDG and CRS commands. But that would behave strangely when you try to command it with the mouse.

      You should really refrain to make agressive comments like this when you obviously don't know what an encoder is or how it works. Hint: they don't work with axes.
      sigpic

      Comment


        #4
        I'm sorry if my statement sounded aggressive, it was not meant to be. Since I apparently (unintentionally) tend to offend you, I will not make further comments regarding the subject, which I understand very well. I have done a lot of customization and created axis commands in "default.lua".
        Last edited by LeCuvier; 10-18-2020, 10:57 AM.
        LeCuvier
        Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

        Comment


          #5
          I think the crux of the issue you're having is that the HDG and CRS select switches are designed to be held in one position or the other, as they're used in the real jet, not pulsed.
          Bunny's Form-Fillable Controller Layout PDFs

          Comment


            #6
            TARGET scripts should accept much longer pulse lengths. All my scripts are set default pulse duration of 250ms. You might have to text edit the GUI-generated script to get a usable value.

            Comment

            Working...
            X