Photon shaders not loading the terrain (vanilla Render Distance)
I am using Photon shaders and I don't have the option to see the whole terrain I set up in Distant Horizons. Also with other shaders where I can see the whole terrain configuration, just the vanilla Render Distance applies the shader effect. The rest is just shaderless.
65 Replies
Are you using Iris?
Make sure you have the latest version of photon, and check if you meet the other shadersupport requirements as well
/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, 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.
No, I am running Forge on 1.20.1
I use Oculus and Embeddium
Which versions of Oculus and DH?
1.7 and 2.1.2?
Yes
Does it work without any shaders?
Not really
Render distance is very low
A bit bigger than vanilla but not much
/slowgen
World generation in general is quite slow, if you want to speed it up:
Install Noisium and Faster Random, these mods can improve generation speed by a couple percent.
Make sure to remove the C2ME mod as it significantly slows down DH chunk generation by up to 35%.
Increase
CPU Load in Distant Horizons settings for faster generation, but you will experience more lag spikes and stuttering due to heavier workload on CPU.
To see if Distant Generator is really working or not:
1) Check CPU usage while in-game, using Aggressive settings of CPU Load. If CPU usage's hovering around 80-100%, the LoDs are generating in the background.
2) Go to DH settings > Advanced Options > Debug > Wireframe, set Enable Debug Wireframe Rendering and Show World Gen Queue to True.
Enabling both settings will show you the visualization of world gen tasks queued and working on the map (blue boxes for queued tasks, red boxes for working tasks)Try the second part
What are your vanilla and DH RDs?
Vanilla: 32
DH: 128
You can most likely decrease the vanilla RD, recommended vanilla RD with DH is between 8 and 16 with shaders and 12 to 24 without shaders
Try vanilla RD 2 to see if DH LODs are present
Vanilla RD 2
Try both parts
However with shaders, RD 8 is like this
My guess it that the worldgen is just slow
It's usually pretty fast
/overdraw
Hole at the edge of vanilla Render Distance, especially during movement:
This is caused by either vanilla terrain not loading in fast enough, or shader's incorrect overdraw prevention implementation or configuration (if you use one)
Some world gen speed improvement can be found when adding these two mods, but the affect will be minor:
- Noisium
- Faster Random
There is another mod that may help:
C2ME. However, it can decrease DH generation speed by up to 35%.
The easiest fix is to move slower and/or ignore it. This hole is most visible while moving over not generated (by vanilla) terrain. Moving over that terrain every subsequent time may not create the hole. And moving slower will give MC more time to load the chunks as you go.
If none of that helped, you can also tune the overdraw prevention, look at the third section to know how.
Low quality full blocks behind and around non-full block, e.g. fences or ladders:
This is intended behavior, to prevent holes in the world while you move, DH will overlap with some part of the vanilla terrain.
How much of the terrain is covered is determined by the overdraw prevention:
- 1.0 will mean DH LODs start where vanilla chunks end.
- 0.0 will mean that DH render everywhere starting from your position.
To fix this, you can either:
- Increase your vanilla RD, which will move the DH LODs further from you.
- Tune the Overdraw Prevention setting, see the next section to know how.
Where to edit the overdraw prevention setting?
Overdraw prevention setting can be edited inside the DH config under:
Advanced > Graphics > Advanced Graphics
But if you use shaders, they will override and take control of the overdraw prevention.
In that case, check the shader's settings, if overdraw prevention is not there, contact the shader devs or change the shader you use.Do I download those mods?
You most certainly can
Is it recommendable for me?
Noisium for sure
They will speed up the worldgen
Okay, let me try
Thing is that with shaders I can't get more generation than vanilla one
What is your DH CPU load?
I already had Noisum
Maxed out
/chunky
Chunky is known to cause LODs to turn into swiss cheese and bloat up world size, as can be seen in the attached screenshot.
We recommend you enable "Distant Generation" in Distant Horizons' settings and wait.
If you actually want to pre-generate vanilla chunks along with LOD data, disable Distant Horizons, wait for chunky to finish, then re-enable Distant Horizons.
I have Chunky yeah
This has been appearing before using Chunky though
Also some shaderes that don't give me this RD issue, like Complementary Shaders, just apply the shader effect to the vanilla radius
/logstored
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.Here
Oh wait
Didn't read the last part sorry
Here
You have Oculus 1.6.15a not 1.7
Only 1.7+ has shader support
Yeah 1.7 crashes my game for some reason
Let me try again
/binary
Try a binary search and figure out which mod is causing it.
So disable half of the mods, see if issue is still there, if yes disable half again etc etc until you find the mod that's causing the issue.
Either you find a mod that crashes Oculus 1.7 or you won’t get DH shader support
Yeah, thing is that I am using a modpack with my girlfriend which could break the game
You can test it on a new world
Or on a separate instance
I am getting this
With Oculus 1.7
You have to update Create and/or Flywheel compat
Yeah I supposed so, let me check
You can also update DH to 2.1.2 for less bugs
Now Oculus 1.7 works
Let's see
Okay, something changed
Now shader effect applies to the whole render distance
But render distance is pretty low for some reason
You have a lot of mods, the worldgen speed is just slow
It isn't usually :/
On modded worldgen on 13900k 128 RD can take even an hour
I have an i9-13750
Do the second part
Which second part? The debug part?
It you see any boxes, leave the game AFK for half an hour and see if anything changes
Yes
Alright
I see nothing
Can you send a screenshot?
It's like all my loaded chunks have been unloaded
For some reason
Also Chunky does not load all the chunks exactly?
Yeah sorry for all these questions, last time I modded Minecraft, you had to delete the "META-INF" folder in order to work
Do you see the boxes with shaders disabled?
Double check if you enabled the 2 correct debug settings
I don't
They are enabled
Do you have creativecore?
I don't know