@ScrunchGumpgins@ahumeniy@SadlyItsBradley the drivers support burning perfectly fine, it's just a matter of using something like Brasero (on flathub) or cdrdao... installing authoring software wasn't unusual even back in the day
@jxstfeli many qcom drivers and firmware bits were written for previous SoCs and continued getting expanded with additional support for newer SoCs (while keeping their old names)... so there's no immediate indication that this would mean they used a different headset with XR2 <.<
Valve is working on a Frame OLED:
- 3552×3840 up to 90Hz (similar to those on the Galaxy XR)
- same SoC as Frame LCD
- renders at half res (1776×1920) to hit the same perf as LCD with an option for "Foveated Scaling" to show the UI at native res
more at:
https://t.co/ot1tAzdynr
@SadlyItsBradley uhhh... they're just updating from one LTS kernel to the upcoming one, Valve's patchset is the same between both... so there really isn't nothing to expect here other than generic bug fixes
@josethevrtech Valve is using foveated scaling, so there really isn't a need to send an entire full-resolution frame with each screen refresh; the Sony OLED panel can scale/combine chunks of the video together, so only the specific area that the user is gazing gets drawn at full resolution
@CoolDuel24 120Hz is considered an experimental feature (the Sony panels used in these prototypes have to be overclocked to achieve that speed), but it will very likely be available as an option in SteamVR once the final version of Deck OLED ships
On "Foveated Scaling", the Frame's Snapdragon 8 Gen 3 does not have the bandwidth to drive 3552x3840 OLED panels at 90Hz, so Foveated Scaling is a hardware workaround that gives perception of full resolution while retaining their 90Hz performance target
@Sezamn_@jimkoutso2008 emulators are definitely an edge-case for driver conformancy, regular games are far more forgiving, plus the good thing is that in either case it doesn't crash :)
@valeradx @valerieslop @QuantumV3 it'd be better to say that nvk is the Vulkan abstraction layer that generates commands that an NVIDIA GPU would expect, while nova is what actually resides in the kernel and sets up hardware/queues up commands from nvk... nvk works with either nouveau or nova as the kernel driver
@jimkoutso2008 for context, Valve started including the open source nvk driver with SteamOS as of a few days ago; this is after the announcement that they're working on NVIDIA support in the background, and it seems that they are indeed making good on that promise
@OyasumiBastet@jimkoutso2008 yea, it's very much in the realm of a technology demo; the desktop works great but games absolutely need a ton of work (and tuning) before it's ready for prime time
@pixel_brush@jimkoutso2008 the 3.9.x image data is up on https://t.co/aUPD8kO4GV, but if you just wanna try it on an internal/external SSD, then write https://t.co/W2WMXWF7i6 with rufus or dd or win32imager to a drive and boot it, pretty simple