1.20.1 server weirdness rendering shaders/DH?
When I load in, I have DH working with no shaders, then I enable ComplementaryUnbound5.2.2 , 5.2.1, or 4.something, it has weird issues like this. I've tried turning shaders off then back on again as well.
30 Replies
/shadersupport
Distant Horizons and Iris Shader Support Requirements:
- DH 2.1 + Iris
- Minecraft 1.20.1, 1.20.4, 1.20.6, 1.21
- Sodium 0.5.8+
- Iris 1.7.0 - 1.7.3
- Fabric API
- A compatible shaderpack: https://gist.github.com/Steveplays28/52db568f297ded527da56dbe6deeec0e
- DH 2.2 + Iris
- Minecraft 1.20.1 (wait for iris 1.8), 1.21.1
- Sodium 0.5.8+
- Iris 1.7.5, 1.8, or newer
- Fabric API
- A compatible shaderpack: https://gist.github.com/Steveplays28/52db568f297ded527da56dbe6deeec0e
Gist
Distant Horizons shader compatibility info
Distant Horizons shader compatibility info. GitHub Gist: instantly share code, notes, and snippets.
/blisssky
This is a Bliss issue, there are 5 known potential fixes:
- Turn shaders off and back on (repeat after each next fix)
- Set transparency to complete in DH settings
- Decrease or increase the DH RD by 2 - 8 chunks
- Restart the game after applying all the previous fixes
- Change the shader to different one
,){kind=link}
Ignore the Bliss part here, it usually happens with bliss, but it is Iris issue so all shaders can trigger this
Does everything check out?
But I'm actually using optifine
on a forge server
Try redownloading the shader from the link
Optifine does not have DH shader support
It will never look good
dangggg ok gotcha
so is there any way to use DH with shader packs on a forge server??
If you want to see less bugs go back to DH older then 2.1, it works with Optifine a bit better, but still bad
dang..
With DH 2.1 you can use Oculus 1.7
With DH 2.2 Iris for Forge
Iris For forge is only on 1.20.1 and 1.21.(1)
Oculus 1.7 is only on 1.20.1
Sorry im a bit confused, should I use iris or oculus for 1.20.1?
If your other mods will be compatible with the newest Sodium 0.6.0 for forge and Iris 1.8 for forge use this combo
But Sodium 0.6.0 is incompatible with a lot of mods
Ok let me try that out
in this case oculus 1.7
okk gotcha, so if sodium 0.6 causes issues, use oculus 1.7, and then i should be good?
oh im actually not even seeing a way to use sodium on a forge server
Yes
and oculus and all that servers zero purpose in my server mods right? Strictly client side?
I downloaded Oculus 1.7 for forge and now my client crashes instantly with no crash log, just Exit Code 1
yes
For oculus you have to go back to DH 2.1.2
Ahh right right sorry about that. Ok I'll try that now then. Thanks!
Sodium is also client side
And Sodium 0.6.0 and Iris 1.8 for forge for 1.20.1 are only avaible on Iris DC server
https://discord.com/channels/774352792659820594/883067831485366304/1268783380015878144
Ok so now I have DH 2.1.2, and Oculus 1.7 both ony my client and not my server, but when I run my client now, it insta-crashes with only exit code 1. Neither of those two mods are on my server either.
can you send logs?
/logsstored
You should send your
latest.log file to provide additional useful information.
Logs are located in the .minecraft/logs directory.
On Windows: %appdata%\.minecraft\logs
On Linux: ~/.minecraft/logs
On Mac: ~/Library/Application Support/minecraft/logs
Please upload the file to mclo.gs instead of sending the raw file. This makes reading the contents of the file a lot easier and improves the chances of you getting the help needed.
After uploading the file, click on Save and send the link.Do you have embeddium installed?
It's required by oculus
Sure didnt, installing now. Puhpine to my rescue once again!
ah dang crashed again just the same ,sending latest log.,
Oh! There we go! I had a bad version of embedium I think. All is good now! Thanks so much for your help once again @Puhpine (GMT +2)
Nice! Glad to help