C2ME conflicts with Sodium and then breaks F3 debug screen.
frosthuuuund opened this issue ยท 7 comments
Describe the bug
C2ME conflicts with Sodium and because of that breaks F3 debug screen.
When you set render distance above 32, client chunks section starts showing wrong information about how many clientsided cached chunks are.
This number usually is 2^8 or 2^16, depends of current render distance, but when you go beyond non-extended render distance, lets say 128 chunks, this value is 2^18.
To Reproduce
Steps to reproduce the behavior:
Install 1.21, actual version of C2ME at this moment, and Sodium 0.5.11.
Expected behavior
The debug screen should show the correct number of cached chunks on client side.
Runtime info (please complete the following information):
- OS: Windows 11 24H2 Preview
- Minecraft version: 1.21
- Mod version: c2me-fabric-mc1.21-0.2.0+alpha.11.106
Crash reports / logs
Not necessary
Checklist
- I am using the official version of the mod.
- I tried the latest development version but the issue persists.
- I searched for similar open issues and could not find an existing bug report on this.
Where is the number you are looking for on the F3 screen? Have you waited long enough for the chunks to actually load in?
I don't have to wait, this value is constant, i guess...
C2ME + Fabric API
Oh, and also, you have to set render distance, and then return to the game to get this value updated.