Strange artefacting with shaders
When I enable shaders DH LODs disappear and this strange artefacting appears, not changing when I look around. I had shaders working with DH and am unsure what changed for it to break.
Mod list
Solution:Jump to solution
Alright, after some more testing I've found out the true cause of this issue.
I had installed an optimization mod called Palladium, which, when installed with Immersive Engineering, Embeddium, Oculus and DH causes the issue above when toggling on shaders....
20 Replies
Can’t see any ghosting on the screen shots
Could you maybe try recording a video?
Or mark the ghosting in a circle or something?
Ghosting with shaders is usually caused by TAA, so you can try reducing or disabling it
The "ghosting" you're seeing is not what people typically call ghosting.
What you're seeing is just the shader being broken with DH. Try a different shader that has DH support
If you mean the white LODs, that isn't usually broken, that is just a debug setting present in probably every shader there is
Though usually it affects both LODs and vanilla at the same time
I would first suggest resetting the shader settings to default
And only then if it still won't work, you will have to change the shader
I've already reset the shader settings to no avail. This happened with BSL which is compatible with DH and I had them working together perfectly fine but at some point something which I do not know changed and now this is happening. I also tried another shader and had the exact same problem
This artefacting appears when I toggle on the shaders and then remains like that unchanged even when I look around. Like it's burned in to the background
Ah, I understand now
Do you have any other mods?~ I see the book in the SSs
Quite a lot
/logs
You should send your
latest.log file to provide additional useful information.
Logs are usually 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.Maybe some incompatibility
I've sent it
Oh, right, sorry
After enabling shaders
BetterF3 spams console with errors
Try removing it, it that won't work, send new logsStill happens. I do see some shader and DH errors in the log though
Do the shaders work when DH, Oculus and Embeddium are the only mods?
Yes, with no issue. They also worked with this pack previously, but there was a slight kerfuffle (automodpack screwed with some things and I thought I reverted them but alas) and this now happens
Make sure
Alex's Caves fix from the FAQ is applied correclty
Outside of that
/binaryTry 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.
Is your best bet
It is
Unfortunate :/
The problem mod in question was Immersive Engineering.
Immersive engineering does work with embeddium, oculus and DH, but not in this modpack for some reason.
I've removed Immersive Engineering as I wasn't able to make it work and the issue is gone.
Solution
Alright, after some more testing I've found out the true cause of this issue.
I had installed an optimization mod called Palladium, which, when installed with Immersive Engineering, Embeddium, Oculus and DH causes the issue above when toggling on shaders.