It's plenty fine, but you don't need the G version of the 5700. You'll be fine with no iGPU - get ei
It's plenty fine, but you don't need the G version of the 5700. You'll be fine with no iGPU - get either the 5700X or the 5600X depending on budget
SI tinkered with that a bit last night on the Deck, as well. Dropped the resolution down and turned on the Deck’s NIS scaling and it actually looked shockingly good. I don’t know if we’ve got NIS scaling in Bazzite or how to access it if we do, but it’s not a bad place to start. Even FSR1 with Proton-GE probably wouldn’t go wrong
GAnd yeah, like others have said, you will never reach the 16 GB VRAM threshold at non 4k resolutions, unless you're doing compute on the GPU
Aso you saying i should disable igpu and let dgpu run games and desktop and gamescope steam thing
Syes
GThere really is no point in using the iGPU if you have a dedicated card
BI've had these wayland crashes occasionally lately, with or without streaming. Mostly in desktop mode. Once just copying a link to clipboard
CTrouble is the game only supports dlss and I haven't figured out the mods to replace that
SOh yeah, I definitely meant applying some external form of upscaling. You can enable FSR1 by running it with Proton-GE rather than Proton Experimental (I don't actually know if Proton Experimental has it baked in now, it's been a while), then using
WINE_FULLSCREEN_FSR=1 %command% in the launch options on SteamSActually apparently FSR is enabled by default with Proton-GE? Just have to set the resolution to something lower than your native screen res. Huh
C
SI'm getting conflicting information. A patch note from GE 6 months ago says it was enabled by default but the Repo's Readme states you toggle it on. I'm trying to find out LOL
SAh ha, it was related to a bug with one game (Halo Infinite). That's been resolved and FSR is off by default and toggled with
WINE_FULLSCREEN_FSR=1 in the launch options againCAhhh interesting
CI'll see what I can do after I take care of a bunch of morning prep stuff 
CPossibly, depends of the GPU, the 5700G uses PCI E 3.0 instead of 4.0 and loses some stuff, BTW, get the 5600G, the 5700G is a waste of money, is just a slightly overclocker 5600G
LHow do I manually update bazzite since mine doesnt do so automatically as it says it fails the checks?
LAnd how do I see what version of bazzite i currently have?
Tjust updateTrpm-ostree status
CYou could at one time! In their initial APU wacky days, you could pair an A8 or A10 with a kinda low end HD 7000 series and enable a kind of crossfire which would do exactly that, heavy tasks to the dgpu, small tasks to the igpu, of course this only lasted one generation and then was retired, cool stuff tho
CDepends if my guy has the money to buy everything at once, if he doesnt have a GPU available, then it would make sense to go first for an APU first
Lthanks, well it seems its failing the update because of the secure boot thing, "Recipe
" "sudo mokutil --import /etc/pki/akmods/certs/akmods-ublue.der --timeout -1
"
enroll-secure-boot-key failed on line 41 with exit code 255" "sudo mokutil --import /etc/pki/akmods/certs/akmods-ublue.der --timeout -1
"
Tah. I don't use secure boot, so I can't help with that
Lwell, I only ran it because of this message in the terminal "Warning: The next major update for Bazzite will introduce new requirements for secure boot to work.
Please make sure to run "ujust enroll-secure-boot-key" at least once.
"
Please make sure to run "ujust enroll-secure-boot-key" at least once.
"
GIt does depend, but I think it's pretty clear he wants to go for the GPU with the build
CYeah but if you dont have the money to buy everything at once, well
GI'm mainly just discouraging it for the purpose of "I want to run the iGPU and dGPU at the same time"
CIf you have enrolled it already it should be gucci
Ci got the same error, because the key was already enrolled
Kthat message appears no matter your hardware or state
Kit's there to make sure people were informed of the change for that week
Konce you update it'll be gone
Loh thank you
Lso how do i tell if something has gone wrong, as i entered "just update" then i see
Starting the ublue-update service, and its just hung like that in the terminal ever since
Starting the ublue-update service, and its just hung like that in the terminal ever since
KYou can run
rpm-ostree update instead to see a more verbose updateKThe release you're updating to majorly improves just update and adds an app for it as well
Loh nice
Lso is it possibly just taking a while to update then i suppose and not actually borked
KIt's downloading the next update, could take 20 plus minutes depending on your internet
Lah i see
Lthank you
KNo problem
Lwhat am I doing wrong with this? I installed the update and tried installing a recipe and got this: error: Justfile does not contain recipe
fix-steam-download-speed.Lit doesnt seem to contain any of the recipes
Tare you using
ujustjust
Lujust
Ljust doesnt work with it either
RAny reason why on install deployment started hasn’t moved for ten mins ?
RAlly:latest
