https://komodostation.com/

Komodo Steam Deck Store rebranded to Komodo Station today. Which to me indicates that Valve’s distributor in Asia is already ready to begin selling more types of hardware. So that’s at least a positive sign.

https://github.com/FEX-Emu/FEX

My understanding is that FEX + Proton is the plan and just double up on the translations as appropriate.

Valve has supposedly just been heavily investing in fex.

Steam deck highlights that Windows -> SteamOS translation is good enough.

I’ve use my Index on Bazzite successfully with no issues, so I’m confident in SteamOS VR capabilities.

ARM-based is the only wildcard, but if fex works, then that’s not an issue either.

Then just onboard compute performance is the only factor. But like you said, even if this winds up only being a “stream everything, its a wireless index,” then I’m already excited.

There is an optional accessory for knuckle straps for these, mentioned in some of the 3rd party reviews.

Which somewhat implies the ability for custom knuckle straps and other accessories as well since they are detachable with mount points.

edit: screenshots from the LTT coverage:

And it is recognized in game by comparing the steam user ID of the other players on the server. Which means if someone else spoofs their name it won’t work. But if real Garry is there, achievement confirming it is him

Not detecting case fans sounds like it would be not communicating with the motherboard properly. Unfortunately every specific motherboard is going to have it’s own unique set of constraints. But generally this is all handled through “it87” i believe? But it87 can sometimes take some nonstandard params.

Here’s an example gist of instructions for getting things working on one specific motherboard. https://gist.github.com/bakman2/e801f342aaa7cade62d7bd54fd3eabd8

The wifi7 on my motherboard causes kernel panics pretty regularly, and the RGB isn’t properly exposed so I cant control(/turn off) any of the lights. Usually these things work themselves out with time as drivers for the new/nonstandard chips make their way into the kernel/libraries.

Yeah. In college world, one needs to be prepared for the school to not care at all and declare that it is the student’s responsibility to make sure any required software runs on their machine. And college can be a hectic stressful time, so finding time to be able to get things working on Linux may not be worth it. Having the Windows escape hatch ready is very important to be able to not lose your mind while on a deadline.

I’m not raging and I’m not even saying that Debian is bad. I’ve just been told MANY times over the years (including on Lemmy), when I’ve commented about bugs and issues I’ve had on Debian, that stability doesn’t mean “without bugs, always upright” it means “not moving, not changing.”

Debian has a very specific use case. And when people say Debian is stable they mean the base platform isn’t going to change under you and suddenly a config file doesn’t work anymore because Package v2.0 uses a different format.

This is good for people who want a low maintenance system that won’t unexpectedly break due to a random Windows update.

This is good for probably the vast majority of people that fall under “normal” computing habits. If there was a major groundbreaking bug that affected everyone, it probably would have been caught in testing.

This is not good for people who have quirky computing needs or otherwise do things in slightly niche ways, IF a bug shows up. Some bugs are minor annoyances, some require different workflows to get around.

But ultimately, people should know that if they are experiencing an issue with Debian, and it’s not just a configuration issue, they either need to have a solution for themselves (recompiling), or switch distros.

I personally stopped using Debian for my desktop around linux 3.16 days, but I do still use it for my home servers (where I don’t want to be updating things constantly). If Debian works as a desktop platform for you, that’s awesome.

But OP was having issues with Debian. So OP should know that due to Debian’s unchanging nature, it will be quite a while before things start working. And they shouldn’t expect otherwise. And that’s ok, their use case is going to just be a bit more bleeding edge.

Ok? “You only have to wait a few months for this crash to be resolved.” still doesn’t resolve people’s issues.

“Fix playing of custom alarm sounds” doesn’t sound like a severe issue to you, but it was also something that if someone needed, they were forced to wait a few months.

Debian would rather have broken custom alarm sounds for several months, even if it was fixed earlier. Fixing a bug to me lands closer to a security issue than “shipping bleeding edge feature sets”.

It ultimately means if something you need is broken for a non-security reason, it is not being fixed until the next point release. There is a fixed unit of time in which you know your problem will not be resolved.

Packages are individually updated for security fixes. Individual packages are NOT updated for bugfixes.

I’ve been told plenty of times that when I had bugs that weren’t getting fixed that “stability means no unexpected changes, not uptime, compile the package yourself if you need it fixed.”

There are plenty of examples of upstream projects asking debian to not package their stuff because they get bug reports for things that were fixed months ago.

Debian does not ship bugfixes. Debian only ships security fixes.

If something works, it’s not going to break. But if something doesn’t work, it’s not going to unless you fix it yourself by going outside of the official packages.

Also worth noting that Debian’s definition of “stability” doesn’t mean “doesn’t crash” even in the slightest. It means “doesn’t change.” That means not changing broken software to be newer working software.

Any non-security bug that exists will stay because new software only ships for backported security updates. So if you have a crashing issue, Debian has no interest in fixing it until the next release. Unchanging is more important than working.

If you don’t have any crashes or bugs popping up, Debian is great, because it won’t introduce crashes or bugs. Nothing unexpected will happen.

By Debian’s definition, the Titanic is now VERY stable, unmoving at the bottom of the ocean.

Well sorry. If it works for glxgears there is probably some other weird interaction happening with Steam + Gamescope + Game launching. (you could try to add glxgears as a non steam game to further push the boundaries of if anything will run from steam).

I don’t have an nvidia GPU so I couldn’t even possibly comment on the state of that situation, but I wish you the best of luck.

Out of curiosity, what happens if you try to run gamescope from the terminal to just run anything (not even having proton in the mix).

For example:

gamescope -f -W 2560 -H 1440 -r 144 --force-grab-cursor --mangoapp – glxgears

If this doesn’t run, you should get some log lines at least to let you know whats on fire with gamescope.

I feel like “Japanese games” is pretty vague. Square Enix and Fromsoft are some of the largest Japanese studios out there and their games work great on Linux.

This lightning talk requires running SteamVR for the room setup bits, and it recommends a few things in the name of “user friendliness” that I would otherwise not suggest (Ubuntu bad, Gnome bad, etc). (edit: so switching to Monado wouldn’t really help since it would require SteamVR working in the first place, and if SteamVR works… OP could just use SteamVR)

But it does show a lot of problems and solutions and things to try along the way.

Based on https://db.vronlinux.org/ (which is like protondb for VR, kinda), monado works better for VRChat, but otherwise SteamVR should honestly work just fine.

Is your issue getting it to start at all, or performance issues?

For me it wouldnt start at all in the default big picture mode and would only start in desktop mode.

I made a few tweaks to get performance tuned up when I was on the Vega64, but I don’t remember what all I did there.

edit: Also, I’m the KDE desktop (i wanted my HTPC/VRPC to be as steamdeck similar as possible, and also I have strong anti gnome feelings).

Yeah. Valve Index.

I originally got it working on a Ryzen 1700, and Vega64. But Vega64 is old GCN architecture and it performed poorly.

I have since upgraded the VR setup to Ryzen 5950x and Radeon 6900xt, and it works quite well. I just played an hour of Beat Saber actually.

Interesting. I use Bazzite for my SteamVR setup. Though I do have to swap to desktop mode for VR, otherwise works great (I have a steamdeck build installed because HTPC, so it boots to big picture, but the desktop mode still works).

Unfortunately that is the target frame rate for steam deck most of the time.

So runs like crap is more like “runs as intended”

Sure.you figure out which parts to scale when.

But point being that it quickly pivots into automating away tasks you were previously doing by hand.