1.20.1 glass is not allowing sunlight to go through when using the shader comp unbound
Thunderrock424242 opened this issue ยท 23 comments
What happened?
sunlight can't pass through glass
Screenshots
Relevant log output
No response
Minecraft Version
1.20.1
Oculus Version
1.6.9
Rubidium Version
n/a using embedium
Operating System
windows 11
What is your GPU?
nivida geforce rtx 4060 laptop
Java Version
java 17 i think
Additional context
No response
this is a shader bug, try enabling stuff like colored shadows
The shader dev says it's a ocuals issue and iris does not have it
this is a shader bug, try enabling stuff like colored shadows
The shader dev says it's a ocuals issue and iris does not have it
When will it get fixed? I can't use things like glass domes and glass roofs if they're going to cast shadows like this?
This issue also happens on Oculus 1.18.2-1.6.4. So it's not exclusive to just 1.20.1. Been playing Vault Hunters with shaders and noticed that light doesn't pass through glass.
Minecraft Version
1.18.2
Oculus Version
1.6.4
Rubidium Version
0.5.6
Operating System
windows 11
What is your GPU?
Nvidia RTX 4080
Java Version
17.0.9
Forge Version
40.2.9
@GarthF What shader are you using?
So I'm unable to reproduce this in a standalone instance, but if you can only get it to happen in a large modpack I have an idea of what the issue might be. Can you try this version and let me know if the behavior is any different?
I'm not sure what's being used for that, I'll trawl through the direwolf20 pack and see if I can spot anything.
So, did some digging. Xycraft: Override looks like the mod thats doing it. Provides override textures for glass
Thanks. I looked through the mod list and saw the same thing, and I can indeed reproduce with just Xycraft's stuff installed.
I found the problem and solved it in the latest change to #529; when that is merged and released, XyCraft's overrides will not break shadows anymore.
Please check if this is fixed when using 1.6.13.
Pretty sure it's fixed I tested it and looks good
Please check if this is fixed when using 1.6.13.
Will this fix be ported back to the 1.18.2 build as well?
Or should I fill a different bug report for that version specifically?