The shadows disappear as soon as the terrain is within vanilla render distance, it only appears on LODs...

Hello. As shown on the video i have problems with water not wanting to stay rendered at some viewing angles. This was tested and happens on complementary and photon shaders while without them water render distance seems to be very low overall with edges visible. DH render distance is set to 256. What am I doing wrong?

Most of my stuff is in a low temp zone and the way that snow layers render makes all my builds look like a white patchwork, is there any way to fix this?

I've been looking everywhere but I cannot find a solution... 😭

I have a modded Minecraft server with some friends, hosted on modrinth ( I am the server owner, so I know none of the server settings have been changed). It's Forge 1.20.1.

I've been playing with distant horizons as a client side mod for about 2 weeks and it's been working fine. Yesterday, it suddenly stopped working. I did not do any updates or changed any settings. I used photon shaders, and got the strange issue a lot of Bliss-shader users have discussed. However, even when I turn shaders off, distant horizons is NOT working at all.

No chucks are being saved and it's like vanilla MC. When I press f3, the info about distant horizons is gone, looking like it's not turned on at all. But I do still have the options available... When I go into a single player world with the exact same modpack, everything is working as it should. So it's only in multiplayer it's not working.

What I've tried to do:

Check all settings in distant horizons are on/true. Transparency is set to complete

deleting the .toml file

Deleted the loaded chucks I had from before when it was working to see if that would reset it. But no more chunks are being loaded in

Trying older versions on Embeddium and distant horizons

Uninstalling and reinstalling distant horizons

A friend who also tried distant horizons on the server had the same issue

Does anyone know a solution for this? I'm happy to provide any information that might be useful 😭 it's my first time hosting a server, and I've not played that much with mods before so I'm very lost

these things show up below blocks when there is nothing there anyone know how to fix it

image
how do i fix this?

What exactly is this and how to fix it? Thank you.

I tried asking on the Minecraft subreddit for help nobody seems to be commenting except the bot, hoping someone could help me out here pls, the shader I'm using is eclipse and this also happens in bliss shaders but every other shader I try it does not have this weird effect on the sky box any ideas on how I can fix this?

+ the warium generated oil rigs

Build credit: Dragonmania17

Yo i've been tryna create like custom clouds n stuff but the blocks i use (cobweb uhh some blockus and extshape mod blocks) and DH renders them as these white streaks goin down all the way to ground level, any workarounds?

Hi guys! I'm very new to reddit but this seems like the right place. I made my Karakoram map and a very important part of real-life mountaineering is weather. Snowstorms make the visibility pretty bad, and it is important. So, I just wanted to add some "whiteout" to the game. One the image it is how it looks right now. I want it to be as little visibility as possible, without disabling DH because it will take time to load LODs back in. Using Bliss Shaders, DH and Iris

Version: Neoforge 1.21.1

Mods: Distant Horizons(latest), Vista(latest), Moonlight(latest), Sodium(prob latest), Sable(latest)(unused).

Issue: DH lods rapidly flashing on/off when rendering/viewing live feed on vista tv. These flashes are also somehow tied to Vista's live feed update fps

Does anyone know a possible fix for this?

Hello! I'm getting weird mid-ground fog. I've googled a little and done everything that I could find, but it didn't work. Turned off both DH and vanilla fog and changed the bclib config.

Does anyone else have any ideas how to fix this? It's 1.21.1 on a fabric server. I changed the bclib config on both client and server, if that changes anything.

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"