Trouble with DH + Oculus + Shaders
Hello, I'm currently having trouble to make bliss and DH work on 1.20.1 on solo and I think i need some help
I'm using the 1.7.0 version of oculus and the latest bliss version (that I downloaded from the DH gitHub) and for some reason when I activate the shaders the textures do a weird flickering between being visible and invisible and sometimes they remain completely invisible. I attached the video of how it looks like, my mod list and the logs.
I don't really know why it's doing this especially since I'm using the recommended versions for both oculus and bliss.
I'm using sinytra connector to use embedium with oculus (these are the only mods I had when I recorded the video)
Solution:Jump to solution
Finally it works! Looks like the problem was neither oculus or the fabric api but rather the fabric version of embedium, I switched to the forge version and it works perfectly fine now
27 Replies
This is an issue ive seen alot with bliss
try Complimentry it looks way better and provides much better options of customization aswell @Rexi666
its the one defaulted to the Reimagined look
couple examples of what it looks like for ya
(Note this is with all settings at the absolute maximum on SLI 2080 Supers)
also so you can avoid the blackhole bug roll back to the 2.10 version
2.12 has been extremely buggy
Thanks for the recommendation, i'm trying the shader rignt now but it looks like the issue remains 😦
delete all the files for Distant horizons
and install 2.10
heres the 2.10 version
and search the word distant here and delete all of these before putting it in
also thats for 1.20.1/
I don't think DH is the issue because the shaders load just fine in chunks loaded by DH but I just don't know what causes this problem
hm, Weird
if it's not the shaders it might just be oculus
try deleteing all of the Oculus Files
however oculus 1.7.0 is kinda needed so idk what to do
delete these and reinstall it
search oculus and then delete those and reinstall it
aight
lmk if that helps
sadly no 😦
that is so weird
might be oculus 1.7.0 that's just this buggy
you sure it isnt DH?
I tried without DH and it still does this
I went on oculus discord and they told me to talk with the shaders dev, which I did and he told me that oculus is probably the problem so I don't really know what causes this issue
I mean what just baffles me is that I (theoretically) DH+oculus 1.7.0+Bliss are supposed to be compatible and work together since the compatibility is noted on the DH github so I have really no clue why it does this
maybe its an issue with Sodium.
try removing or embeddium
wtv you wanna call it
try removing Embeddium and Oculus and using optifine to see if it fixes it.
@Xkiller-5678 dont send jar files please. send a link to the download instead
(and no zip files as well)
im not sure about the issue in the origional post though. optifine wont fix it though. can you remove connector and fabric api and see if it works then?
Try removing Fabric API and connector
Solution
Finally it works! Looks like the problem was neither oculus or the fabric api but rather the fabric version of embedium, I switched to the forge version and it works perfectly fine now
Thanks for the help yall