Ok, let’s talk frame times first:

1s / 90Hz = 11ms

1s / 60Hz = 16ms

1s / 45Hz = 22ms

Vsync introduces a lag between the frame being ready and being display in the screen. This means input lag is heavily dependent on the screen refresh rate, the higher the refresh rate, the lower the vsync lag. Then we need to add at least one frame time to the vsync lag, which is the minimum required for us to see the new frame. So it goes like this:

​

​

The input lag between 60/60 and 90/45 is identical. Some game engines might work better with higher fps (they’re tie to game render frequency), so 60/60 has a slight advantage over 90/45 regarding input lag overall.

60/60 shows 4 frames in 66ms, but 90/45 only presents 3 frames, so 60/60 is smoother.

90/45 uses less battery and it’s generally more stable, as it gives more times for hiccups in the frame timing.

In conclusion: 60/60 is preferred in high pace/action games (like shooters or racing games), but 90/45 is better in slower pace games, specially open worlds with big variance in scenes (like RDR2 or Spider-man).

60fps is always going to feel smoother than 45fps. In 66ms you’re getting around 4 frames while using 60fps but only 3 frames with 45 fps. This is good for games with a lot of motion, such as racing games.

However the input lag depends on the sync between the game and the monitor. The higher the monitor frequency, the sooner it “asks “ for a new frame. Having a higher frequency means it waits less time before asking for a new frame .

The max input lag is dictated by the monitor frequency. For example, a game that runs at 45fps (and has a frame time of 1s/45= 22ms) has a maximum input lag (the delay between the frame being ready and being displayed in the screen) of 11ms because the screen is checking for a new frame at 90Hz (1s/90=11ms)

Another way to setup FSR is to change game resolution on steam properties, this will force the game to run at that resolution whatever it uses (fullscreen or windowed). When FSR is enabled steam deck will scale game from the configured rework to the display, in this case is to 800p. This is better because it works with every game, the video method does not work with some games that run « scaled to fullscreen » all the time

As far as I know, BOE panels are actually better in low light than Samsung. What’s yours? How many clicks until you can say there’s no black smearing?

I share your opinion, they look cheaper. Not bad, just cheaper.

To do dark plastic is way cheaper than white ones, specially the glossy. The lighter the color the less reusable and recyclable materials they can use, that’s just how plastic works. Dark plastic can contain a lot of recycled plastic, so they get cheaper and appear more often in cheap products. We subconsciously attached them to cheap things because they’re more common, but this does not mean they’re worse, it’s just the association we made

I’ve bought Titan Soul in GOG, installed on Deck and it started, but did not work. Then I bought the same game in Steam and it worked flawlessly. Since then I’m prioritizing Steam despite the DRM :(

It broke one of my external screens vsync for some reason, I guess we’ll have to wait

I’ve read that load times are similar and performance was almost the same between SD card and internal SSD, so I’ve bought a microSD and discover that open world games (like Star Wars Fallen Order, RDR2, etc.) stutter a lot more when they’re in the SD card. I believe that’s because they have multiple assets to load and that causes a bottleneck when moving in the world, the stutters doesn’t happen in the internal SSD. Other simpler games run ok, even if they’re graphically demanding, as long as they don’t use many assets simultaneously

I’m a bit disappointed they did not test in game vsync vs gamescope cap. It’s been the biggest problem related to input lag since launch

Dave the diver

Try Linux. You’ll feel lost, confused, it’s a bit frustrated at first because you will realize how much Linux is the same as windows, but a bit different. The small everyday task are going to be “small learnings” and will take longer than usual in windows. But Linux is not changing a lot against your will every major release, and all functions added are there to add something that users need, not to generate profit. In the long run, it pays off because it makes sense

I’ve been experimenting with VRR in the Deck for a while, I’ve always thought it would save low framerate games, but it actually doesn’t fix games with inconsistent and choppy frame time. But it’s nice to play games that are stable and can vary a lot depending on the region/level.

That being said, it’s very unstable to get the toggle to be available for whatever reason. Yesterday I got it working on my gigabyte usb c monitor, but only one single time. Restarting the device, unplugging it, desktop mode, nothing else worked to get it back after. It almost work every time with a Samsung tv and official dock. So I’ve decided to not use it for now, let me know if you find an answer

I felt the same in the first two weeks. It all comes down to having a good posture to play, and good games properly configured.

I suggest laying down in the couch, with a pillow over your belly and supporting the deck on it to start. Also, limit your TDP to 10W to drastically reduce heat and noise without virtually any lost to performance.

No headphone, no external controller, keep it simple , just try to get a good posture for gaming. Playing in bed is also a good option.

I went to settings and change the audio output there, a few back and forth and it worked, but it’s definitely bugged.

So FYI, the path addition did not work. The folder environments.d wasn’t there, and even after I created, nothing happened, it did not recognize it.

So I ended up adding the following line to .bashrc directly. Also, “mangolimiter” is quite long to type in Deck’s screen, so I’ve shorten to “fps”. I’ll remove the -f parameter, probably, so in the end is going to be just “fps 40 %command%” , but thanks for it

export PATH=“/home/deck/.local/bin:$PATH”

Yes of course, it’s unlikely that will ever be fixed. For now just bypass it completely and use Mango hud commands for an actually usable limiter with low latency.

Is there a way to shorten the command? Or make something default for all?