Modded Clients not launching with Iris profile
I play with 2 well known custom clients for anarchy servers which both rely on fabric.
Everything for Minecraft 1.21.1
When launching from the Iris + Fabric profile the clients do not launch with the game, no errors nor reference to the clients in the logs.
When launching from the raw Fabric profile the clients seem to work properly.
...
Solution:
Well, for anyone experiencing the same issue and for the archive, I got it fixed by launching the fabric installer after the Iris + Fabric and clients installations. No idea why it worked, but it did.
Anarchy server spawn looks awe-some with these shaders ty for your work....
Shaders with iris
I have installed, terralish, tectonic, sodium iris, and distant horizons
And im using compementary unbound + euphoria shaders...
Solution:
solved

Custom Polytone "default_color" attribute for colormaps causes items to go invisible.
This works perfectly fine when shaders are disabled. Only happens when shaders are enabled.
Using all the latest Sodium, Iris, and Polytone versions....

Black screen
whenever i have iris downloaded in my modpack the game wont update past the initial loading screen and it seems that my resource pack fail to load as well just upgraded from 1.21 to 1.21.1
Iris 1.8+ crashing on launch (intel linux)
Every time I attempt to load Iris, the game crashes on launch with the below error. It works fine when I load Sodium without Iris. I am running on linux (per
glxinfo
: OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (KBL GT2), OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.3.1
), and have tested with multiple game versions + compatible combinations of iris/sodium patch versions.
The error:
```
net.minecraft.class_1041$class_4716: GLFW error 65543: GLX: Failed to create context: BadMatch (invalid parameter attributes)...1.20 Fabric Iris is making blocks see through
I would really like to figure out how to fix this because I love shaders. Basically, on my server I have a custom modpack with 120+ mods, and it works very well; However, the bad news is that whenever I or others install iris, we are able to implement shaders and whatnot, but unfortunately we get some weird bug/glitch that makes some of the world see through.
1.21 incompatible with sodium
when ever I try to start with sodium, both updated to where GDlauncher consied to be the highest for 1.21 it gives me this message

clicking on "shader packs..." doesn't do nothing
when i go to graphics settings and try to click the shaderpacks button, it doesn't do nothing. even tho i download shaders. the only thing i can do is enable them pressing "k". is this a issue related to my modpack (fabulously optimized) or it's iris itself? please let me know.
In iris 1.8.1, the player's shadow is broken in the SEUS PTGI GFME shader.
I updated to iris 1.8.1 on fabric 1.21.1 and noticed a bug: not always, but at certain angles from the sun, the player's shadow becomes patchy and lacks arms/legs. I installed iris 1.8 release, and this problem does not occur.

Photon shaders bug
These dots appear around the sun using photon shaders. I tried reloading and using different performance presents but this issue persisted.
How do I fix/disable this?...

Sky Bugging
When using a shader, the sky is really odd and peculiar around the world outline/player hand
I'm using Complementary reimagined and I honestly have no idea how to fix it
image attached has world outline enabled to highlight the bug, clouds are also enabled which you can see through the bugged areas...

Sky flickering during sunset to night transition
There's a bug where the sky flickers through multiple colors during the sunset to night transition? I've also been experiencing this since 1.21.3
another nametag
Every time I use a shader, a name tag other than the one above my head floats in the air (see the red circle in the picture).
The same thing happens even if you change the shader to a different one....

Trying to install
Getting a fun error message. It's 100% I'm doing something wrong, I just need someone to tell me what that thing is.
Running Java 1.21.1 in fabric. Downloaded the Iris+Fabric version through the installer. Iris is in my mods folder. Used the Iris+Sodium game version....
Solution:
caused by more culling, update it to the latest version

black UI text problems continuing
This has been ongoing for a few days now. After much testing, I have narrowed it down to this. When shaders are enabled and a shader pack selected, the first interaction with a piston causes the GUI to go black. Text on all screens remain black until the game is re-started. I think other things were also causing it when it first appeared. I have pared all mods back to just Iris and Sodium and the problem persists.
If it assists, every time the log gives me the same line when it occus:
UNSUPPORTED (log once): POSSIBLE ISSUE: unit 0 GLD_TEXTURE_INDEX_2D is unloadable and bound to sampler type (Float) - using zero texture because texture unloadable...
Solution:
I’ll release Iris 1.8.4 today

Almost always getting a black screen when switching worlds or shaders
Using Fabric 0.16.9 on Minecraft 1.20.1, whenever I load in, there's maybe a 50% chance I'm loading into a black screen. Whenever I switch shaders, it's definitely going to go to a black screen. If I switch to the nether or end, I always get a black screen. Using DH but tested without it and it didn't have any noticeable effect on the issues. There would also be other rendering errors that simply confuse me, those are attached. Both using Bliss commit #482, unsure if that's relevant. Other issues happen indiscriminate to what shader is applied.
-Computer Specs-
RTX 4080
For a full computer spec issues...
Solution:
It was palladium!

Can not use texture file path with <"> in shader.properties
The mcmeta file path of texture is incorrectly set as
"file_path".mcmeta
.
e.g. When using path like texture.noise = "/lib/textures/noise.png"
, causing java.nio.file.InvalidPathException: Illegal char <"> at index 0: "/lib/textures/noise.png".mcmeta
error....