Navigation

    ViGEm Forums

    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular
    • Twitter
    • GitHub
    • Discord

    C# app to drive HidCerberus / HidGuardian?

    HidGuardian
    1
    12
    582
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Flarum Bot
      Flarum Bot last edited by

      Originally posted by evilC


      Orly?
      So app whitelisting / blacklisting is working now?
      Are the reg keys documented somewhere?

      1 Reply Last reply Reply Quote 0
      • Flarum Bot
        Flarum Bot last edited by

        Originally posted by nefarius


        There is now 😆

        1 Reply Last reply Reply Quote 0
        • Flarum Bot
          Flarum Bot last edited by

          Originally posted by evilC


          Yeah I know about those keys, but they are for global whitelisting / blacklisting.
          I thought you meant that control over which apps could see which devices was working...

          1 Reply Last reply Reply Quote 0
          • Flarum Bot
            Flarum Bot last edited by

            Originally posted by JoshWobbles


            @evilC#62 That's the general idea, PIDs in the whitelist key are able to access the devices, others are not.

            1 Reply Last reply Reply Quote 0
            • Flarum Bot
              Flarum Bot last edited by

              Originally posted by evilC


              What whitelist key? There is no mention of one.
              All the linked documentation tells you are the AffectedDevices and ExemptedDevices keys, which only appear to let you globally whitelist / blacklist devices, which serves no practical purpose.
              I see no mention of a reg key which will whitelist / blacklist on a per-PID basis.

              1 Reply Last reply Reply Quote 0
              • Flarum Bot
                Flarum Bot last edited by

                Originally posted by evilC


                Oh, and @JoshWobbles - I see in another thread you have been tinkering around yourself in this area - it seems to me that we probably only need one application to handle HG/HC interaction - I am not really sure that I see any benefit in building our own implementation into our various feeder apps.
                So the basic workflow that I envisage would be a Gui app that you can run, click "Add Rule", and it pops up a list of all devices, allowing you to select one and configure various options (whitelist / blacklist apps etc) and also handle the "replug device to take effect" dialogs etc. It may need to be running all the time, as if white/blacklisting is based upon PID, I suppose you would need something that detects when your feeder app is launched, gets it's PID and hands it to HC.
                Do any other consumers of ViGEm feel the same? Is anyone else interested in pitching in on a community-driven effort do develop such an app?
                Would be happy to pitch in on coding / QA / design ideas etc.

                1 Reply Last reply Reply Quote 0
                • Flarum Bot
                  Flarum Bot last edited by

                  Originally posted by nefarius


                  Currently working in a more user (and developer) friendly API, UI and documentation:

                  1 Reply Last reply Reply Quote 0
                  • Flarum Bot
                    Flarum Bot last edited by

                    Originally posted by evilC


                    @nefarius#73
                    Awesome news!
                    What would happen if you whitelisted a specific mouse to only be able to send input to my feeder app?

                    I take it I would just read it via RawInput as normal? Would windows move the mouse pointer in response to this mouse at all? Ideally we would love a solution where we can read input from a mouse without it having any effect on the OS - there are a bunch of input devices for disabled people that report as a mouse, and we want to be able to totally transform the input from them, without having to hook all mice on the system.

                    1 Reply Last reply Reply Quote 0
                    • Flarum Bot
                      Flarum Bot last edited by

                      Originally posted by nefarius


                      You white-list the **process** which wants to access it. Mice are tricky; AFAIK the OS picks up their input in stages the guardian can't block - which is expected behavior since I designed it for user-mode processes to get blocked access to the device. And yes, you should be able to use RawInput right after you called HidGuardianOpen.

                      1 Reply Last reply Reply Quote 0
                      • Flarum Bot
                        Flarum Bot last edited by

                        Originally posted by evilC


                        Bummer, I was hoping that since HG appears to be able to stop joy.cpl from being able to see a stick, that a similar thing might be possible with mice.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post