A lot of what you list is built into the emulation cores and are not just UI features.
For games that don’t use their emulation cores:
They would need to come up with a steam-like injected overlay approach
CRT shaders are probably a no go without engine injection (similar to reshade)
Bezels could maybe work with stacked borderless windows, but again it would be an entirely new approach compared to what they have now
Netplay would also need something new and Hamachi-like and would only work with games that already have LAN support, patching support for online service based multiplayer would likely need per-game implementations
The customisable interface would probably not need any changes at least
Basically they would be building all the tough bits from scratch to do everything you’re suggesting
I literally just found out yesterday you can utilize a virtual second monitor with (some) split screen multiplayer games to stream the “second screen” to a friend, giving you a multiplayer experience that you could previously only have with online connections, having totally separate screens with streaming which blows my mind, and this comes out today rather than having to try to figure out how to set it all up myself. Sick.
You don’t use DirectX on Linux, as it is a windows API.
Instead, you use DXVK or VKD3D which provide DirectX functionality, but while translating the actual GPU calls to Vulkan.
If you have installed the Linux version of Steam (not the windows version inside wine) Steam will handle everything for you after you enable steam play for all titles in settings.
In steam, you can choose a default proton/wine version to use, and also set one for each game in the game properties.
For Heroic, it should install these things automatically, but this may be broken. It wasn’t working for me last I needed it.
Instead, you can use protonUP-QT to download additional versions of wine, which can then be used in Heroic. GE versions should come with DXVK and VKD3D already.
If you need a particular dependency (like vcrun), this can be installed using winetricks/protontricks.
When using protontricks, select the game, then select installing dependencies to the default prefix.
For Heroic, open the settings for a game. There should be a button to access winetricks, from there select default prefix, then install dependencies.
You don’t use DirectX on Linux, as it is a windows API.
But we are talking about wine, so we are using directx and there is even native implementation of directx 9 in mesa called gallium9.
Instead, you use DXVK
Not necessarily. Wine has its own implementation already built in, but it translates to opengl not vulcan (yet). You can even partially use the native directx, but it won’t be very efficient, because wine has to translate more staff.
Hey, I was just thinking… You should get the Ublue guys to try tour project. I think IT aligns greatly with their goals. Bazzite has scripts that install sunshine and everything they do is containerized. Maybe they could ship a script to install GOW.
Well if everything’s working correctly you’d want the desktop itself to stay close to the sdr values but have applications that are HDR capable to make use of it. Otherwise you’re limited to full screen apps making use of it.
My monitor (Acer XV275K P3) has a better MiniLED local dimming algorithm in HDR mode than in SDR, so even SDR content looks better that way. Also it’s annoying having to switch it back and forth, it’s way easier to just leave it in HDR mode and not worry about it.
For the washed-out colors, are you using an Nvidia, Intel, or AMD GPU? If you’re using AMD you need to run kernel 6.8 or later I believe, if you’re using DisplayPort.
I’m not sure why your display lets you adjust contrast in HDR mode, I would just leave it at the default imo.
I’m using all of them sometimes. ^^ Washed out colors are not an issue on AMD anymore as you said it, but on nvidia I can’t seem to fix it. I wonder if this is happening to absolutely everyone, as the arch wiki makes it sound like nvidia 545+ has been reported working…
About the contrast: I wish I could, but I found that the factory default was 70% and it did seem to often cause noticeable dimming because the image was too bright for the max avg luminance. It felt weird and I think it’s because Alienware, like many manufacturers, just can’t resist blasting the consumer with overtuned contrasts to get a purchase out of it.
But why does it end up washing out colors unless I amplify them in kwin? Is just the brightness absolute in nits, but not the color?
The desktop runs in SDR and the color space differs between SDR and HDR, meaning you will end up with washed out colors when you display SDR on HDR as is.
When you increase the slider in KDE, you change the tone mapping but no tone mapping is perfect so you might want to leave it at the default 0% and use the HDR mode only for HDR content. In KDE for example, colors are blown out when you put the color intensity to 100%.
Why does my screen block the brightness control in HDR mode but not contrast? And why does the contrast increase the brightness of highlights, instead of just split midtones towards brighter and darker shades?
In SDR, your display is not sent an absolute value. Meaning you can pick what 100% is, which is your usual brightness slider.
In HDR, your display is sent absolute values. If the content you’re displaying requests a pixel with 1000 nits your display should display exactly 1000 nits if it can.
Not sure about the contrast slider, I never really use it.
Why is truehdr400 supposed to be better in dark rooms than peak1000 mode?
Because 1000 nits is absurdly bright, almost painful to watch in the dark. I still usually use the 1000 mode and turn on a light in the room to compensate.
Why is my average emission capped at 270nits, that seems ridiculously low even for normal SDR screens as comparison.
Display technology limitations. OLED screens can only display the full brightness over a certain area (e.g. 10% for 400 nits and 1% for 1000 nits) before having to dim the screen. That makes the HDR mode mostly unuseable for desktop usage since your screen will dim/brighten when moving large white or black areas around the screen.
OLED screens simply can’t deliver the brightness of other display technologies but their benefits easily make it worth it.
Ah cool, I didn’t know that there are layers of capabilities for different requested brightnesses. Thanks for your in depth reply! I’m also a 1000 nits enjoyer but I don’t switch on any lights - I like when my eyeballs get blasted with colors. 😂
linux_gaming
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.