- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
With such a headline, I’m going to believe they have removed
usleep(10000)from the frame rendering code.Nah, they reduced its
If { else ifsequences.
According to the commit, they enabled loop unrolling? Im not that experienced with reading this stuff, but if I had to guess, I’d say that’d be what did it
Yup, that’s the one line change, enabling loop unrolling.
loop-unrolling.enable()
Honestly, the Talos Principle Vulkan implementation feels so broken/underbaked I’m surprised anyone’s testing new drivers with it
Yes, bad use of API shouldn’t be use as reference, but it also increases Valheim (which does not seems to be the best API us ever):
I can confirm, this also brings Valheim from 45 to 70-80 FPS on my machine (4090M, 7945HX) at 1080p Ultra Settings.
Commit here.
They simply added this line
op.max_unroll_iterations = 32;, related to NIR shader compilation. Passed to NIR here.(I stop here, lost track and interest in further investigation)
Phoronix is going to be flooded with almost identical headlines like this if they make an article every time the (brand-new) NVK Mesa driver gets a commit that improves performance somewhere
now let’s see whether the next patch bumps it to 27 or 36 fps!
