diff options
| author | grbr404 <166065505+grbr404@users.noreply.github.com> | 2025-05-24 13:22:02 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-05-24 13:22:02 +0200 |
| commit | 2d4bc2ef30a25826fdd933020aa3b862ff5d9205 (patch) | |
| tree | c6e8aace80c273f640770d97e394c8b7d16e53a1 /source/core/StarNetElementGroup.hpp | |
| parent | 1eac38c5526f6d4deee811e9995ed5579cdda46c (diff) | |
revert zink adition
Why?
After testing extensively, setting LIBGLE_KOPPER_DRI2=1 resolves the issue with devices like the Steam Deck. These devices have specific drivers that break when using Zink with DRI3, causing the driver to attempt to load and fail repeatedly.
By not using DRI3, most of Zink's performance advantages are undone, so fixing this issue preserves the majority of Zink's performance benefits.
I think the best approach would be to make Zink an additional setting, allowing users to choose whether to use it. This is because we can't predict if a user's device has a driver that breaks Zink with DRI3. Additionally, we could add another setting for DRI2 for users who want to use Zink on their device even if it doesn't support Zink + DRI3.
I don't think that I'm going to be able to implement it due to my lack of experience in C/C++.
Diffstat (limited to 'source/core/StarNetElementGroup.hpp')
0 files changed, 0 insertions, 0 deletions