Using Lithium alongside a vanilla fabulous shader causes ambient occlusion to flicker
LucilleTea opened this issue ยท 8 comments
Version Information
Lithium 0.7.5
V++ 1.8 (a fabulous shader resource pack)
No other mods - not Sodium!
Expected Behavior
The game should render as the resource pack usually does.
Actual Behavior
The ambient occlusion on blocks flickers when you move.
Reproduction Steps
Enable the resource pack
Enable fabulous graphics
Load a world
Move
Other Information
Only occurs on fabulous graphics as it relates to the shader.
Occurs regardless of the smooth lighting setting.
First reported by Reaper Lord in a support thread, unknown hardware. https://discord.com/channels/602796788608401408/912671298478538763/912671300793819137
Confirmed by myself on a GTX 1070, windows.
Maybe this is related to the voxel shape optimizations, I don't have another idea.
Trying adding mixin.shapes=false
to the config. That disables several optimizations, we can narrow it down later if that works.
I'd try that but I have no idea how I could edit that with just the mod file. I'm not sure if it is related, but I am also experiencing a strange white box reaching from the center to the bottom right only when I look around -45 and 45 degrees (South East and South West.)
Both of these effects appear to be rotation and location dependant, as I have been able to find some precise positions that trigger each change. When I walk backward into a corner I can trigger the AO issue and when I stand still it stops
In your game directory (.minecraft) there should be a config directory with a lithium.properties config file inside. Edit that with a text editor
Doesn't seem to make much of a difference. I did notice it mostly happened while walking, flying doesn't seem to affect it as often. Similar to the rotation thing I noticed earlier.
Reproduced with Lithium 0.9.0 and latest V++ on intel integrated, linux, dev environment
Seems like adding the line
mixin.math.sine_lut=false
to the lithium properties file in the config directory works around this issue
Fixed in 46fede1