Gotcha, makes sense. Yeah my setup is very straightforward

Agreed. Quadlets and podman are amazing.

I hate docker compose and find that much more complicated. It’s a whole other structure that’s essentially unneeded.

But I started with podman and not docker, so that’s probably why

openSUSE MicroOS is amazing

Just want to chime in here to say I use containerized caddy as a reverse proxy with quadlets and did nothing special.

you got this! don’t give up!

thank you, i will try!

what GPU are you using, btw?

lol my man. XD get ALL up in there!

yeah, the menu will never change. that kind of stuff in-game would need to be done by the game devs.

you’d need other tools, like Optiscaler, to tell you that FSR4 is running.

alternatively, you can check the folder where the executable is. you should see this dll there: amdxcffx64.dll

otherwise, if it’s an FSR3 game, if you don’t want to check you can just assume it’s working.

lol it’s really not bad. its bark is worse than its bite. XD

ok, CyP2077. looks like it has FSR3 already, that’s good. so add this launch parameter in steam:

PROTON_FSR4_UPGRADE=1 %COMMAND%

and set it to FSR3 in-game.

that should auto download the FSR4 dll to the game folder and you’ll be good to go. note that the settings in game will still say FSR3, but it will be FSR4, since FSR4 only needs a dll drop-in to update from FSR3.

that will not work with FSR2 games, however.

nice! i just updated to the 9000 series myself! specifically for this reason.

it just has made such great leaps in the realms of FSR and encoding.

i can attest, FSR4 looks incredible. i’m using it on Lies of P, which you just need the parameter for. any game with FSR3 support you only need the parameter.

i’m also using it on Returnal. Returnal only has FSR2, so for games like that, you need some assistance from OptiScaler.

you can scope out my video here as an example if you want to see!

https://vods.198x.eu/w/u72HQH8fVybQ4xsa9t9yyq

optional launch parameters for your game in question.

i’m starting to think it’s the debian base of this container image. it may just be too out of date for my GPU.

thanks! that seems in line with what i’m doing, though my container is rootful.

the container is rootful.

any help is appreciated as i’m at a wall. :/

what i’m so surprised about is that it works for owncast, and the setup is the same.

rootful. render group isn’t named in the container and the owncast user isn’t in the group.

but it works, and peertube doesn’t.

thanks! i took a look and sadly i’ve already covered those parts. :/

this is a great thought and i’m not sure, probably not.

when i examine /dev/dri in the container, it has the groupid that it has on host, but not the name. peertube user is not in that group.

i tried making the render group in the container with the same gid and added peertube to it, but it didn’t change anything. this process may not be correct, however, to achieve that goal.

any suggestions for quadlet on how to bring in the render group and add container peertube user to it?

thanks, i just ended up going with a new image with the components installed.

ooo i see. ok i did not consider that