AnOpenSauceDev
commented
1 month ago This may be a problem with FPS Reducer, because the "non-legacy" engine technically does less than legacy. Not sure what's causing the error here.
Open Flavio6561 opened 1 month ago
AnOpenSauceDev
commented
1 month ago This may be a problem with FPS Reducer, because the "non-legacy" engine technically does less than legacy. Not sure what's causing the error here.
Flavio6561
commented
1 month ago This may be a problem with FPS Reducer, because the "non-legacy" engine technically does less than legacy. Not sure what's causing the error here.
I tried all mods like DynamicFPS, IdleTweaks and Ruthenium but the problem persists... At this point i think that non-legacy engine has like a "base" CPU usage for some reason... I've tried to change FPS capping and the CPU usage is proportional, but at low values it seems like it has a default hight CPU usage.
This is at capped 60fps with legacy engine enabled.
This is at capped 250fps with legacy engine enabled.
This is at capped 60fps without legacy engine enabled.
This is at capped 250fps without legacy engine enabled.
It seems like non-legacy engine has a ~10% more CPU utilization that legacy engine.
ALL OF THIS IS IN SINGLEPLAYER, in some rare cases for some reason the problem is also present in multiplayer.
High CPU usage while having legacy lighting disabled and Minecraft singleplayer in the background with idle FPS reducing mods (as DynamicFPS and FPS reducer).
In some rare cases, the issue is also present in servers.
With legacy engine enabled:
With legacy engine disabled:
Mod used / mod folder:
Methane version: 3.7.0 (Latest for 1.20.6)
The issue is present also in all versions that have the legacy engine switcher, so it is not a 1.20.6 problem.
Removing completly Methane the hight CPU usage disappears.
Possible ways to replicate this bug:
Creating a singleplayer world with legacy engine disabled and leaving minecraft idle with DynamicFPS or FPSreducer set to 1/2 FPS in the backgruond.