Download Latest Version WitchTime-v0.12.3-windows-x86_64.zip (91.7 MB)
Home / v0.11.0
Name Modified Size InfoDownloads / Week
Parent folder
WitchTime-v0.11.0-windows-x86_64.zip 2026-11-16 91.7 MB
WitchTime-v0.11.0-windows-x86_64.zip.sha256 2026-11-16 103 Bytes
WitchTime-v0.11.0-linux-x86_64.tar.gz 2026-11-16 156.4 MB
WitchTime-v0.11.0-linux-x86_64.tar.gz.sha256 2026-11-16 104 Bytes
README.md 2026-11-16 15.6 kB
Witch Time v0.11.0 source code.tar.gz 2026-11-16 3.0 MB
Witch Time v0.11.0 source code.zip 2026-11-16 3.2 MB
Totals: 7 Items   254.2 MB 0

Witch Time v0.11.0

DLSS / DLAA and FSR 4 can take FSR 3.1's place, and there is a first frame generation, all with DLL files you copy in yourself (#190, [#119]). The Linux build asks PulseAudio for sound first, which fixes a silent game on SteamOS (#235). The download holds only what your PC reads (#211).

Read this before you turn the new graphics options on: DLSS upscaling ran on two testers' PCs (RTX 3080 and RTX 5070). FSR 4 and both frame generators have never run on any GPU. They are off by default, and where one can't start the game goes on as before and the log says why.

Coming from v0.10.2, nothing compiles again and there's no PREPARING SHADERS screen. The game adds three keys to your config/graphics.ini (frame_generation, frame_generator, frame_generation_hud); the file as it was goes to graphics.ini.bak. At its first start after the update, the launcher removes developer files older releases shipped (docs, tests, tools, the launcher's source and a few more). Your config/, mods/, build/ and converted textures stay as they are.

If Update stops with "Cannot install ...: The system cannot find the path specified" (#224), your launcher is v0.10.1 or older and its folder's path is long. Download the Windows zip below, unpack it to a short path such as C:\Games\WitchTime, copy your config folder over from the old one, then pick your dump again and rebuild.

Coming from an older version, you also get these one-time steps:

  • From v0.10.0: the cloud's tessellation shaders are translated once more the first time the game draws them, without a screen for it.
  • From v0.9.3 or older: press REBUILD once. All of the game's 409 code files compile again, as on a first install (see the v0.10.0 notes). Don't copy a build/ folder from one PC to another.
  • From v0.9.2: if your Internal resolution isn't 1.0, or your aspect ratio isn't 16:9, PREPARING SHADERS shows once more.
  • From v0.9.1: the game also adds the hdr_peak key to your config/graphics.ini. Anisotropic filtering and texture detail are fixed at 16x and -1.
  • From v0.9.0: the game's compute shaders, a small part of all its shaders, are translated once more as the game first uses them, without a screen for it.
  • From v0.8.0: FSR 3.1 compiles most of its passes once more the first time it runs.
  • From v0.7.0: the game adds the upscaler key to your config/graphics.ini, set to off.
  • From v0.6.1 or older: PREPARING SHADERS shows once more, on every GPU. See also the v0.6.0 and v0.5.0 notes.

Linux (x86_64) and Windows 10/11 (64-bit). macOS is experimental and built from a checkout (see the README). Android is planned.

Download and run

  • Linux: download WitchTime-v0.11.0-linux-x86_64.tar.gz, unpack it and run ./witch-time.
  • Windows: download WitchTime-v0.11.0-windows-x86_64.zip, unzip it to a folder you can write to (a short path with no special characters works best) and run witch-time.exe.

Each archive has a .sha256 file to check it against. Windows Defender might flag Witch Time as a Trojan (#64), because the programs aren't code-signed. Download it only from this page.

Already on v0.4.0 or later? The launcher's title menu offers Update and keeps your config/ files. On v0.8.0 or older, start Witch Time once without --play to see the offer. If Update fails on Windows, see the note at the top.

What you need is the same as before: a Vulkan-capable GPU and driver, plus OpenGL and FreeType on Linux, or the Media Feature Pack on Windows "N" editions. The picture book also needs program 1 from the game's update 1.2.0 (see the README).

The new graphics options and their DLL files

No file of NVIDIA's or AMD's is in this release, so you copy them next to witch-time.exe yourself and start the game again. All of this is Windows only. The rows are in the game's PC settings panel (F1, or Start + Select).

Option Row and values Files to copy Needs
DLSS / DLAA FSR 3.1 / DLSS / FSR 4: DLAA, DLSS Quality to Ultra Performance nvngx_dlss.dll, from a game you own that has DLSS NVIDIA RTX
FSR 4 same row: FSR 4 Native AA, FSR 4 Quality to Ultra Performance amd_fidelityfx_loader_vk.dll and amd_fidelityfx_upscaler_vk.dll, from AMD's FSR SDK 2.4.0 or newer Radeon RX 6000 or newer, Adrenalin 26.10.1 or newer
Frame generation, FSR Frame generation On, type FSR amd_fidelityfx_loader_vk.dll and amd_fidelityfx_framegeneration_vk.dll, same source an upscaler mode other than Off
Frame generation, DLSS Frame generation On, type DLSS nvngx_dlss.dll and nvngx_dlssg.dll, from a game you own that has DLSS frame generation RTX 40 or newer, an upscaler mode other than Off

The driver's amdxcffx64.dll is for DirectX 12 and doesn't work here.

Changes

  • DLSS and DLAA in FSR 3.1's place (#190, [#231]). With your own nvngx_dlss.dll, the upscaler row gets DLAA (at the Internal resolution) and DLSS Quality to Ultra Performance, at the same scales as the FSR 3.1 modes. Without the file, or on a GPU that isn't an NVIDIA RTX, the FSR 3.1 mode of the same rank runs. Two testers ran it on an RTX 3080 and an RTX 5070.
  • FSR 4 in FSR 3.1's place (#119, [#231]). The same with AMD's two files: FSR 4 Native AA and FSR 4 Quality to Ultra Performance. AMD's own list for your GPU and driver decides whether FSR 4 runs; if it doesn't, FSR 3.1 runs and the log says why. Never run on a GPU.
  • Frame generation (#119, [#233]). With Frame generation On, a generated picture is shown between every two frames of the game, so the screen gets twice the game's frame rate. The game's own speed and timing don't change. Off by default. It needs:
  • an upscaler mode other than Off (that is where the motion information comes from);
  • a display that shows twice the game's frame rate (120 Hz for 60 fps), or Vertical sync Off. Otherwise nothing is generated, so the game isn't slowed down;
  • a 3D scene: menus and movies are shown as before.

It adds about half a frame of delay. Frame generation: HUD (On by default) gives the generator each frame without the HUD too, so health bars and prompts stay sharp. Neither generator has run on a GPU, and the DLSS one is a guess: NVIDIA doesn't publish how it is called.

  • Linux: PulseAudio is asked for sound first (#235, [#236]). A SteamOS player on a ROG Ally had no sound until they set SDL_AUDIO_DRIVER=pulseaudio. The game and the launcher now ask for PulseAudio first, and go back to SDL's own order where no PulseAudio server answers. SDL_AUDIO_DRIVER in the environment still decides. Windows and macOS are untouched.
  • The download holds only what a player's PC reads (#211, [#232], [#234]). docs, tests, tools, the launcher's source and the repository's own files are no longer in the archives; GitHub's "Source code" archives still have everything. An update unpacks over your folder and removes nothing, so the launcher removes those files itself when it starts. It never does this in a git checkout.
  • Check dump names the archives it can't find (#226, [#230]). A romfs folder with more files than expected, such as another game's RomFS or unpacked archives, was told only "files are missing". The message now names the .pkz archives that aren't directly inside romfs/.

Known issues

New or changed in this release:

  • The launcher and the game's own Options tab don't list the DLSS and FSR 4 values (#190). Set them in the PC settings panel (F1, or Start + Select) or in config/graphics.ini; the launcher shows "Custom" for them. The Options tab doesn't have the three frame generation rows either.
  • Frame generation with HDR on gets the 8-bit picture (#119), and the frame-pacing numbers count the generated picture as a frame.
  • With DLSS, each change of the game's dynamic resolution can cause a short hitch (#190).
  • A fault inside NVIDIA's frame generation closes the game (#119): it can't be caught. Set Frame generation to Off in the launcher, under Settings, Graphics.
  • Why the sound was silent on SteamOS isn't known (#235). That PipeWire was the silent driver is our reading of the report. If the game is silent on Linux with this version, tell us there.
  • Update from v0.10.1 or older still fails in a long folder on Windows (#224). See the note at the top.

Still open from earlier releases:

  • The fence change wasn't run in a fight, a cutscene or other chapters (#218). If the picture breaks or the game stops where v0.10.1 didn't, start it with WT_VK_SYNCJOB=1 and tell us.
  • The cloud pass costs more at an Internal resolution above 1.0 (#207). If the clouds of erasure slow the game down, set WT_VK_CLOUD_SCALE=1.
  • Other effects may have the fault the cloud's patches had. Only tessellation shaders were changed; vertex shaders with the same lookup are as they were.
  • A spawned enemy from the debug commands belongs to no verse (#217), so a fight's end doesn't wait for it.
  • The volume fix was never heard (#203). If the sound engine caps the level, slider positions 10 to 20 may sound the same.
  • The ride change wasn't measured in a ride (#156). At a frame_rate of 90 a ride runs at 45 fps: rides run at half the frame rate.
  • A build copied to a PC with an older processor stops with an illegal instruction (#206). Press REBUILD there.
  • "Check dump" can fail with "clang: linker command failed" (#204). The launcher shows only the last line. We've asked the reporter for the full output.
  • The reporter's Jeanne mod in [#181] is still unexplained. If a mod doesn't load, attach build/run/witch-time-game.log there.
  • Nobody has confirmed the Linux HDR Auto fix (#180), and nobody has looked at HDR on an HDR monitor on Windows with a log (#195).
  • The PC Settings tab's texts in the 12 languages other than English aren't proofread, and some are shortened.
  • A silent game on Windows isn't fixed (#182). A test build is with the reporter.
  • Intel UHD 620 still stops at the first frame after the loading clock (#55).
  • The v0.9.1 sound fix isn't confirmed by its reporter (#157).
  • On a graphics card with 4 GB, later chapters need more video memory than the card has (#153). The game should slow down, not freeze. Lowering Internal resolution leaves more room.
  • After you replace a damaged dump file, the textures left out stay left out. Remove the converted textures in Settings, Graphics, then convert them again.
  • Deleting targets/program1 by hand (the picture book) still isn't noticed by REBUILD.
  • FSR 3.1 is experimental (#118): faint trails on effects, and no sharpening yet. Set it to Off before you open the picture book.
  • Frame rate above 60 is experimental (#134): some timers still count frames, so a few fades may run faster.
  • Frame rate drops in some areas (#132, [#133], [#50], [#89], [#93]) and in the cutscene after the Prologue's Kraken fight on an RX 6700 XT on Windows (#144).
  • Visual marks: dashed lines on model edges on an RX 570 (#161), squares on shadows and water on an RX 560 at 720p (#147), small dark marks on character outlines and in Bayonetta's hair (#93), and marks on Bayonetta's face with a face mod (#215).
  • Windows Smart App Control can block the game at the text step (#177), because the programs aren't signed.
  • Cutscenes can still stop the first time on a hard disk (#136). Settings, Graphics, Converted textures, Turn off helps.
  • If the picture book's book step fails, Play is blocked for Bayonetta 3 too. Take program1/ out of your dump and press REBUILD.
  • On Windows, a copy of the game can keep running after you've stopped playing (#127). End every witch-time-game.exe in Task Manager.
  • A desktop shortcut doesn't start under GNOME when the game folder's name has a % in it.
  • The spider ride falls behind below about 41 fps, and with rebound buttons the ride's four-circle prompt shows the right button in the old button's place.
  • Stalls: a shader kind that wasn't prepared still compiles at its first draw, and the picture book's prologue stutters on its first run.

Not tested yet

Please report anything you see with these:

  • FSR 4 (#119). AMD ships none for Linux, where this was written. Open: whether AMD's file takes the game's picture format, and how long the first frame with it takes.
  • Both frame generators (#119). Only our own part ran, on Linux on one RX 9070 XT: the two presents a frame, with the real frame shown twice. The spacing of the two presents wasn't measured. If you try it, [#119] lists what to send.
  • DLSS in this build (#190). The testers ran the branch before it was merged with FSR 4.
  • The game with the PulseAudio change (#235). A small test program ran the same steps; the game itself wasn't started with it, and cutscene sound timing on PulseAudio is unchecked.
  • The launcher's clean-up on Windows (#211). It ran on Linux against an unpacked v0.10.2.
  • The new Check dump message in the Windows launcher (#226).
  • The update from v0.10.2 itself. Nobody has run it through the launcher yet.
  • Still untested from earlier releases: the updater fix on Windows (#224), the fence change on Windows, on NVIDIA and Intel GPUs, in a fight and in cutscenes (#218), all of v0.10.1 on Windows, the cloud fixes on NVIDIA, on AMD's own driver, on macOS and with FSR (#207), real interpolated 60 fps movies (#213), the debug commands on Windows (#217), the processor levels on a slower processor or one without AVX2, the volume sliders by ear, the ride without an artificial load, the macOS port played by hand, a fresh unpacked release without the settings files, the clickable hints with a controller's glyphs, a real mod past the title screen, the fog wall and mist fix on NVIDIA and Intel, HDR on a real HDR monitor and in cutscenes or with FSR, the PC Settings tab from the pause menu and in other languages, v0.9.1's compute shader change on GPUs other than an RX 9070 XT and an Arc A770, its video memory budget on a real 4 GB card, the Desktop shortcut on real Windows, KDE and the Steam Deck, the launcher sounds by ear, the start language on Windows, FSR 3.1 on Intel and the Steam Deck, the 90 and 120 fps fixes played by hand, the picture book on Windows, and a real ultrawide monitor (#77).

If something fails, include build/run/witch-time-game.log, the files in build/logs/, your OS and your GPU. Copy the log before you start the game again, because each start overwrites it.

This release contains no game code or assets, and no file of NVIDIA's or AMD's. Everything derived from the game is made on your PC from your own dump. Please never share it.

What's Changed

  • Dump check: the archives missing from romfs/ are named (#230)
  • DLSS / DLAA and FSR 4 with the player's own DLLs in FSR 3.1's place (#231)
  • Release: the packaged folder holds only what a player's PC reads (#232)
  • Frame generation with the player's own DLLs: AMD's and DLSS (#233)
  • Launcher: an updated install loses the developer files older releases shipped (#234)
  • Audio on Linux: PulseAudio is asked first (#236)

Full Changelog: https://github.com/Zexyen/Witch-Time/compare/v0.10.2...v0.11.0

Source: README.md, updated 2026-11-16