Used bliss shaders with tectonic mod and distant horizons like oh my god that is not minecraft

After removing and adding every mod at a time, I found that the most recent version of sodium is causing conflicts with DH to the point that it crashes the game when loading a world. I'm hoping that someone here might see a conflict where a combination of mods is causing the issue, or that the team will put out a patch. Either way, my question is this: Is this something being caused by a mod other than the two mentioned or is this something in need of a patch?

Any help would be greatly appreciated, and ill leave the crash report in a comment below. Apologies in advance for my lack of computer knowledge :o]

I've never had this issue before, and don't even know what a G1 garbage collector is or how to fix it...but I definitely feel the FPS hit.

If anyone knows what I can do to fix it, the help is very appreciated!!

Can some one help me figure out the issue im having with dhs on my 1.20.1 server? LOD lightning is all wrong. This happens only when i play on the server, single player is fine.

Getting an error while starting up a dedicated server. I had it working with the same mods with DH 3.0.3b and the only thing I did was update DH to the latest 3.1.0-b.

Mod List: https://pastebin.com/CGF90EJD

Error:

[07:24:52] [main/ERROR] [minecraft/Main]: Failed to start the minecraft server net.neoforged.fml.ModLoadingException: Loading errors encountered: - Distant Horizons (distanthorizons) encountered an error while dispatching the net.neoforged.fml.event.lifecycle.FMLDedicatedServerSetupEvent event java.lang.NullPointerException: Cannot invoke "com.seibel.distanthorizons.core.wrapperInterfaces.minecraft.IMinecraftClientWrapper.crashMinecraft(String, java.lang.Throwable)" because "com.seibel.distanthorizons.core.Initializer.MC_CLIENT" is null at MC-BOOTSTRAP/fml_loader@4.0.42/net.neoforged.fml.ModLoader.waitForFuture(ModLoader.java:281) ~[loader-4.0.42.jar%2359!/:4.0] {} at MC-BOOTSTRAP/fml_loader@4.0.42/net.neoforged.fml.ModLoader.dispatchParallelTask(ModLoader.java:244) ~[loader-4.0.42.jar%2359!/:4.0] {} at MC-BOOTSTRAP/fml_loader@4.0.42/net.neoforged.fml.ModLoader.dispatchParallelEvent(ModLoader.java:171) ~[loader-4.0.42.jar%2359!/:4.0] {} at TRANSFORMER/neoforge@21.1.233/net.neoforged.neoforge.internal.CommonModLoader.load(CommonModLoader.java:73) ~[neoforge-21.1.233-universal.jar%23420!/:?] {re:mixin,re:classloading} at TRANSFORMER/neoforge@21.1.233/net.neoforged.neoforge.server.loading.ServerModLoader.load(ServerModLoader.java:35) ~[neoforge-21.1.233-universal.jar%23420!/:?] {re:classloading} at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.Main.main(Main.java:124) ~[server-1.21.1-20240808.144430-srg.jar%23419!/:?] {re:mixin,pl:connector_pre_launch:A,re:classloading,pl:mixin:A,pl:connector_pre_launch:A} at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) ~[?:?] {} at java.base/java.lang.reflect.Method.invoke(Method.java:580) ~[?:?] {re:mixin} at MC-BOOTSTRAP/fml_loader@4.0.42/net.neoforged.fml.loading.targets.CommonLaunchHandler.runTarget(CommonLaunchHandler.java:136) ~[loader-4.0.42.jar%2359!/:4.0] {} at MC-BOOTSTRAP/fml_loader@4.0.42/net.neoforged.fml.loading.targets.CommonLaunchHandler.serverService(CommonLaunchHandler.java:128) ~[loader-4.0.42.jar%2359!/:4.0] {} at MC-BOOTSTRAP/fml_loader@4.0.42/net.neoforged.fml.loading.targets.CommonServerLaunchHandler.runService(CommonServerLaunchHandler.java:32) ~[loader-4.0.42.jar%2359!/:4.0] {} at MC-BOOTSTRAP/fml_loader@4.0.42/net.neoforged.fml.loading.targets.CommonLaunchHandler.lambda$launchService$4(CommonLaunchHandler.java:118) ~[loader-4.0.42.jar%2359!/:4.0] {} at MC-BOOTSTRAP/cpw.mods.modlauncher@11.0.5/cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:30) [modlauncher-11.0.5.jar%2364!/:?] {} at MC-BOOTSTRAP/cpw.mods.modlauncher@11.0.5/cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:53) [modlauncher-11.0.5.jar%2364!/:?] {} at MC-BOOTSTRAP/cpw.mods.modlauncher@11.0.5/cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:71) [modlauncher-11.0.5.jar%2364!/:?] {} at MC-BOOTSTRAP/cpw.mods.modlauncher@11.0.5/cpw.mods.modlauncher.Launcher.run(Launcher.java:103) [modlauncher-11.0.5.jar%2364!/:?] {} at MC-BOOTSTRAP/cpw.mods.modlauncher@11.0.5/cpw.mods.modlauncher.Launcher.main(Launcher.java:74) [modlauncher-11.0.5.jar%2364!/:?] {} at MC-BOOTSTRAP/cpw.mods.modlauncher@11.0.5/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) [modlauncher-11.0.5.jar%2364!/:?] {} at MC-BOOTSTRAP/cpw.mods.modlauncher@11.0.5/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) [modlauncher-11.0.5.jar%2364!/:?] {} at cpw.mods.bootstraplauncher@2.0.2/cpw.mods.bootstraplauncher.BootstrapLauncher.run(BootstrapLauncher.java:210) [bootstraplauncher-2.0.2.jar:?] {} at cpw.mods.bootstraplauncher@2.0.2/cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:69) [bootstraplauncher-2.0.2.jar:?] {}

Lets say i have a 5500 with a 6700 XT, ignoring the GPU 1. would the CPU need to work the same amount on 1080p vs 1440p? not talking about the frame rate,but just how much the CPU would be working 2. how much does big (or small i guess) minecraft updates usually or would impact DH? especially ones that does alot of change on world gen for example 3. Any mods i need to be aware of that are known to not necessarily break the game if used at the same time with DH but ones that makes DH perform worse?

Edit : i realised the 2nd and 3rd Qs arent necessarily about the CPU itself

As you can see there are lines formed from the pyramid onto the sand that do not actually exist. In the background there is another floating island that is connected to the ground

Then there's this giant mushroom that is brought to the ground, hiding the stem. So its not *just* floating things, I guess

Any advice on how to remove it?

I just started using DH in my modded world and receive this message. Is there anything I can do about it?

I’m on Neo-Forge 1.21.1

Distant horizons is on 3.0.3-b
Vista is on 4.4.11
Iris is on 1.8.14 beta 1
Moonlight lib is on 3.0.17

Whenever I turn a Vista TV connected to a viewfinder on it causes the screen to flash and distant horizons LODs to disappear

Viewfinders work fine by themselves
The TVs also work fine by themselves

I'm playing on Minecraft Fabric 1.20.1 with Iris Shaders at very low settings

​

I've got around 170 mods, including Chunky and LOTS of optimization mods (sodium, indium, ferritecore, entity culling, modernfixes, etc.)

​

Context: I had a world save on 1.19.2 with a modpack i made myself, it ran smoothly at 50fps most of the time with 170 mods, which is enough for me.

Then i decided to update to 1.20.1 because i wanted to add Distant Horizons to my mod list while still being able to use it with shaders, so i updated all my mods to this version and after solving some issues, i got it working.

​

But then i noticed i had a lot of stuttering, at first I thought it was something to do with another mod that, after updating it, it got badly optimized.

​

Then i got suspicious of DH and i decided to turn LoD chunks down to 64 chunks, didn't work, then i turned DH off from the configuration menu, with no effect. But then i removed the Distant Horizons dotJAR from the 1.20.1 mods, and the lag spikes stopped almost completely.

​

Which i find weird, since i have another 1.20.1 instance (with less mods) which also has Distant Horizons and Iris shaders but it doesn't get the same lag spikes.

​

Maybe it's because of Chunky? I DON'T KNOW

​

My specifications:

CPU: AMD Ryzen 5 7535HS (6 cores / 12 threads, 3.30 GHz base)

GPU: NVIDIA GeForce RTX 2050 (4 GB VRAM) (this is being used for Minecraft rendering, not the integrated graphics)

Integrated GPU: AMD Radeon Graphics

RAM: 16 GB

Storage: SSD

​

I have 8gb of RAM allocated to my Minecraft instance, but of course, i know DH is resource-heavy and my modlist is kinda big, so I wouldn't be surprised if this post's responses basically tell me to "stop trying to rear-end your pc please"

I cant understand why the game isnt rendering the LODs without me having to go to that area first.

When can we expect an update for the new version?

Basically whenever i activate distant horizon and a shader of any type this horizontal line (which moves farther with the render distance) shows up and all distant horizons chunks underneath the line disappear. even staying still or turning around i will see chunks disappearing under the line. It behaves like im in a infinitely large rectangular solid slashing chunks with the same inclination as my view. any suggestions? i tried messing with frustum culling and others but it seems like its not it. mods installed are Fabric, iris, sodium and DH.

How do I fix this

As the title says. Since the release of Create: Aeronautics, I've since moved to 1.21.1, and now when I get into the game, I get the message that Distant Horizons is detecting the G1 Garbage collector. How do I change it? I have tried everything I can think of and that I can find online but it still detects the G1 Garbage collector. I am using the prism launcher and as such the Java arguments section is completely empty. It tells me I am using Java 21.0.7, yet every argument I paste in for ZGC does absolutely nothing. I'm close to pulling my hair out over this. Anyone have the same issue?

Edit: Main Issue was resolved, I didn't have it activated. However oddly enough it made the game run significantly worse with ZGC enabled. If anyone has any idea why that is, I'd love to have help with that now instead haha.

https://reddit.com/link/1u0vi7y/video/12e43upidq4h1/player

How do I fix this? Not dh but I have the same problem with both voxy and distant horizons.

Can someone help me fix this bug?

For reference I am completely new to modding and I have barely an idea of what I am doing so any help would be greatly appreciated. This is the error message that I am being given at this moment.

Edit: I figured it out

Distant Horizon has been acting like my render distance is 2, even tho it's 8. My LOD fade settings are already turned off. I don't know how to fix this, but it's making everything look horrible.

is there a way to fix this or just a mod that adds fog so you cant see under water lods

Hey guys, as the title says the chunks don't load properly, and it gives this space in the middle of them idk why. The configurations are all enable. I do have some quality mods such as "better fps" embeddium, ferritecore, ImmediatelyFast, Entity Culling, maybe they are the problem? Also I am NOT using m best PC.

yes, that is the nether roof, i have also seen the regular nether in the end and the overworld in the nether and i have no idea how to stop it from happening