DON’T RUSH IT.
Fuck’s sake.
The current deck is more than enough to handle most games today. There is no reason to rush the next one out. Let the technology simmer for a while, reduce a little. Turn into a fantastic lightweight little belt buckle that connects to a pair of AR glasses and tracks my hand movements so I can play without holding a controller or mouse/keyboard anywhere I want.
Asking for a handheld the performance necessary to run a VR headset is too much
Quest is doing it with less power than a current Steam Deck.
I ran Alyx with a WMR headset and a mobile 1060. It wasn’t fantastic but it ran well enough that the experience wasn’t diminished. A next gen Deck could easily handle it
You’re incorrect, and that’s okay. We’re talking about some future date where technology that doesn’t exist today is available. We can ask for anything we want.
Even the different problems between the LCD and OLED models make me content for valve to take it slow.
Don’t diminish the support with multiple sku’s, work on fixing the small but persistent problems with the current operating system, let other companies keep the hardware manufacturers pushing forward, continue making sure the operating system works well on the more modern hardware, and release a single product when the time is right.
There should be no decimal after the deck 2, keep the product focused, don’t divide your labor and multiply your potential bugs.
Also please have your operating system developers try using the deck interface for things besides gaming, trading, forum posting and even browsing the store is hampered by easily replicable bugs.
Its gonna be ARM based. Just no other way to get the power to performance. Maybe some of the AMD architectures. Also, expect soldered RAM.
people overexagerate the power efficiency of arm because of controlled environments. for gaming handheld workloads x86 is more than enough.
Snapdragon on windows has already shown(ignoring games that outright dont work) then when under a gaming load, the efficiency gains arent there.
Another example that its not a magic bullet in terms of strictly hardware is the M1 in non OSX environments. If you look at the M1’s efficiency while using Asahi Linux (a distro of linux specifically tailored to apple m series cpus), it does not remotely get the same kind of battery life as it does in OSX. Its why for example, the steam decks battery lofe reletive to size is better than windows handhelds.the bottleneck wasnt the hardware but more the OS
what valve really wants is if they could get a handheld with only AMD C cores (that is power efficient cores with less cache but like 70% of the size of a full core) such that the power budget would go to the iGPU more than the CPU, as a majority of games are gpu limited in performance rather than CPU. AMD just has never made a C core only consumer part (only servers have gotten them).
Wouldn’t that be the point of focusing on the interoperability layers and recent investment in Arch?
it does not remotely get the same kind of battery life as it does in OSX
Yeah exactly. So you need to invest into finding the fixes to that. Which is what Valve appears to be doing? It might be a fishing expedition or just a virtue signal to the foss world, sure. But they did do the thing.
And yes on AMD. I did leave that window for myself to crawl out through. I think if the trip down ARM on Arch ends up being a fishing expedition, they flip over to a known quantity for a refresh.
their investments is into a later for x64 to arm cpu translations, but still does not settle the problem that the gpus on arm based systems still have soo little development into games, which would then limit your options to amd, intel and nvidia based arm designs if you wanted an SOC with existing GPU support already in the environment. the moment you choose to have a tiled approach of mixing cpu and gpu from companies, you sort of instantly throw away the efficiency gains from switching to arm in the first place.
AMD and intel basically havent pushed out an atm based device yet, and Nvidia notoriously hates doing semi custom designs for clients.
personally i think youre far more likely to see the arm compatibility layer for basic pcvr games on a theoretical index 2 before a steam deck uses arm.
I wouldn’t sound so sure. There are a lot of blockers to getting a working ARM based steam deck. First Arch Linux (which steam os is based on) does not offer official ARM binaries. This would mean they would need a new base os or work on getting Arch Linux to support ARM. With their recent donations to Arch Linux were focused on unblocking some issues with supporting Arch on ARM (notibally stuff needed for better automated builds) would suggest they want to stick with Arch.
Next you need good emulation layers for x64 and x86 as that is what all games are written in. Which there are leaks that say they are working on this as well.
But that is two big blockers that could take years to solve. So all comes down to when they want to release the next deck. Within a couple of years and I don’t think it will be arm based. After that the chances go up quite a bit.
With their recent donations to Arch Linux were focused on unblocking some issues with supporting Arch on ARM (notibally stuff needed for better automated builds) would suggest they want to stick with Arch.
Next you need good emulation layers for x64 and x86 as that is what all games are written in. Which there are leaks that say they are working on this as well.
Thats two legs of support for an ARM architecture.
But that is two big blockers that could take years to solve.
Sure. But what you are describing is “uncertainty”. Uncertainty in isolation isn’t a form of evidence. It could take years. It could not. Its not just Valve looking to solve this issue. MS has committed to ARM based interoperability; so has Apple. MS and Apple obviously want things to work seamlessly between ARM and x64, x86. The heat/ power to performance gains are just too much to leave on the table and both of those Software/ Hardware manufacturers saw this coming. If this was a project coming out of Valve & Arch doing the work; sure, I’d give it a time line of a couple to several years. But Valve while coming in with backing and there are other players looking to overcome and address the same problem. With teams like MS and Apple also working on it, I expect this to be figured out on a faster timeline. Months/ few years.
Within a couple of years and I don’t think it will be arm based.
Sure. If thats your bet thats your bet. My bet is solidly on ARM. Its what the evidence we have points at, even if there isn’t a ton of certainty around it.
With teams like MS and Apple also working on it, I expect this to be figured out on a faster timeline. Months/ few years.
That assumes they will share a meaningful amount of work. I do not see what Apple have done to help much at all - completely closed ecosystem with their own custom chips that they are not going to want to share.
MS have done a really bad job as well at getting ARM to kick off and have not been putting a huge effort into it that I have seen. And especially since valve is doing this in part to get away from MS systems why would MS help valve with this goal?
So yeah, if they did put in and share the effort it would take less time. But I don’t see them doing that. Plus, it takes years to develop a product like this. And all evidence ATM suggests they have barely if at all started on the next version. Which does suggest that the next deck is likely more than a year away, likely two. Which does increase the chances that it could be arm based.
Removed by mod
This seems like it would put the price far out of reach.
Removed by mod
That just seems like at least double the cost.
Removed by mod
That sounds like a nightmare to code for.
That the kernel developers to decide, the deve wouldn’t need to change angthingz but i doubt the idea too, how can sincronize the arm and x86? How to you handle libraries of the different architectures
The libraries would probably be easy. We’ve already got x86 and amd64 libraries on the same machine, but the kernel I imagine would be awful. Would two kernels have to run on the same machine? What about memory access? What about the scheduler? Would it really be more efficient than emulation? For every x86 instruction, there is either an equivalent instruction or an equivalent set of instructions for ARM.
Removed by mod
But the code that loads other code (launches an app, switches to it, etc) needs to be running on the same CPU, afaik.
I think Intel’s Lunar Lake has shown otherwise, it’s quite good.
And ARM performance per watt isn’t going to be as good when you’re doing x86/x64 emulation
Obviously anecdotal, but if the next Steam deck was Intel based, I wouldn’t buy it.
I’m just citing Intel’s Lunar Lake as an example. If Intel can do it then so can AMD, and eventually both companies will surpass that
ARM isn’t exactly efficient when used for performance-demanding things. It excels a low power efficiency, but as soon as you throw a persistent heavy process at it, it’ll gulp down a battery all the same.
And x86 has been catching up on both sides. Standby times are only getting better.
If the hardware can ever be shrunk enough to make even a semi-pocketable x86 handheld, I would be happy if Valve were ever to release a “Steam Deck Mini” or something.
Or maybe their new efforts with ARM support point toward a future of a much more portable Steam-on-Linux-on-ARM device.
