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.
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.
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
Maybe, depending upon how it is implemented.
If they somehow use those AMD NPU’s as accelerators to handle spatial recognition, then it might be possible to at least add some of the needed functionality behind AR/VR without pounding the APU.
Or, considering it might be ARM, it might be an in-house or even AMD designed SoC with all the necessary bells and whistles to implement at the very least AR.
I’d buy the heck out of an AMD ARM device.
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.
Its gonna be ARM based
Doubtful. Emulation of x86 code is just too slow. I’d rather expect hybrid SoC, with both ARM cores and x86. System and dedicated games can run natively on ARM, while legacy software may utilize x86
This seems like it would put the price far out of reach.
I don’t know - you’d need at least 4 arm cores, and 4 x86. Current deck uses just 4 x86, so squeezing in more would require waiting for some fabrication improvement to keep power draw and cost sane
That just seems like at least double the cost.
Not necessarily. Steam Deck SoC is CPU+GPU out of which latter is probably the bigger part. Also, on the chip there are all the memory, USB, Pcie, audio and other controllers.
Adding 4 arm cores definetly wouldn’t double the chip size
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.
I imagine would be awful. Would two kernels have to run on the same machine?
Correct me if I’m wrong, but afaik, applications talk through APIs. It shouldn’t matter if app runs x86 and kernel is ARM
But the code that loads other code (launches an app, switches to it, etc) needs to be running on the same CPU, afaik.
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.
