| Age | Commit message (Collapse) | Author |
|---|
|
[skip ci]
|
|
|
|
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++.
|
|
xorg aka x11 drivers
adding the Variable fixes issues on devices like Steam deck. Hope that this can be removed in te future when the linux build has no issues when build with wayland. (building Wayland version seams to have only 2 small bugs)
|
|
added exit to run-client because it has no reason to run after starbound is started
|
|
|
|
Check if user already has set any of the variables to avoid overwriting them
|
|
zink check now uses all environment variables for check and only use one export function
|
|
|
|
|
|
Added Vulkan support check befor looking for Zink support
|
|
If your system supports the Zink driver, you can use it for OpenGL rendering by switching to the Vulkan backend. This can improve performance.
|
|
|
|
|
|
|
|
[skip ci]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|