It should be non-Spain but ok i guess, lets keep letting the rich countries in EU destroy our chance at a home…… (which i assume by fare are the most prevalent)

Bingo, yes this is the same issue for what they say. I am connected through DisplayPort though on all my screens. Shame that it is not being worked on but from my testing I assume that when steam moves proton to support wayland natively it will be fixed. Thanks for the info, very interesting!!

Its one of those stylized games where i can not choose resolution, only fullscreen or borderless. And when i choose borderless the screen goes to a small 1080p window.

Thanks for the input! I tried it but no luck, the black blocks are still there and it still renders on 16:9. Thanks though!!

Yes i read that in the documentation but for some unkown reason if i omit either the lowercase or the uppercase the game won’t even start! Only the gamescope instance.

I’m running with the mesa drivers on version Mesa 24.2.0-devel. After some tinkering around it seems its a combination of things and gamescope fixes the black blocks but it still won’t render in ultrawide, so I’ll just stick with wine and lutris for now which seems to work fine.

Thanks for the help!!

I think you are correct assuming it’s an issue with proton not supporting wayland as if i try to use lutris proton still doesn’t work but wine does and so does with gamescope.

I’m trying to use gamescope now as you and the other comment have mentioned but I’m having the issue with this command, if you could help me:

gamescope -w 3440 -h 1440 -W 3440 -H 1440 %command%

It creates a window of the appropriate size but the game is still in 16:9 (Without the black blocks issue, which is already a win, but i’d prefer it to be ultrawide too).

Thanks for the help!!

EDIT: Just tried it with Lutris but it seems to also not work even with their setup on proton. So it might be a them thing. For now I’ll just use lutris to play on wine directly.

Yeah after seeing this and another very detail answer it looks line my settings are too demanding and that is causing a slowdown. Since i do direct playing on everything i might just turn them down for the one friend who seems to be always on the weirdest player that needs transcoding. Thanks all!!

I don’t know where you’ve bought your N100 but i think it shouldn’t be able to do that. I have one too and it cant do even one 4k 10bit HDR transcode.

As i see in the results from the benchmarks we’ve gathered (here: https://gist.github.com/ironicbadger/5da9b321acbe6b6b53070437023b844d), my experience seems to be the common one.

While de N100 is a great value and low energy processor for a jellyfin server (especially if you direct play everything as is my case), I think if the objective is 4k hdr 10bit it will fall short as in my experience it usually transcodes at 8-9fps.

Seems to have the same issues as the other software. After digging for a while seems that AMD changed the way their driver works for RDN3 cards and the zero rpm “feature” is not exposed yet to the kernel. There are some issues tracking progress but as far as i can tell AMD isn’t prioritizing the issue so who knows when this will be fixed…

In one of the gh issues someone fixed it by bypassing the vrm connector directly to the motherboard. In their model it was doable without having to disassemble anything. I don’t feel comfortable doing that so for now the only thing to do is wait…

Thanks anyways though!!