From 4327bc1e9fb9b57457ddef2b63d6d7f6da2e37af Mon Sep 17 00:00:00 2001 From: sp2xdev <127630192+sp2xdev@users.noreply.github.com> Date: Fri, 14 Mar 2025 19:28:45 -0700 Subject: [PATCH] Updated Known issues (markdown) --- Known-issues.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/Known-issues.md b/Known-issues.md index c38baa0..915aef7 100644 --- a/Known-issues.md +++ b/Known-issues.md @@ -6,7 +6,8 @@ > [!CAUTION] > If you have Rivatuner (RTSS) or MSI Afterburner, **fully** shut both of them down before running spice, otherwise your game may crash or hang, sometimes without any trace in the log. -# General +# Common issues across all games +## General * When you open a log.txt, you'll want to reopen it with `SHIFT-JIS` encoding to properly show Japanese text. How you do this depend on your text editor. * Some anti-virus software may (incorrectly) flag the binaries as malware. If you have concerns, you are free to inspect the included source files and compile on your own. * Windows XP is unfortunately no longer supported - see [here](https://github.com/spice2x/spice2x.github.io/wiki/Compiling-spice2x#compiling-for-winxp) for details. @@ -15,12 +16,12 @@ * 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. * No support will be provided for Linux users running with WINE / proton; you're on your own. That being said, we are not against other developers working on getting things to work better in Linux. If there are any small tweaks to the code base that can be made to make it easier to run on Linux, please feel free to submit a patch. -# Configurator (spicecfg) +## 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. It's not *exactly* the same environment as spicecfg, but it's close enough. * `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. * `spicecfg.exe` may fail to launch when run from a network share (UNC path). -# Input +## Input * 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. * 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) @@ -31,7 +32,7 @@ * 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. -# Graphics +## 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: * Some multi-monitor games will fail to display more than one window.