I recently upgraded to the newest version of minecraft and with that have upgraded sodium and iris versions, i use the same shaders with the same settings as i did before the update, complementary reimagined being that shader. On 1.21.4 i averaged between 140 to 170 fps at all times with a render distance of 28 chunks. Since updating to 1.21.5 and using all of the same settings and shader my fps struggles to ever go above 110 in the overworld, sometimes reaches as low as 60 to 70 frames which is an insane fps drop for just a little update.

Ive tested several things to see what has been causing it and the vanilla versions seem to run identically but the sodium versions for both 1.21.5 and 1.21.4 have a big performance gap especially with shaders. Which leads me to believe sodiums 1.21.4 version just offers far better performance than the sodium version we currently have with 1.21.5

(also I have a very good pc so its just strange to see the huge performance drop between versions)

It's an issue with 1.21.5 itself, not Sodium.

I'm unsure if it has to do with 1.21.5 itself, it could actually be on sodium for why it's performing worse. Compared to the previous version, if you check the OpenGL version it shows 4.6 on 1.21.4. However, this is not the case for 1.21.5, because it shows OpenGL 3.2 which is considerably older and does not support mesh shaders, leaving everything computationally expensive and dependent on your CPU. Vanilla Minecraft also runs on OpenGL 3.2 to ensure compatibility with older devices, as that is considered the standard for supporting both new and old graphics cards. However, by doing this, graphics cards that work better on OpenGL 4.6 come to a crawl when using OpenGL 3.2.

Because Sodium is a rendering pipeline, whatever they did for 1.21.4 has not been applied correctly to 1.21.5 so that's my theory as to why the performance is much worse. It's quite frankly terrible, I dip into the 50s with a render distance of 5 and my graphics card being the 1060 is able to hit a lot higher, usually consistent 100+ fps with shaders enabled on low (which still looks great) when using the newer OpenGL 4.6 version.

Most definitely a sodium issue.

The OpenGL version shown is completely irrelevant to performance. Mojang changed the OpenGL context initialization code slightly so it shows a different version, but this has no bearing on rendering performance, unlike the other extensive changes they made to buffer streaming and resource management.

Furthermore, Sodium replaces significant portions of Minecraft's rendering code, and it does not need to interact much with the game as a result. This is also largely the reason why we are able to provide updates to newer versions of Minecraft so quickly -- there's just not really any code that needs to be updated, outside of making sure we return state back to what Minecraft expects after we finish our own rendering.

The performance regressions in Minecraft 1.21.5+ are extensively documented and profiling shows the time is being spent in code outside of our mod. These problems are not caused by Sodium.

As I've written elsewhere, we're not super interested in trying to fix issues in Minecraft 1.21.5 since the game's rendering code is changing so quickly, and our work would quickly be made obsolete in a future update.

The reality is that Mojang is (unfortunately) beta testing their rendering code changes on users due to their inability to have multiple branches of the game, and this means a lot of people are simply going to have a significantly worse experience over the next year until issues are worked out.

@jellysquid3 let's say mojang made some rendering code changes that didn't change for a long eough time, would you update sodium to fix it?

30 fps with no shaders in 1.21.8. :(

I'm closing this issue since it isn't actionable in its current state. We always want to improve the mod, but right now we're waiting a little bit for Mojang to settle down with their changes.

I'm closing this issue since it isn't actionable in its current state. We always want to improve the mod, but right now we're waiting a little bit for Mojang to settle down with their changes.

Would it be possible to keep this issue open until Mojang updates settle down and performance improves? I would like to have some tracking point for any updates regarding these performance regressions and this issue seems like a good candidate.

the issue is just closed, not deleted.

Closing issues tends to reduce discoverability quite a bit and makes it more likely people will create duplicate issues.