is it still not possible to do emudeck-style per-game steam entries with steam rom manager?
is it still not possible to do emudeck-style per-game steam entries with steam rom manager?
Ait's the one thing I've been on the lookout for w/ retrodeck
Hits an example, the number doesnt matter for an example 
Ktrue
DGuys which one to choose for my LLGO ? KDE or GNOME?
KThat's user preference, they both work
KIf you want an exact match to steamos, use KDE
DOkay, thanks. I'm determined
KHey I want to creat a symlink of my videos on a separate drive.
is this command correct:
ln -s /var/mnt/adrive/videos /var/home/username ?
or just /home/username ?
is this command correct:
ln -s /var/mnt/adrive/videos /var/home/username ?
or just /home/username ?
K-
nvm, I think /var is the way
nvm, I think /var is the way
Hln -s /var/mnt/adrive/videos /var/home/username/Videos
LYou will see in the patch notes we will release soon, but it will come in a minor update after 0.8.0b as the removal of Yuzu and Citra + ES-DE 3.0 brought major changes and the BoilR dev also have been very busy.
But we hope to have it in something like 0.8.2b or the like.
But we hope to have it in something like 0.8.2b or the like.
F/home is the symlink to /var/home, so both would work well I guess
KThanks. Yes I did it like this, forgot the "Videos" in my first message 
KOh okay
Hhopefully it wont mess up anything for those that already have yuzu and citra added (or have an archived version of them) 
AYouTubeOKestGamer
Full comparison of the ROG ALLY(s) and the MSI Claw 155H. Performance, physical overview, repairability, and other comparisons.
Device info:
ROG ALLY:
-Bios 337
-Driver: 23.20.23.08
MSI CLAW:
-Bios: release bios
-Driver: 31.0.101.5379
00:00 Intro
00:23 Performance comparison
04:59 screen and sound
05:41 Specs
06:31 Physical comparisons
08:1...
Device info:
ROG ALLY:
-Bios 337
-Driver: 23.20.23.08
MSI CLAW:
-Bios: release bios
-Driver: 31.0.101.5379
00:00 Intro
00:23 Performance comparison
04:59 screen and sound
05:41 Specs
06:31 Physical comparisons
08:1...
Aalso turns out the controller is cursed
Ahhd support unlikely
KHoly hell those cyberpunk benchmarks are brutal
Athe oem buttons send WMI events
KHow did they fuck this up so bad
KI still really want to see Linux on it
KSomething tells me there's an Intel driver on windows portion to this
Aimplementing a WMI event listener in the controller 
Awhy
Atdp controls its still unclear if its EC or WMI
Atheres a chance msi did raw ec for it and i aint doing it
KOmg you even have this kernel module 
KI was never able to see the watt usage on my CPU
KI had to rely on zenpower3
Aoh the vent is fake too rip
Ai can listen to wmi events already but just why make it part of the controller you know what i mean
EI have a question
BDo have a question too, would bazzite 40 land on testing or unstable first?
EHow achievable is it to make a Bazzite desktop version with all of the Intel OneAPI drivers and shit overlayed or preinstalled
EOr is it still better to rely on distrobox Ubuntu for this
EOn my current Kinoite install I have Blender flatpak fully working with OneAPI by overlaying all of the Intel OneAPI shit
EBut I don’t think this is the best way to go about it
EBlender is just a way for me to test so I make sure it works with PyTorch and TensorFlow
EAt least at this moment
Aintel one what now
EIntels alternative to CUDA
Awaht can you run on it
ESpecifically for Intel Alchemist architecture GPUs
ETheoretically anything you’d use CUDA or OptiX for
EIn practice not that much since it’s not as widely adopted
AUsually pytorch bundles stuff
A@Kyle Gospo big brain idea time, we take pictures of handhelds running bazzite for the website
Awould be even more big brain if we had stickers
EIntel has released a specific library for PyTorch which requires the system to come installed with the Intel compute runtime and some other shit
