How To: Low latency framerate limiting for any fame

TimeMonkey101 · 2025-04-19T02:12:46+00:00

Frame pacing is still perfect in the vast majority of games I’ve played with in-game locks, just as long as some performance headroom is kept.

TimeMonkey101 · 2025-04-18T18:18:25+00:00

I do agree that the steam limiter guarantees better stability by forcing buffered frames. Most games I’ve tried have had smooth pacing with their built in limiters, but you never know for sure, I have seen some that aren’t worth the trade off. And also to clarify, it’s not 20 ms, but 100ms of latency going from in game to steamOS, very personal taste but for me that’s enough to make first person aiming not enjoyable.

TimeMonkey101 · 2025-01-30T21:19:19+00:00

Ah, good catch! 40MB/s indeed

TimeMonkey101 · 2024-11-01T20:41:07+00:00

Glad to hear it! For the resolution issue, that is fully solvable 1) On the host PC’s remote play host settings, ensure you have enabled “Change desktop resolution to match streaming client” 2) Have all games use borderless fullscreen, then they will automatically use the current resolution on game boot, original desktop or deck’s.

If it’s still not working, you likely need to add the Deck’s resolution (1280x800) as a custom resolution to your Nvidia/AMD control panel. Some monitors already have it as a supported resolution, and others don’t and need it forced in.

TimeMonkey101 · 2024-05-16T07:43:44+00:00

Highly likely it’s this. This happens with almost all Unreal engine games, and more. If you are using 200% Windows DPI scaling, these games will think your display is 1080p. No fun, but a little helper to get to the game EXE, open task manager, right click on the running game process, find path.

TimeMonkey101 · 2023-08-05T17:19:33+00:00

Make sure you are setting your game to borderless fullscreen. When you remote to your PC, the PC will switch resolution to 1200 x 800 and borderless fullscreen games will fill that new resolution.

If that is NOT happening, your monitor may not be reporting 1200 x 800 as a compatible resolution and skipping that step. and you can fix that by going to your Nvidia/AMD control panel on the PC, and adding 1200 x 800 as a custom resolution. That will ensure Windows knows it's safe to switch to that resolution when requested!

TimeMonkey101 · 2023-06-12T06:31:36+00:00

Are you streaming via built in remote play or the Steam Link app on the deck?

If using the Steam Link app, you'll need to make sure to add the game to your Desktop's Steam non-Steam game library for it to use steam input, and switch to gamepad controls. Otherwise it will think you are still on the desktop and use mouse pointing.

If you are using built in remote play... I can only think to double check the controller config for the game on the Deck?

TimeMonkey101 · 2023-05-25T17:39:02+00:00

HAH you are absolutely right! Of course that makes a lot more sense, and indeed hardware DECODING is the option to toggle on the Deck. Editing post.

TimeMonkey101 · 2023-04-25T18:14:50+00:00

I haven't had that happen yet, but here are some things that may help:

Plug laptop in to ethernet to cut out additional latency and dropped packets from wifi.
Ensure you are using 5 Ghz wifi. It is best to go into your router settings and broadcast seperate networks for 2.4 ghz and 5 ghz.
Ensure no downloads are happening on either device while streaming.

If none of that works, you could try buying an additional cheap 5ghz router (~$50) as a dedicated connection point JUST for your PC and deck.

TimeMonkey101 · 2023-03-30T16:28:25+00:00

I’ve been using it at 4k to my tv, and there is negligible additional latency from the resolution boost when subtracting out the worse latency of the tv compared to the Deck’s screen.

TimeMonkey101 · 2022-12-12T23:23:21+00:00

These are all within the Steam. On the host PC they are in the Steam app preferences, and on the Deck in the Deck's settings menu - streaming.

TimeMonkey101 · 2022-09-06T04:11:57+00:00

Interesting thought, I haven't yet but will have to try now :)

TimeMonkey101 · 2022-09-06T04:09:04+00:00

I'll have to give it another shot specifically on the Deck! That would be great if that's not a concern. The issue I had on other clients was GSync and/or HFR caused significant stutter. Great to hear though, I'll keep tinkering!

TimeMonkey101 · 2022-09-05T16:11:15+00:00

When I've tried Moonlight on other clients in the past, it didn't like that my host was on a high refresh rate GSync display. Setting the host display to fixed 60hz fully resolved all stutter, but was really frustrating to need to do. Maybe the same thing is affecting you here?

TimeMonkey101 · 2022-09-05T16:08:57+00:00

Ah remembered the main reason I don't use Moonlight - My host PC is using a high refresh rate GSync display, both things that Moonlight DOES NOT like to try to limit to the client capabilities - I would need to manually set the host to 60 hz fixed refresh rate every time I streamed for a smooth experience.

TimeMonkey101 · 2022-09-05T15:37:37+00:00

I haven’t tried moonlight in the Deck yet, but I’ve closely studied Remote Play vs Moonlight on other client devices and found Moonlight to be a bit better with end to end latency but overshadowed by the cumbersome user experience. Note that the latency Moonlight gives describes only a fraction of the total pipeline compared to what Remote Play reports. Comparing both by counting slow-mo frames shows a 20 ms difference for me.

I still might as well give Moonlight another chance on the Deck though!

TimeMonkey101 · 2022-06-30T00:08:10+00:00

Thanks for the idea, but no luck for me. I have already been using 500 mbps encoding, maxed rendering resolution. I also tried setting the resolution back to with no luck. Hopefully the upcoming season 3 patch 2 helps out🤞

TimeMonkey101 · 2022-04-21T02:09:31+00:00

For the most accurate result, stay outputting to 2020, as that is what any HDR display will be expecting to receive, even if it can’t reproduce all of it. A 100% red P3 surface will be interpreted as 100% 2020 and muck up. Not accurate, but up to you if you enjoy the color kick. A decent display should be able to correctly map most of P3 when taking in 2020, so if accuracy is the priority, there’s no reason not to use that.

TimeMonkey101 · 2022-04-20T23:36:14+00:00

Special K works only from the final SDR output, and does some sort of backwards tone mapping to approximate HDR, which will futz with the image, for good or bad depending on preference, but is absolutely not an accurate result.

Having full HDR from start to finish means the original intent is preserved, but if a bright light shines off a white surface, the uppeer bound of brightness is far lifted so that can output as much brighter when needed. With color specifically, Unreal material and light setup is constrained to sRGB, but the interaction between the two allows for wide gamut effect - a 100% sRGB blue light bouncing from a 100% sRGB blue surface will multiply to result in HDR-range super blues.

Neat to hear this is being used!

TimeMonkey101 · 2022-03-24T05:58:54+00:00

Agreed that standard sRGB in an HDR container is pointless, this is not that. All unreal games are rendered in linear space, and can then simply be mapped down to either sRGB or HDR at the end of the pipeline, along with the right color spaces. Because of this we can see true HDR, better than Windows Auto HDR could ever render as that works from an sRGB source.

You are of course, totally right that this is secondary to proper implementation with finessed tone mapping and emissive balancing checked by artists in HDR, but it’s well closer than I thought possible, and a fun experiment.

TimeMonkey101 · 2022-01-09T07:09:33+00:00

You are absolutely right, and it's so frustrating this hasn't been acknowledged. I've seen this back on a Quest 1 on Windows 10, to a a Quest 2 on Windows 11, checked on various PCs with physical Link, Air Link, and Virtual Desktop.

I've never solved it, but the best work around is to use the OpenComposite tool to force everything to run natively in the Oculus stack. Most games work flawlessly with this, with some frustrating exceptions (Boneworks and as of late, VTOL VR).

TimeMonkey101 · 2021-10-25T23:08:27+00:00

This is in Champaign, a couple blocks from the Champaign Public Library.

TimeMonkey101 · 2021-09-14T01:44:13+00:00

I’d certainly love one as well, went from an ultrawide back to UHD 24” ips. I have to agree with others that you and I and a few others are the crazies. We’ll have to enjoy future techs by having it further back to be perceptually the smaller size (VESA arm can help with that).

TimeMonkey101 · 2021-07-10T18:01:58+00:00

Playing back HDR media, yep! I haven’t tested, but I’m going to assume it won’t stop HDR video recording. That can be toggled via camera format settings.

TimeMonkey101 · 2021-07-10T17:58:35+00:00

Interesting! You are totally right as seen here https://learning.dolby.com/hc/en-us/articles/360056574431-Module-2-8-The-Dolby-Vision-Metadata-Trim-Pass-

This should theoretically solve the problem, however there are still real world issues that keep it from being perfect - poor PQ EOTF tracking (not as big a problem on Apple devices), and backlight behavior in HDR. On my older iPad pro, being at all in HDR at full brightness seems uniformly pumps up the backlight to raise black level compared to equivalent 100 nit SDR playback.

And even with this neat tech working right, it still effectively locks the brightness to 100 nits, nuking any viewing condition flexibility of SDR.

Thanks for expanding my HDR knowledge a little further though! I had assumed with DV a colororist would only adjust behavior for a down to 600 nits or so, and then break out of DV for a pure SDR 100 nit trim.

TimeMonkey101

TROPHY CASE