From 19613517fed0ead96afb793c63c515b5884fb684 Mon Sep 17 00:00:00 2001
From: sp2xdev <127630192+sp2xdev@users.noreply.github.com>
Date: Sun, 20 Jul 2025 03:06:31 -0700
Subject: [PATCH] Updated Known issues (markdown)

---
 Known-issues.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Known-issues.md b/Known-issues.md
index 664c918..c2c2d92 100644
--- a/Known-issues.md
+++ b/Known-issues.md
@@ -32,7 +32,7 @@
     * If you were already using `Naive` button, try `Bind` button instead.
     * If neither helps, your keyboard sucks.
     * (`Bind` uses HID APIs and `Naive` uses `GetAsyncKeyState` - one may work better than the other depending on your keyboard)
- * If you're using input remapper like AutoHotKey, slidershim, joytokey, i2dx, etc - make sure you're running them as **admin** in order to be bound in spice. Also, try both the `Bind` and `Naive` buttons when binding if one or the other doesn't register your remapped input.
+ * If you're using input remapper like AutoHotKey, slidershim, joytokey, i2dx, Elgato Stream Deck, etc - make sure you're running them as **admin** in order to be bound in spice. Also, try both the `Bind` and `Naive` buttons when binding if one or the other doesn't register your remapped input.
     * Some input remappers will not work, depending on what method they use (which Windows API they use). In order for injected input to be recognized by spice, it must flow through Raw Input API. Some applications are unable to do that.
  * Windows 11: if your controller is not detected for some reason, reboot your PC with your controller plugged in. Seems to be some bug with raw input APIs in newer versions of Windows 11.