search

mKenfenheuer / steam-deck-windows-usermode-driver

A windows usermode controller driver for the steam deck internal controller.
GNU General Public License v2.0
413 stars 23 forks source link

[BUG] UI not appearing, driver possibly not starting #92

Closed ndarilek closed 1 year ago

ndarilek commented 1 year ago

Describe the bug I've gone through all the installation steps, but launching the desktop shortcut doesn't appear to launch a GUI of any kind. I'm blind, so it's possible that I'm missing something. But I've been all over my taskbar and don't find an icon/button to make the driver UI appear.

To Reproduce Steps to reproduce the behavior:

  1. Download and install the Tetherscript Virtual HID Driver.
  2. Download and install the ViGEm Bus driver.
  3. Download and install Microsoft Visual C++ Redistributable Package.
  4. Download and install v0.33 of SWICD_Setup.exe. I didn't find an installation zip containing a .msi as per the installation instructions--did I download the wrong thing here?
  5. Launch the SWICD Driver desktop shortcut.
  6. For me, there is no indication it is running other than a SWICD process in my task manager. Killing/restarting the process or my entire system makes no difference in whether anything appears.

Expected behavior Not sure, never having run this. But it sounds like I should find a configuration UI somewhere in my taskbar?

Debug information Driver version: v0.3.3

Since I can't find the UI, I can't get a package. Running from the terminal also produces no output.

Additional context I'm assuming this UI should be reachable via the keyboard in some way? I.e. pressing windows-t should put me in an area where I can arrow/tab to an icon to open it?

Sorry I can't be more helpful. If there's any way to get output from the terminal or logs of some sort, I'm happy to do that.

ndarilek commented 1 year ago

Is it possible there's no accessible text/button for whatever needs to be clicked to launch the UI?

As a workaround, I wonder if launching the shortcut when swicd is already running might cause the UI to appear? So first launch starts the background process, and the second launch brings the UI into the foreground?

Not quite sure what's going on here in order to make specific accessibility suggestions, but I don't typically have these issues accessing tray icons.

ndarilek commented 1 year ago

Actually, never mind, finally found it. I had to arrow up or down from a specific area in the taskbar, possibly due to the screen size being small.

Sorry for the noise.