MMesa stable has not been touched in a few weeks but Mesa-Vulkan gets built from git more regularly
Awhatever bazzite is doing, it's overall been less buggy on the LGO than nobara right now.
there's currently a nasty bug where after several suspend-resume cycles in gamescope-session, the LGO screen starts flashing white and basically is unusable unless you reboot.
all the bug reports I've seen for the issue have been for nobara or arch, none for bazzite yet.
edit: i've done some investigating for the flashing screen bug, but have had no leads yet.
there's currently a nasty bug where after several suspend-resume cycles in gamescope-session, the LGO screen starts flashing white and basically is unusable unless you reboot.
all the bug reports I've seen for the issue have been for nobara or arch, none for bazzite yet.
edit: i've done some investigating for the flashing screen bug, but have had no leads yet.
Abut for this specific game, I could see mesa being related
JWould bazzite work on a MacBook Pro?
MI just know that our combo worked well enough for other devs to ask wtf we were using
Jone using integrated intel graphics
Mfor p3r specifically
Ayeah, let me try p3r in gamescope-session with nobara on my LGO
Aand see what happens
MI’d fully update first via konsole just to be safe,
nobara-sync cliMor nobara-sync in TTY
Ahrm, turns out i don't have a nobara ssd on hand, time to install it onto a spare drive
Mhttps://github.com/Nobara-Project/rpm-sources/tree/main/baseos/mesa-vulkan-drivers yeah our Mesa-Vulkan got a bump 2 days ago
GitHub
Contains patches, configs, and RPM spec sheets for Nobara's packages - Nobara-Project/rpm-sources
M
Mmy guess is it’s one of the more recent commits behind the difference since this is a deck verified title
MI was told Mesa 24.0 is a substantial improvement across the board for P3R specifically so maybe these Vulkan commits are a part of that. We’re on 23.3.3 I think.
AI wonder why p3r works in desktop mode on the LGO. just not in gamescope session 
MI’ve had Vulkan issues with RPCS3 before that presented the same way
MThis was months ago though
MDesktop would work, game mode would crash with a Vulkan error
Aproton logs unfortunately weren't particularly helpful when i checked them
Myeah more than likely it would be gpu logs of some sort. No clue if/how Mesa keeps track of that stuff tbh. I’m just reporting what I’ve heard from people with way more knowledge about this stuff than me.
Alooking on protondb, it looks like while most people aren't having issues, there's a few outliers that are also running into similar crashing
Alol yeah, i have no idea on mesa stuff
Mit’s a shame there’s a couple of locations that run like dogshit because of the ray tracing but overall I think it makes quite a nice improvement in many scenes without too much of a performance hit
Mlike the battle effects and such are all noticeably ray traced but run very well for me
Mit’s just that fucking mall lol
Awith game mode? or just the desktop build?
Asince i think desktop bazzite would probably work fine
Abut game mode might be iffy
Atime to wait for nobara to finish installing on the LGO
MDepends on the weather and how your system is feeling that day
TWould this be something that will update with baxzite then? Everything been great so far except this now I gotta boot back into windows
Ayou could just play it in desktop mode
Anot great, but might be easier than a full reboot
Ai got p3 reload working in desktop mode with no fiddling
Ait was game mode where it's crashing
Awas it crashing for you in both?
THaven't tried desktop I'll do that rn
THow do you manage tdp tho
Aif you want to do tdp control via plugin still, open bpm in desktop mode
Atbh, bpm in desktop mode is not great
Asince it often doesn't overlay on top of games correctly, etc
TOh wow yeah game works fine in desktop
TSo weird
Ayep, i have no idea why
Ayou could map a back button to alt tab or something
Aand alt tab back and forth between bpm and the game
TYeah I'll try something. Thanks for the work around
TCould I run nested desktop and this
