https://www.tsmc.com/english/dedicatedFoundry/technology/pla...
Which is how they could pull the APU shrink off without breaking the bank.
And... Is the OLED not VRR? That was my #1 wish for the original Deck (with #2 being an OLED).
According to LTT it is due to the physical connection. Basically the panel is the same as Switch OLED and thus uses whatever it uses which is MIPI and thus no VRR (need eDP for that). The hardware clearly supports it (just plug an external display with VRR support into the deck and it works)
https://youtu.be/uCVXqoVi6RE?t=179
Basically Valve doesn't do large enough volume to make proper custom display economical so they have to take whatever they can get.
Makes sense. The highest volume OLED with the right size is... the Switch's!
>Basically Valve doesn't do large enough volume to make proper custom display economical so they have to take whatever they can get.
Yeah exactly. I see a lot of online complaints (mostly outside HN) about no new APU or no custom display, but the capital costs of doing either from scratch are just hilariously high.
I think one side of the mother glass has a few extra pixels that you can just not cut off and end up with the 80 pixels more on one direction?
If you start from a panel that cuts perfectly to 8K or 4K TV panels and you keep halving it won't go down evenly to 720p as it is not half of 1080p (1440p is half of 4K and 1080p is half of 1440p so they come out nicely without any wasted panel/pixels by cutting in half)
For what it's worth too, my experience gaming on Wayland has been great from a consistency perspective. Once you dial in settings that work, the only performance blips you can notice are related to shader compilation. 144hz feels like 144hz, which has not always been the case on Linux.
I tried to get my 3090 working in Wayland/KDE/Arch for about a month (after repeatedly running into the same issues on my 2060 laptop) and gave up.
AMD IGP output it is... and I just game on Windows instead. But even then, neutering the leftover bits of the Nvidia driver (which I need for CUDA) that keep breaking electron/chromium is making me pull my hair out. I still hold my breath opening VSCode, wondering if its going to freeze or not.
Try using a dedicated rail or another PSU if you have one.
I have literally all the exact same issues on my RTX 2060 Asus G14 laptop, like:
- GPU rendering broken in Wayland Chromium/Electron, and sometimes Firefox
- Occasional black screen on boot, from some kind of race condition.
- Unpredictable artifacting on the KDE desktop and some apps.
And I still get some of that when Nvidia DRM is disabled and I'm just using the 4900HS/7800X3D for display out. Completely disabling the Nvidia GPU fixes all of it, every single thing, but then I can't use CUDA.
I'm also running everything on NixOS, so assume there's a fair bit of fairy dust blessing the config. Besides enabling modeset and cudatoolkit manually though, I don't think there's much special about my software setup.
If it wasn't for AI, I'd upgrade to AMD right now. But ROCm and the CUDA translation layer don't quite seem to be there yet.
Those are all things you particularly want on the Deck.
But I don't think that's gonna happen until Zen 5, and only if we're lucky and AMD restarts the Van Gogh successors they canceled[1].
1: https://videocardz.com/newz/amd-ryzen-6000-notebook-roadmap-...