Repository navigation
PushFPS v3.2.0
What's new in 3.2.0: PushFlow, HUD detection that works, G-SYNC set-up, better recordings and streams
PushFlow no longer gets stuck at the game's frame rate
PushFlow never refuses to run. When its frames would arrive too late, the frame budget quietly skips them, so a PushFlow that is too slow, or only looked too slow, showed as "stuck at 30 FPS" with no error. That was reported on an AMD card and is likely on NVIDIA cards too. Every cause found in the code is fixed:
- PushFlow no longer waits on the CPU for every frame. Each generated frame used to stop the engine thread until the graphics card had finished the network, and the gaps that left on the GPU queue were counted as frame generation cost. The network is now queued on PushFPS's own GPU queue and the next step follows it there.
- The network has a fixed size. With a size left open, DirectML could not plan the network ahead and ONNX Runtime ran part of it on the CPU provider. Each PushFlow start now fixes the size, and every part of the network runs on the graphics card.
- Warm-up at start. DirectML prepares the network on its first runs. That now happens while PushFlow starts, not on your first frames.
- A skipped frame pair no longer costs a second one, and the first measurements after a skip no longer start the next skip (the fix NVIDIA VFG already had).
- Too slow for your card? PushFlow says so and steps down. If nearly every pair is skipped for eight seconds, PushFlow moves one tier down (Quality → Balanced → Fast) and tells you why. On Fast it tells you what else would help.
- Half precision, tested safely. Half precision can make the network about twice as fast, but it depends on the card and driver. Professional → Frame generation → PushFlow half precision → Test now tries it in a separate process, so a driver fault cannot touch PushFPS, and turns it on only if the picture matches and it really is faster.
The time shown for PushFlow in the quick setup is now the network's real time on the graphics card.
Automatic HUD detection now finds real HUDs
The first detector only counted an area as HUD when a whole block of the picture stood still. Text drawn straight over the game, thin health bars, half-transparent panels and a minimap whose map scrolls never do, so on most games it found nothing. It now looks at every pixel of a 1080p copy of the picture: a pixel that holds still while its surroundings move, or next to another still pixel of a different brightness, is HUD. Letterbox bars and a flat sky are still left alone.
In the new tests (whole pictures drawn the way games draw them, in 1080p, 4K and a noisy 720p stream) the old detector found none of the HUD elements and the new one finds all of them.
Optimise for my PC
- A method that crashes can't break it twice. While it tests, PushFPS keeps on disk which method is running. If PushFPS stops in one, your settings from before come back at the next start (since 3.1.7) and what was being tested (the method, or the extra on top of it such as AI enhancement) is not tested again in this version. The crash report behind this (an RTX 5090 over Xbox Remote Play) ended inside ONNX Runtime while PushFlow was being tested. The most likely cause is PushFlow's start-up check of half precision, which broke the graphics device on the software renderer; that check no longer runs inside PushFPS. Not confirmed on that PC.
- It works the same with a capture card and with PS5 or Xbox Remote Play: it measures the picture that is on screen.
- If your game is set to 30 FPS but 60 new pictures a second are measured, the result says so and points to the "60→30" fix.
Live play
- G-SYNC set-up from the quick setup. If your screen can do variable refresh but the NVIDIA driver has not turned it on for PushFPS, live play judders where a recording looks smooth. The quick setup now shows a row with a Set up button when that is the case. It does what Professional → Display → NVIDIA G-SYNC profile → Repair does: allows G-SYNC for PushFPS in a window and in full screen (restart PushFPS afterwards).
- A notice when duplicate removal can't see your game's 30 FPS (some capture cards add noise to repeated pictures), pointing to the one-click "60→30" fix in the quick setup.
Recording and going live
-
Two-pass encoding and psycho-visual tuning (NVIDIA NVENC), for recordings (Settings → Recording → Advanced) and for streams (Go live). Both are off by default. If your card refuses them, PushFPS keeps your other settings and says so.
-
Twitch test stream. A switch on a Twitch output sends the stream as a test: Twitch takes it without showing it on your channel or notifying followers, so you can check the connection and bitrate first.
-
A stream that is dropped right after it connects (a wrong or expired stream key, a second stream on the same key) now backs off and stops with a clear message. It used to reconnect every two seconds for as long as you were live.
-
A stream encoder that refused your advanced settings fell back to a variable bitrate. It now stays on the constant bitrate the platforms ask for.
-
Instant replay shows what it costs. Settings → Recording → Instant replay and video playback mode show, live, how much memory the buffer uses now and how much the chosen length takes when full. A saved clip takes about the same on disk.
Updates
- The in-app update (the banner, or Settings → About) downloads the new release, checks its signature and installs it. That path is now run end to end on every build, and the first run found a real fault: if PushFPS had been started from a PowerShell 7 window (or by a tool running under it), the update stopped right away ("Get-FileHash is not recognized") with PushFPS already closed, so the old version came back and offered the update again. Fixed. If an update cannot finish for another reason, the installer now says why, keeps its window open and starts the version you still have.
- The update banner only appears when the installed version is older than the latest release. (3.1.3 and 3.1.4 offered the update they already had; that was fixed in 3.1.5.) The log now records the installed and latest versions, so a wrong offer can be traced.
Linux
- The AppImage is now named
PushFPS-<version>-x86_64.AppImageand carries update information, with a.zsyncfile beside it, so AppImageUpdate and similar tools can update it. (Suggested by the AppImage catalog's test, which PushFPS passed.)
About
- PushFPS is made by DosukaSOL: credited in Settings → About, with a link to @DosukaSOL on X.
How it was tested
On GitHub's Windows machines, which have no graphics card: the build, the unit tests (the HUD detector's also on Linux), PushFlow through DirectML on Windows' software renderer (all three tiers, the queued path against the old waiting path, the half precision test process), the QML tests, the live-stream tests against a local RTMP server, and the install and update test.
Not tested on real hardware: PushFlow's speed on NVIDIA, AMD and Intel cards, the NVENC options, the G-SYNC row and HUD detection on real games (its test pictures are drawn, not captured). The software renderer shows that the new paths are correct, not how fast they are on your card. PushFlowBench.exe (next to PushFPS.exe) measures that; results are welcome in a GitHub issue.
Windows Defender note. Defender may flag new PushFPS downloads as Trojan:Win32/Tecabans.STV!cl. This is a false positive from its cloud check on new, unsigned files, and it has been reported to Microsoft. Always check the zip against SHA256SUMS.txt on this page.
Credits. PushFPS is built on Veyra by Likely7. PushFlow runs RIFE by hzwer. ANR frame generation is by Apex Compute.
Install
- Download PushFPS-3.2.0-win64.zip below and extract it.
- Double-click Install-PushFPS.cmd.
The installer downloads Veyra's official runtime package (about 750 MB, NVIDIA or AMD to match your
graphics card) from Veyra's GitHub release, checks its SHA-256, and installs PushFPS with Start menu
and desktop shortcuts. No administrator rights needed.
Built and tested automatically on Windows. Please report anything that doesn't work in Issues.
SHA-256: 44E7DD65ABA50058A903A4B5B080CEE78761C3C067435BA243D7BB6E01426016 PushFPS-3.2.0-win64.zip
Setup guide
PushFPS-Setup-Guide.txt has the recommended settings to start from, how to tune them, the
settings for PS5, Xbox and Switch, the Windows settings and when to use HDR. Also on the website:
https://dosukasol.github.io/PushFPS/#guide
OBS Studio plugin
PushFPS-OBS-Plugin-1.2.0-win64.zip adds a PushFPS source to OBS Studio 28+ (Windows): your PushFPS picture,
frame generation included, in any scene. Extract it and double-click Install-PushFPS-OBS.cmd.
SHA-256: 3549d7282caee30bc43df5fe4370ed1b41161e042402d2a54a3b42cf61b44dab PushFPS-OBS-Plugin-1.2.0-win64.zip
Linux and macOS (preview)
PushFPS also runs on Linux and macOS with its own frame generation, Frame Pacing Repair and Live HUD
Lock (no vendor components). The packages (linux-x86_64 folder or AppImage, macos-universal app)
are attached to this release when their build finishes. See the README for what is tested.
Checking the download
SHA256SUMS.txt lists the SHA-256 of every file; *-components.txt lists the pinned components
this build was made from.
License and source
PushFPS is free software under the GNU GPL-3.0 and comes with no warranty. It is a modified version of
Veyra by Likely7 (see NOTICE.md). Corresponding source:
the v3.2.0 tag of this repository (also attached by GitHub as Source code); the build recipe is
.github/workflows/build-windows.yml at that tag. The streaming libraries built into PushFPS
(chiaki-ng, AGPL-3.0 with the OpenSSL exception; moonlight-common-c, GPL-3.0; and the vcpkg recipes of
OpenSSL, Opus, SDL3, libdatachannel and the other static libraries) are in the attached
streaming-source archive.