Embeddium and Oculus not working with supported Shaderpack
I've installed embeddium and oculus in order to use shaders with distant horizons, but every time i install the supported shaders the game gives me the unsupported shader message. I've checked multiple places for supported shaders and none of them have fixed my problems.
41 Replies
use fabric, embeddium and oculus are a pain and buggy and in general just shouldn't be used
is there any other solution, i've made my entire modpack on forge
port as many of the mods to fabric as you can
ooooor
you use unstable releases of Iris and Sodium for Forge
unstable like completely gamebreaking most of the time or rare crashes
crashing all the time, visual bugs
etc.
shame
Forge’s #1 hater right here lol
Which shaders are you downloading and from where?
For some shaders the latest release on modrinth/curseforge isn’t DH compatible
/shadersupport
Distant Horizons and Iris Shader Support Requirements:
- Minecraft 1.20.1, 1.20.4, 1.20.6, 1.21
- Sodium 0.5.8 or above
- Iris 1.7.0 or above
- Indium version 1.0.30 or above
- Fabric API (latest version)
- Distant Horizons version 2.1.0 or higher
- 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.
Use the direct download from this Gist
Don’t go to Modrinth or CurseForge as some of the shaders require the in dev alpha/beta/dev versions
And yes, Oculus has a bit more Buga and is a bit more unstable, but it works correctly most of the time
Oculus, sure. Embeddium, absolutely not.
Embeddium enabled experimental unfinished Sodium code, that is not enabled in Sodium because it can cause corruption.
I never heard of it happening... but the Sodium author probably knows better what his code does
At least never use Embeddium on fabric
But this discusion is pointless because there isn't anything beside Embeddium on Forge
What do you mean? Genuinely never heard off them enabling anything that could lead to corruption.
The Embeddium also has a fabric version, and the only thing that is different from Sodium is an experimental code that the Sodium dev didn't want to enable
Okay, but what is that "experimental code"? That's what I'm asking.
From what I heard the Sodium dev had an argument with Embedium dev
I really don't care about that (especially since the fault lies entirely on the sodium dev for freaking out over the embeddium devs messing around with a private fabric version, that wasn't ever meant to go public initially), I'm asking you about the experimental thing you kept bringing up.
IDK, code written by Sodium dev to enchance the performance, but in the end not enabled by the the dev for reasons
Alpha code
Beta optimalizations
Untested yet code
Experimental code such as transparency sorting. What it does? Renders transparent objects (glass, water, ice, etc.) accurately when any of them are placed in order.
Oh, so the thing they wrote their own code for? That's it?
not exacly, it exists in Sodium, but the Sodium dev decided to not enable it yet
Well, the only known risk for experimental code is that it may melt your GPU if it's not properly implemented.
:harold:
The sodium dev is writing one that's supposed to be more optimized, that they refuse to release in any sort of less-optimized state
the embeddium devs made a slightly less efficient one that they decided to release right away and potentially optimize later
I'm not wither any GPU expert or shader expert or even a best programmer, but if a code author states a code to be unsafe I would rather listen to him
I would love the choice, but it is in the dev's right to refuse it
I'm trying to tell you that it's literally not the same code. The embeddium devs aren't using the wip version of the sodium dev's transparency layering, they're using their own.
I like embeddium, I don't like it stealing revenue on fabric from Sodium dev who is currently homeless
This one maybe not, but I have no idea what got added or enabled
And that is what Piotr Barcz YT might have had in mind
The embeddium devs absolutely aren't stealing revenue. Jelly was complaining about the so-called "revenue stealing" before the fabric version of embeddium existed, it's her fault for not releasing a forge version of sodium themself. And the embeddium devs are literally even giving Jelly a split of the embeddium revenue, so she's getting extra revenue she wouldn't be getting otherwise.
Forge is their revenue
And I don't care when Jelly was complaining.
I complain now when Embeddium is stealing revenue on Fabric
It's not stealing to have a fork of an open-source project.
I know, but you wont change my mind
I still won't like what Embeddium was doing, even if it now redemed itself
They've literally never been doing anything wrong though.
not in a legal matter, but the ethics are quastionable for me and everyone has its own personal standards fot them
At the beginig:
- Embeddium ported Sodium to forge -> Cool
- Embeddium enabled unfished Sodium code while fixing it a bit and released in 95% unchanged code as its own fabric mod earning revenue from it -> really un cool and the problem for me personally
Now embeddium might rewritten a bit of Sodium to perform even better and it is back in the cool territory but the scar remains in my eyes
As long as the donation link in game points to Sodium dev donation page while Embeddium stays in >50% Sodium i'm passive towards it
I've already explained that the "unfinished code" you keep referring to was neither unfinished nor was it jelly's work, it was the embeddium devs' own code that they implemented into embeddium.
Also, the fabric release only came about as a result of jellysquid banning the embeddium devs from contributing to the sodium repository, over private discussions mentioning a conceptual hard fork.
Which is sorta ironic considering it forced them to make a hard fork, achieving exactly what jelly apparently wanted to avoid. In other words, any consequences of the fabric version's existence are entirely JellySquid's fault.
Minecraft has a tendency to attract weird conflicts...
Fabric / Quilt
Forge / NeoFroge
I will need to educate myself on this encounter better
Here it is from the embed devs side.
Anyways in short, embeddium is FOSS still, and sodium isn't any more due to JellySquid's license changes, so I'd much rather support embeddium.
I need to see the Sodium's side first before drawing conclusions, but thanks for additional information
Have a nice day
It seems I was quite misinformed myself
Minor necropost but there is also Xenon as an alternative to Embeddium. Some people have non-trivial performance differences.
Xenon is unmaintained (from what I heard).
harold emoji
At this rate we're going to run out of elements and planets with all the forks. Modrinth and Curseforge will need to make a "Periodic Table & Astronomy" tag.
There's also that transactinide elements if you want to be fancy. Maybe the "beyond super heavy" or even the "hyper heavy" elements.
linus emoji