From f27996386febd4d59dea692672e44599e06daa60 Mon Sep 17 00:00:00 2001 From: sp2xdev <127630192+sp2xdev@users.noreply.github.com> Date: Wed, 19 Mar 2025 17:35:25 -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 110c0a3..cd56439 100644 --- a/Known-issues.md +++ b/Known-issues.md @@ -15,7 +15,7 @@ * 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). * 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. - * If spice fails to launch on older OSes (Windows 7 and Windows 8), please ensure [UCRT is installed](https://github.com/mingw-w64/mingw-w64/blob/master/mingw-w64-doc/howto-build/ucrt-vs-msvcrt.txt) by downloading Visual Studio 2019 16.7 redistributable package. + * If spice fails to launch on older OSes with `api-ms-win-crt-convert-l1-1-0.dll is missing` message (Windows 7 and Windows 8), please ensure [UCRT is installed](https://github.com/mingw-w64/mingw-w64/blob/master/mingw-w64-doc/howto-build/ucrt-vs-msvcrt.txt) by downloading Visual Studio 2019 16.7 redistributable package. ## 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.