Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
You can ask on the Minecraft forums.
Steam Deck forum... https://steamcommunity.com/app/1675200/discussions/
You should be able to grab the latest version (8.4) of the Prism Launcher through the Arch User Repository on the Steam Deck.
I assume you have Java updated to the correct version as well?
Shaders are not supported by Minecraft without mods, so they depend on a mod to load them. Therefore, the problem is likely with the mod you use.
Generally people use either Optifine or Iris.
Optifine can work without a modloader, but generally people use a specific modloader so that they don't modify Minecraft's core to achieve shaders.
And so yeah the various setups may matter on how you achieve shaders.
Minecraft -> Forge Modloader -> Optifine -> shaderpack
Minecraft -> Fabric Modloader -> Iris -> shaderpack
(just to name examples)
Prism is just a minecraft gamelauncher, right? It doesn't do more than just 'start minecraft', so it's really the mod loading the shaders that seem to have issues.
Anyway yeah-- the point being, its too little information.
Unless you're suggesting that a Steam Deck update caused graphics to no longer work, I don't see how it matters.
Minecraft runs in Java. Java can be run on anything, even your phone.
I suspect it was a Steam Deck update, yes. Here's why:
I've been running Iris since it first supported shaders. I was using SEUS PTGI. It worked. I've developed a high-resolution resource pack. It looked great and ran great on the Deck. I had a 1.19.3 instance that I used for a long time, until I was convinced to shift to 1.20.1. That I also got working and used it for a long time, didn't keep up with Minecraft updates. If it ain't broke, don't fix it.
But then it broke. I didn't change anything, just ran the game like normal. But when entering the world, the screen split into two big flickering triangles and the world was unviewable. I had to disable shaders to keep playing my world. I waited for a couple of weeks for whatever was changed to get updated, but whenever I enabled shaders it did the same flickering screen.
So I got desperate and started messing with stuff. I've upgraded MC to 1.21, and of course had to update the java version. It runs, but not with shaders. Same problem as described. I've created fresh instances with just Iris and Sodium, fabric loader, with the same result. I've loaded BSL shaders through the Prism menu, does the same as SEUS.
I had an idea recently to run that 1.19.3 instance, which worked the last time I ran it. I've modified nothing with it. The only difference is Prism has updated multiple times, and SteamOS Discovery updates occur regularly. I half-expected that instance to work, but it does the same thing as all the others. When entering the world, nothing can be seen. If I disable shaders, it's playable.
One potential culprit is file permissions. I have a problem with Prism that others have reported, where when I click on any of the 'open folder' buttons, nothing happens. The only person who tried to help me with that suggested a program called flatseal that can edit Prism permissions. I already had it set up the way the guy suggested. He said it was SteamOS weirdness or something, had no suggestion.
I see. https://github.com/PrismLauncher/PrismLauncher/issues/2624
According to your thread there, the problem started occuring at aroundhalf way June or before.
I have been scrolling through the news on what officially changed on Steam Deck, and I found one that does mess with shaders---
Do you think this update caused it?
https://steamcommunity.com/games/1675200/announcements/detail/6851744408518855772?snr=2___
If so, it may indeed be caused by Steam's way of "fixing" that issue. You should try to contact the Steam Deck development team about it.
And, if they don't plan on looking at it, maybe report the issue here:
https://github.com/IrisShaders/Iris/issues?page=1&q=is%3Aissue+is%3Aopen
...
I can't find any related bug report on the official Steam Deck hub:
https://steamcommunity.com/app/1675200/discussions/1/