TreyRuffy
[Bug]: Performance tanks when the F3 is open on 1.20.5
Describe the Bug
FPS drops by about half (120 -> 60) when the F3 menu is open. Note that I'm not using the default configuration, but even then my configuration isn't that cluttered and doesn't have that many modules. And also performance was (almost) perfectly normal on 1.20.4 with the same configuration (plus the "System" module, which was removed for reasons described below).
Steps to Reproduce
- Load the game in 1.20.5
- Remove all uses of the "System" module to avoid crashes (due to the use of the MinecraftClient.is64bit method, which was removed with the 1.20.5 update since support for 32 bit systems was dropped)
- Go into a world
- Press F3
Expected Behavior
Normal performance even when the F3 menu is open, as it was the case on 1.20.4.
Screenshots
No response
Modloader Type
Fabric
Modloader Version
0.15.10
Mod Version
10.0.0-alpha.1
Log Output
No response
Additional Context
No response
A lot of these performance issues could be related to not having draw call batching and not pace limitting (see very old issue https://github.com/cominixo/BetterF3/issues/5 )
Mod Immediately Fast and Exordium are effective workaround, but this mod may consider doing batched drawing itself and pace limiting itself to be self contained.
Also experiencing performance issues on 1.21. My game runs at ~144fps (capped by v-sync) until I open F3, where it plummets to ~30fps.
By opening the FPS bar graph (F3+1 in your menu I believe), closing F3, waiting a few seconds, and opening F3, you can see that the FPS gets much better while the F3 menu is closed.
