This build isn't code-signed yet, so Windows SmartScreen will probably show "Windows protected your PC" the
first time you run it. Click More info, then Run anyway. You see it once per install: updates are downloaded
by SCSKiller itself and never trigger it.Why: code signing through the SignPath Foundation is in progress, for stable releases (alpha and beta builds stay
unsigned). To check that the download arrived whole, compare its SHA-256 with the one at the end of these notes
(PowerShell:Get-FileHash <file>); these notes aren't signed, so that doesn't prove who built it. The source: https://github.com/BlueHeisenberg/SCSKiller/tree/v1.1.0.Smart App Control (Windows 11) blocks unsigned apps outright, with no Run anyway. If it's on, wait for a signed release.
Added
- Shared packs for the FidelityFX and XeSS upscalers: a game that ships an upscaler DLL version someone has recorded on
the same GPU vendor gets those shaders compiled, free and without an account or a recording of its own. Packs are
uploaded only with "Share anonymous shader hashes" on.
Changed
- The installer is
SCSKiller-Setup.exe, without the version, so its download link always gets the latest release. - Every game's compile plan is rebuilt once after this update, while the PC is idle, and games compiled before ask for
one more compile; it mostly finds the shaders already in the driver cache. - Unreal games: plans also use the pipeline list the game ships, so shader pairs its files alone can't match are
compiled too. Unreal Engine 5.4 is on the list of tested engine versions.
Fixed
- The recorder no longer crashes a game when an overlay hooks its presents after the recorder and the game makes another swap chain, when the game unloads d3d12.dll after creating a device, when NVAPI is called while the recorder hooks it, or when
next=in scskiller.ini names the recorder itself. - A damaged scskiller.db no longer makes the game allocate gigabytes when it starts; a full disk, or a second process
recording in the same folder, no longer leaves a recording that can't be read past that point. - The recorder no longer goes through the C runtime when it ends a launch's timings at exit, which could stop a game's
exit if another thread had died holding its lock. - Stopping a compile after a GPU driver fault or hang no longer makes the next compile skip the pipelines that were
still unfinished. - A compile whose process hangs at exit is always ended after the exit limit, also when its last pipelines finished
right after it started. - DirectX 11 hull shaders that take all 32 input registers compile instead of counting as failed.
- "Last time you played" no longer counts the shaders a game compiles while it starts up as compiles during play.
- Turning the recorder off removes all its files from the game folder, the last session's frame times included (an
scskiller.iniyou edited stays), and files an earlier version left there go at the next scan. - Frame times: a slow load from the game's own pipeline library is no longer a shader stutter, a shader freeze of 5 s
or more counts in the 1% low, and a launch never takes another launch's frames. - Quit waits for a compile you just removed from the queue to save its cache, like any other running compile.
- Choosing another update channel no longer installs an update downloaded from the one before.
- The driver-update notification's buttons work after SCSKiller was closed.
- "Compile queue" also starts games queued to compile when the PC is idle.
- On AMD, the library's cache bar compares the DirectX 12 cache with its limit, not both caches.
scskiller compilerefuses an option it doesn't know or one missing its value, and Ctrl+C before a compile
starts is no success.- Anti-cheat files and folders are found anywhere in a game's install, hidden or system ones too, and an install with a
folder SCSKiller can't list counts as anti-cheat, so the recorder is never offered for those games. An update that
adds anti-cheat while the recorder is being installed takes it out again. - Clear cache deletes only the Windows shader cache's own files in a game's D3DSCache folder, and on NVIDIA refuses
while another installed game has the same exe name (the driver gives both one cache). - A recording imported by the app while the command line compacts it, or the other way round, keeps every record.
- SCSKiller never writes into a game's folder while the game runs, also when a launcher started it under another exe
name, and a game whose launcher id isn't a valid folder name gets a data folder of its own. - A malformed root signature in a recording or a community download no longer breaks a game's whole plan: only the
pipelines that use it are left out. - An update download stops at the size the signed feed gives, and gives up when no data arrives for two minutes (the
next check tries again).
SHA-256:
31fb6fcfb91e23f9353e336014e3d7aaeafdaffc175dd61bfa533b30f15779ff SCSKiller-1.1.0-Portable.zip
3057982e62f73a865e1fddc565e2c561af4b4f946753cec0b7b2fe99c74d7c7d SCSKiller-Setup.exe