It REALLY breaks the fps calculating
sodium fps display
essential GUI fps display
and even F3 fps display...
F3 screen(with better f3 mod)

sodium fps display(top-left corner) and essential GUI fps display(top-right corner)

and my latest.log: (my pack is VERY large and full of messy log infos and errors...)
latest.log

without BadOptimizations:

:(
Dramatic

sodium fps display

Sodium has an FPS display?!

essentials GUI fps display

Essentials isn't open source, so I don't know how it handles its FPS counter.

and even F3 fps display with better F3

Looking into the source, BetterF3 seems to get the FPS like this:

final int currentFps = Integer.parseInt(client.fpsDebugString.split(" ")[0].split("/")[0].trim());

It accesses and parses fpsDebugString, the thing this mod removes for a performance boost. Even worse, it parses it and gets the FPS count from that string, which is a big performance drop, and completely unnecessary because MinecraftClient has a field named currentFps. Looking into more of its code, BetterF3 seems to take a BIG hit on performance, but if you're persistent, I made some a fork that fixes this, and a PR so that it might get merged:
1.20.4 source
1.20.4 download
1.20.2 source
1.20.2 download
1.20.1 source
1.20.1 download
Anyway, when I wrote "use an FPS mod," I meant a more typical one that gets from MinecraftClient.currentFps, which this mod does not break, like this mod.

also quick note: vanilla F3 fps counter is not broken, BetterF3 broke it

sodium fps display

Sodium has an FPS display?!

essentials GUI fps display

Essentials isn't open source, so I don't know how it handles its FPS counter.

and even F3 fps display with better F3

Looking into the source, BetterF3 seems to get the FPS like this:

final int currentFps = Integer.parseInt(client.fpsDebugString.split(" ")[0].split("/")[0].trim());

It accesses and parses fpsDebugString, the thing this mod removes for a huge performance boost. Even worse, it parses it and gets the FPS count from that string, which is a big performance drop, and completely unnecessary because MinecraftClient has a field named currentFps. Looking into more of its code, BetterF3 seems to take a BIG hit on performance, but if you're persistent, I made some a fork that fixes this, and a PR so that it might get merged: 1.20.4 source 1.20.4 download 1.20.2 source 1.20.2 download 1.20.1 source 1.20.1 download Anyway, when I wrote "use an FPS mod," I meant a more typical one that gets from MinecraftClient.currentFps, which this mod does not break, like this mod.

also quick note: vanilla F3 fps counter is not broken, BetterF3 broke it

It's not Sodium's, but Sodium Extra's fps display

Sodium Extra gets its FPS like this:

int currentFPS = MinecraftClientAccessor.getCurrentFPS();

...a normal client accessor to access currentFps. In that case, I don't see how BadOptimizations would break it.

so it is a compatibility problem between BadOptimizations and BetterF3, and it will be fixed recently?

Sodium Extra gets its FPS like this:

int currentFPS = MinecraftClientAccessor.getCurrentFPS();

...a normal client accessor to access currentFps. In that case, I don't see how BadOptimizations would break it.

It's always 1 fps with my 1.20.2 case

Sodium Extra gets its FPS like this:

int currentFPS = MinecraftClientAccessor.getCurrentFPS();

...a normal client accessor to access currentFps. In that case, I don't see how BadOptimizations would break it.

It's always 1 fps with my 1.20.2 case

The fps used to be normal after pressed f3 ingame, but with the latest release always 1 in debug screen

so it is a compatibility problem between BadOptimizations and BetterF3, and it will be fixed recently?

I made a PR to BetterF3 to fix this, and you can download the fixed version in my message in case it doesn't get merged.
Also, as I said, BetterF3 takes a huge hit on performance.

With BetterF3 7.0.2 installed, the fps is still 1...
Guess what, I have VMP.
So #9 ?

Yes I have VMP too

VMP fixed, should be out on curseforge/modrinth in 20 minutes or so

The latest official version of BetterF3 should now work. No need to use the fork anymore!