spoorn / sodium-forge

A Fabric..... I mean Forge mod designed to improve frame rates and reduce micro-stutter
GNU Lesser General Public License v3.0
28 stars 8 forks source link

Disabling the features.chunk_rendering mixin causes a crash #193

Open tofodroid opened 2 years ago

tofodroid commented 2 years ago

Reproduction Steps

Create a new Forge installation (I'm using 36.2.8) and add only Halogen. Edit the sodium-options.properties file to look like:

# This is the configuration file for Sodium.
#
# You can find information on editing this file and all the available options here:
# https://github.com/jellysquid3/sodium-fabric/wiki/Configuration-File
#
# By default, this file will be empty except for this notice.
#
# Uncomment below line for vanilla seed gen parity
# mixin.gen.fast_layer_sampling=false
#
# Comment out or remove the below line to enable Lithium
# Lithium pathfinding conflicts with some mods such as More Villagers
mixin.ai=false
mixin.features.chunk_rendering=false

Try to load single player world and the game will crash prior to joining the world.

Crash Report File

https://pastebin.com/U8HBHaL0

[Optional] Server/Client logs

N/A

Mods list

Forge: 36.2.8 Halogen: sodium-forge-2.9.10+rev.ea6353c.jar (latest)

Additional Information

I was attempting to resolve an issue I've noticed when using the mod I develop alongside Halogen where recolored blocks are not rendering properly (same issue as #178). Haven't yet found a fix on my end for it so was disabling mixins until stuff worked but ran into this issue in the process.

tofodroid commented 2 years ago

Some additional findings - This was the minimal set of feature mixins I could disable to get things working:

mixin.features.chunk_rendering=false
mixin.features.entity=false
mixin.features.particle=false
mixin.features.debug=false

Side-note: I didn't have to disable debug to get my world open but when I hit F3 it caused the same "Renderer not initialized" crash to happen unless I also disabled that mixin.