45-55% FPS Reduction using 1.21.5 compared to 1.21.4
I originally opened this as a bug report on Github, but I'd figure I would also put it here just incase: https://github.com/IrisShaders/Iris/issues/2732
The TDLR though is, fps seems to be around 45-65% of where it used to be in 1.21.4 (performance varries from different specs it seems). This only occurs when a shader is enabled at all, even disabling it (with the hotkey in my case) causes my fps to be normal like how they are in 1.21.4, 3 other people in this thread is having the same issue, and it seems that (if they are to be believed), there are another 8 people having the same issue too that are just casual players.
The difference this time (and I will update this in the bug report too later) is that the fabric1.8.12snapshot.jar does not solve this issue, I'm still getting the same FPS loss. This marks the affected versions now to 1.8.10-1.8.12snapshot for 1.21.5.
I'd like to know if anyone here is having similar issues (it doesn't look like to me this thread is a duplicate since the other threads regarding fps issues is not what I'm talking about in this case). I think it varries spec to spec too which is what makes this more difficult, and I'm using an Nvidia 1060 3GB GPU which complicates things since that snapshot.jar mentions AMD performance fixes.
GitHub
45-55% FPS Reduction using 1.21.5 compared to 1.21.4 · Issue #2732...
What happened? Unsure if it could be related to Sodium as well, but performance with shaders in 1.21.5 is halved (at least with my specs) compared to 1.21.4 despite higher fps average without shade...
46 Replies
This is an issue with vanilla 1.21.5
How much so?
Because Vanilla 1.21.4 to 1.21.5 has no performance difference
Vanilla isn't really affected so you'd have to explain where it would be affected.
there have been lots of people reporting a performance regression, it seems to be some prep for vibrant visuals
maybe, i can see adding features that it would need now (to some extent) but the problem is they're likely using an internal build for that. breaking vanilla rendering for a minor patch is pretty questionable to say the least and vanilla rendering is not affected negatively from what i can tell, i can test vanilla just to make sure.
i got to get rid of fabric loader though
wtf? i thought 1.21.5 was an outlier or result of some fabric optimization update or sodium update.
i literally had to double check to ensure i wasn't running fabric loader on 1.21.5
but then that begs to question, i should not be going from 55-70 fps on 1.21.4 to 23-25 on 1.21.5, indicating something is probably wrong
not saying im expecting more fps either, i should be hovering around the same
fabric isn’t a mod fyi
it’s literally just a transparent loader and can’t touch the game
There have been many reports of Vanilla 1.21.5 graphical issues
they’re going all in with the rewrites
how much of the rendering engine has been rewritten would you say?
a large amount
it does seem like a significant amount atleast
i see
and they’re only starting
well that definitely explains it
1.21.6 already has a lot more
but this is defintiely for the better
ill try and bear with it
ImmediatelyFast will help with some of the loss
because there seems to be no point in fixing this for now if its going to be changed a lot again in the future
let me check if that mod was enabled rq
nah im hovering the same amount
well thats just how it is i guess
well, that's just mojang
not really iris problem
We should be happy that Minecraft is finally stepping in the right direction
(Or at least it seems)
According to the recently released note by mojang they are replacing some rendering pipeline and cause the performance lost
I have the same issue too
Feel free to share your findings on the open issues on mojang’s bug tracker
If anything. on 1.21.5 i am getting higher FPS. its kinda odd
^ its because vanilla rendering code got rewritten
explains both 3x increase performance in vanilla rendering and 1/2 performance with shaders on
i would like to update this topic, it appears that fps is very good in the nether
why exactly? im not sure, but its worth noting
nether is smaller than overworld
same with end dimension
ya but the thing is
i get 30 fps at render distance 2 in the overworld
so its not that
hey i have a question, i've been seeing some people say this issue is fixed (they're usually running newer gpu's than that I have) but when i check it on my end its not. have you implemented a fix for this on RTX 20+ series gpu drivers or am i just hearing wrong information?
This issue is still present with 1.21.7/8 on Iris 1.9.1. I can't speak for RTX 20+ series drivers but its definitely present on GTX 10 series and older drivers.
You're def not alone and it's an issue I've been following closely since it started some months back. I'm using an RTX 4070 and an Intel Core i7 13700k with 8GB out of 32GB of DDR5 RAM allocated to Minecraft and the issue started with 1.21.5 and is still present in all subsequent versions, including 1.21.8.
From what I understand, and please correct me if I'm wrong, it's something Mojang has to fix on their end since they made some pretty major changes to some graphics related stuff in prep for Vibrant Visuals on Java.
With the same settings and mods (including Iris, Sodium, Lithium, ImmediatelyFast) loaded through the Fabric launcher, I'm getting around anywhere between 89fps - 90fps on 1.21.5 and later versions, including 1.21.7/8. On 1.21.4 it would average between 144fps to 200fps.
If you check on the Mojira big tracker site, there's an issue that has over 270 votes regarding the buffer index or something along those lines and details thhis exact issue. One of the comments is from one of the devs and they mention that the issue is on their priority list, just needs a big refactor. I'm far from someone who understands this stuff, so again, please let me know if I'm missing anything.
What frustrates me and confuses me is that they haven't been able to fix the issue yet, knowing it affects both MacOS and Windows, regardless of what hardware you're using.
I should also mention -- this reduction only appears to happen to me when I'm using shaders, and it ranges from BSL to Complementary and a few others. Less intensive shaders aren't impacted quite as heavily, but the issue is still there. I have been praying and hoping for the last couple months this issue is resolved soon because I want to play with shaders on the newer versions, but the performance loss outweighs the visual experience personally.
Huh someone says it was fixed in the latest snapshot, I'm going to try it out
Ok immediately I am noticing an improvement using the latest snapshot + iris/sodium (no ImmediatelyFast though as I am unsure as to if there's an unstable release for that snapshot) but the improvement is only about 15-30% compared to the 80-100% that would be needed to match performance of 1.21.4.
It wasnt fixed
Thought there were other unrelated performance improvements
Yeah :/
I just want to be able to play with shaders man :(
Minecraft uses only 1 CPU core : (
Yes it’s a single core game
C2me can partially fix it
Maybe due to rendering changes in 1.21.5
No Minecraft has always been single core
ironically the changes are actually in preparation for it to become less of a single threaded game, they’re working towards moving rendering to a separate thread rather than being on the main one
oh
it’s still a good while away but that’s the goal before the more complex vibrant visuals features
and the thing is, you actually get significantly more FPS on vanilla rendering with no mods in 1.21.5 compared to 1.21.4 and it makes the game actually playable without mods again on higher render distance
the problem is, in doing so they obviously had to make major rewrites in the rendering code to make it work and that can lead to unintended behaviour down the line and in this case with this thread, it's an unintended behaviour because its not like we are getting the same fps despite better vanilla rendering we are actually losing 45 to even 60% (in extreme cases) of our fps updating to the minor version and ontop of that, increasing the shader quality actually doesn't have that big of an effect as it used to either which definitely tells us that there's a bottleneck somewhere
not sure where you're getting this from because on systems where the issue is reproducible, vanilla performance is worse. No mods involved. See the mojang bug tracker
In my testing this FPS on reduction is far from what I'm getting at all
and I retested this as well on my end
Java Edition is coded in an awful language, compared to Bedrock which uses C++, an optimized coding language.
java is not the performance bottleneck
Simply moving to a faster language doesn’t mean the limiting factors I’ve covered in this video would magically be solved. Trying to generate and render a million chunks will always be difficult, regardless of the language being used.
Feel like I've seen this somewhere...
:linus:
:ame_smug:
Java is not the reason for this
Java's implementation in Minecraft though was an issue
and overall just inefficient rendering code which isn't Java related either
so neither have to do with the language itself