Max/spice2x_spice2x.github.io
1
0
Fork 0
mirror of https://github.com/spice2x/spice2x.github.io.git synced 2026-10-09 23:58:22 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated Known issues (markdown)

sp2xdev
2024-12-13 01:06:10 -08:00
parent e40b5bbe70
commit ffa2155d9b
1 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Known-issues.md
+9 -6
@@ -4,19 +4,22 @@
* Spice will always process keyboard / mouse / gamepad / touch input even if the game does not have focus, as it uses Windows raw input API to directly communicate with input devices for lowest latency.
* Windows XP is unfortunately no longer supported - see [here](https://github.com/spice2x/spice2x.github.io/wiki/Compiling-spice2x#compiling-for-winxp) for details.
* Make sure the game contents are not marked as read-only on your filesystem. Having files with read only attribute can lead to game crashes or failures to launch. This commonly happens when a file-sharing program (like torrent clients) is open, or when copying files across filesystems or operating systems (Linux, Mac OS).
* No support will be provided for Linux users running with WINE / proton; you're on your own.
* If your keyboard has trouble with NKRO in spice (i.e., if you press too many buttons, some keys do not respond):
* Try binding keys using the `Naive` button (do it for all keys)
* If you were already using `Naive` button, try `Bind` button instead.
* (`Bind` uses HID APIs and `Naive` uses `GetAsyncKeyState` - one may work better than the other depending on your keyboard)
* If game crashes with `(AcLayers): (unknown): NotifyShims` on the stack - this is an internal Windows component crashing. Unsure what the exact cause is, but try unchecking `Disable fullscreen optimizations` and other compatibility options in `Properties` dialog for `spice.exe` / `spice64.exe`. Seems to be affecting small number of Windows 11 users.
* If you're using input remapper like AutoHotKey, slidershim, UCR, 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.
* No support will be provided for Linux users running with WINE / proton; you're on your own.
## Configurator (spicecfg)
* If `spicecfg.exe` fails to launch or crashes, try running `spice.exe -cfg` or `spice64.exe -cfg` in the command line instead of spicecfg, which launches the configurator but with logging enabled.
* `spicecfg.exe` may fail to launch or be super slow to open while OBS is running. This is due to a bug in OBS that locks the Windows HID APIs. Try turning off OBS temporarily.
## Input
* If your keyboard has trouble with NKRO in spice (i.e., if you press too many buttons, some keys do not respond):
* Try binding keys using the `Naive` button (do it for all keys)
* If you were already using `Naive` button, try `Bind` button instead.
* (`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, UCR, 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.
## Graphics
* Almost all of the supported games are meant to run in exclusive full screen. Running in windowed mode is a hack done on per-game basis. Things may not work as expected in windowed mode. Namely: