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.
that’s fine for now. Mullvad is very affordable though.
it’s not easy. but unfortunately both states are captured. no one else is coming to save them.
so either the populace rises up as one, or they continue to be abused.
i don’t think either population has their heart in it anymore.
yeah, because that’s what Putin wants?
let us know when you come back to reality.
best? i dunno about that. it was an option, tho.
i prefer Photon, or just the default.
this. and incredibly sane defaults. for me, basically the perfect “traditional” distro and it ended my distrohopping.
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!
great thoughts, thank you for sharing! i’m still quite new to containerization.
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?
understood. this is the route i ended up taking. thank you!
thanks, i just ended up going with a new image with the components installed.
ooo i see. ok i did not consider that
sure, jan.