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.

With what money are they supposed to fight the multi billion dollar mega corpo exactly with dozens of lawyers??

Also, if they fight this in court then that would mean less money for development thus making your experience even worse….

I was just starting to fiddle with the Starr programs so i didn’t realize that the proper way to use it is to sync the torrent clients directly to sonarr and radarr. The issue happened on those programs all the same though. (fixed it already though)

I got it to run, its fairly simple but i am having issues integrating it into the docker compose as it just… stops working… i’ll be looking into it today and tomorrow and if i succeed i’ll report back to you with findings.

yeah, that and other stuff its very hacky. I’ve now done a .env file to keep everything parametrized.

Thats good!! i’m now looking at how to set up caddy to do exactly just just that, then i’ll look at the vpns for outside connections. Thanks gor the advice!

I think you are right! Now that you’ve explained it, it makes sense in my head, as someone else recommended i added hostnames and now i can work with those which makes it nicer, i don´t want to be opening a maze of ports xd

Bingo! This worked. I don’t fully understand why because i expose the ports on the docker containers, i guess i must have something miss-configured. Thanks!!

Version information:

qBit: v4.5.4
prowlarr: 1.7.4.3769

i tried with 127.0.0.1:4666 but i got the same issue

A colleague at work said he was running a Raspberry Pi but in the end had to move to a more powerful system because he needed more power. AFAIK he’s use case is lighter than what i plan so i thought it wasn’t a viable solution. What you describe sounds very nice, especially because of the price of the Pi.

Would love to hear more people’s experiences with this setup.

Thank you for the comprehensive answer! I can see that storage is going to be a big issue here for all the media, I’ve been recommended in this thread to go for a NAS but their low RAM/high cost plus having to use their proprietary software is holding me back. Is a mini PC attached to a HDD enclosure a good solution? Won’t the USB speed be too slow or that isn’t an issue for a media server and the other utilities (I’m more focused on the media server as I am assuming that is the more taxing use case)

My worries with a NAS is their very small RAM (on NAS of reasonable price). When running several docker containers i fear that might be an issue if suddenly several *arr are downloading, pihole, tailgate… all running at the same time might mean that the NAS with 1GB (and t these are already expensive, most I’ve seen more on my budget are half of that) of memory might not be enough (i think).