Fps drops at certain direction but only with biome mods and shaders
Sorry for posting this for a second time. But after no one replied after 21 hours, and after I thought I found a solution (I did not), then closing the post, I'm trying again.
I get huge fps drops whenever I look at a certain direction, which gets worse when I start moving to said direction. This is solved when I manually (not reload) turn the shader off then back on, the frames seem to stabilize... Then I look at another direction, usually behind from where I turned the shader on, then I get drops again.
This only happens when DH is used with shaders and with a biome mod, such as Biomes O' Plenty and Oh the Biomes We've Gone
I'm using DH 2.1.2 on Minecraft 1.20.1, Forge 47.3.0, with the latest versions of Embeddium and Oculus, with Bliss Shaders
My specs are:
GPU: RX 6600
CPU: Ryzen 7 5800X3D
Ram: 16gb
Some things to note:
- I am ONLY using Oculus, Embeddium, DH, Biomes O' Plenty/Oh the Biomes We've gone and their dependencies
- I've tried testing with and without performance mods such as Entity Culling and Ferritecore with no luck
- I've confirmed this issue isn't exclusive to Bliss, this happens with all shaders, or at least the three I've tested
- This doesn't happen if DH and shaders are used without biome mods
- This doesn't happen if DH is used with biome mods without shaders
- This doesn't happen if shaders and biome mods are used without DH
- I have tried to tweak with DH settings such as distant generation and other settings
- Min and max ram are 8gb
- I've even tried to isolate the biome mods' dependencies one by one, such as Terrablender, the issue doesn't happen
- Downgrading embeddium to 3.20 or 3.21 did not work
4 Replies
Video footage:
Can you see if it also happens with DH 2.2.1, and the release candidate that was just posted in #announcements ?
/oculus
Oculus may work, but can produce unexpected results, it is preffered to use Iris on Fabric or Neoforge instead.
To use oculus with DH, it is only possible to use minecraft 1.20.1 with forge. Oculus 1.7 is the only officially released version of Oculus that works with DH, and only works with DH 2.1.x. If you are using DH 2.2.x with Oculus 1.7, that is the reason for your crash.
For DH 2.2.x, the only option is to use an unreleased version of Oculus found at https://github.com/Asek3/Oculus/actions/runs/11198312573/artifacts/2020008921 (you need to be logged in or it will 404). Unzip the given file, take
oculus-mc1.20.1-1.7.0.jar. and put it in your mods folder.
For DH 2.3, you need the unreleased version mentioned above, and edit it to make it work with DH 2.3:
- unzip the mod .jar
- go inside the META folder
- edit mods.toml to say it is Oculus 1.8.0
- save the file and zip the mod file back (zip the files and not the folder)Yessir, one sec
After editing mods.toml to edit the version from 1.7.0 to 1.8.0, rezipping then renaming oculus from zip to jar, the jar just causes Minecraft to crash now
But also the latest available version of DH for Forge still had the issue
Nevermind, got the jar to work, will come back with results in a bit
Nope, DH 2.30 also still yields those immense fps drops-
Yeah, did a couple more tests with no luck.
After a lot more testing, the issue isn't DH. Shaders just... Do this. Closing this Post.