vk pipeline bin files keep increasing in folder #2579

Open

opened 2026-11-12 00:04:59 +00:00 by kvothe3323 · 2 comments

kvothe3323 commented

2026-11-12 00:04:59 +00:00

(Migrated from github.com)

Hookshot version

v2.1.0

What kind of problem

Something else

What happened

as the title says, every time i play the game, the pipeline bin file just increasing with num..rightnow its 22..and it keeps adding more bin files in the folder

Where in the game

game folder

How often

Every time

Graphics card and driver version

rtx 4090

CPU, RAM and operating system

ryzen 5800x3d

Changes from the defaults

No response

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

Screenshots or video

Before you send it

I'm on the newest release, or the problem is still there on it.
I searched the open issues for this problem.
I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.

### Hookshot version v2.1.0 ### What kind of problem Something else ### What happened as the title says, every time i play the game, the pipeline bin file just increasing with num..rightnow its 22..and it keeps adding more bin files in the folder ### Where in the game game folder ### How often Every time ### Graphics card and driver version rtx 4090 ### CPU, RAM and operating system ryzen 5800x3d ### Changes from the defaults _No response_ ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log.txt](https://github.com/user-attachments/files/34720706/hookshot_log.txt) ### Screenshots or video <img width="639" height="638" alt="image" src="https://github.com/user-attachments/assets/a2a599cd-ef83-4651-8d4f-e75747ba7c18" /> ### Before you send it - [x] I'm on the newest release, or the problem is still there on it. - [x] I searched the open issues for this problem. - [x] I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.

mooki000 commented

2026-11-12 02:51:24 +00:00

(Migrated from github.com)

I'm looking at this tonight on Linux with the same card (RTX 4090, NVIDIA 615.78.08): why a new numbered pipeline file appears at each start, whether the older ones are ever read again, and whether they can be pruned safely. By the project's scoring: S3, one report with a log (confidence 0.4); reach depends on the cause, which I'll state once I know it. This is the naming and pruning of the files, not the cache's load and save copies (#2206), which someone else has claimed. I'll post what I find here, fix or not.

👍 1

github-sync commented

2026-11-12 13:39:30 +00:00

Owner

@mooki000 commented on GitHub · 2026-11-12 12:45 UTC · original

These numbered files save additions to the Vulkan pipeline cache without rewriting the large base file each time. Your log merges 15 old files at startup, then saves files 16–22 during that same session.

The cleanup is already in v2.1.0: at the next startup, 16 or more successfully merged files trigger consolidation into mkw_vk_pipelines.bin, followed by removal of those numbered files if the base write succeeds. Sixteen is a startup trigger, not a limit during play, and a file's number is not the count of files still present.

The controlled Linux check also consolidated and removed its 16 seeded cache files; it does not establish what your next Windows start does. Please try one normal restart: if the same old files remain, attach that new hookshot_log.txt, not the .bin files. There's no need to delete them just because the number reached 22.

> [@mooki000](https://github.com/mooki000) commented on GitHub · 2026-11-12 12:45 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2579#issuecomment-6823982797) These numbered files save additions to the Vulkan pipeline cache without rewriting the large base file each time. Your log merges 15 old files at startup, then saves files 16–22 during that same session. The cleanup is already in v2.1.0: at the next startup, **16 or more successfully merged files** trigger consolidation into `mkw_vk_pipelines.bin`, followed by removal of those numbered files if the base write succeeds. Sixteen is a startup trigger, not a limit during play, and a file's number is not the count of files still present. The controlled Linux check also consolidated and removed its 16 seeded cache files; it does not establish what your next Windows start does. Please try one normal restart: if the same old files remain, attach that new `hookshot_log.txt`, not the `.bin` files. There's no need to delete them just because the number reached 22.

Commenting is not possible because the repository is archived.