Repository navigation
PushFPS v4.0.0
What's new in 4.0
4.0 is about how the picture and the sound feel while you play: less ghosting in the HUD, a steadier
rhythm for 30 FPS games, sound you can line up with the picture, recording choices before you record,
and a set of reliability fixes.
If something is worse for you than in 3.2.10, please tell us with a performance report
(Settings → Performance report → Copy).
The HUD stays sharp with frame generation (on by default)
Frame generation works out one motion for every place of the picture. Where a HUD stands still in front
of a world that moves, the HUD's pixels were dragged along with the world: text, bars and the crosshair
smeared, doubled or vanished in the generated frames. That happened with every method.
Now a pixel that is the same in both real frames, and stands in a surrounding that mostly moves, keeps
its real value in the generated frames between them.
- It works with every method PushFPS runs itself: NVIDIA's, AMD's FSR and PushFlow. Not with Intel XeSS,
which presents its own frames. - It needs no setup and no warm-up, and it is its own switch: Quick setup → Keep the HUD sharp.
Live HUD Lock is still there and is not changed by it. - With a still camera or in a menu it touches nothing.
- It costs a little graphics card time for every frame (one pass over the picture). If frame generation
skips more than before on your card, switch it off and tell us. - Measured on PushFlow's models with drawn test pictures: the HUD's pixels were off by 14 to 40 of 255
without it and by about 1 with it. - What it does not fix: ghosting in the moving world right beside a character. A character who stands
still while the world moves keeps a cleaner outline (the error inside it roughly halves); the band of
world next to him is as before, and so is a character who moves himself. - A source with visible noise (an analogue link, a hard-compressed stream) has few pixels that are the same
twice, so the rule finds less there.
A steadier rhythm for 30 FPS games
With duplicate removal on 60 → 30 (a 30 FPS game through a 60 Hz capture), a game that dipped under 30
made PushFPS lose its rhythm: it kept a repeated picture, then ran three pictures 16.7 ms late and threw
one away. In one session we looked at, that happened 325 times, about once every 14 seconds.
A repeat of the picture already kept now waits for the next new picture instead. A still picture (a
menu, a loading screen) keeps its rhythm, and the first new picture after one is shown at once.
Lip sync by hand
Quick setup → Lip sync: move the sound earlier or later in steps of 10 ms, up to 250 ms.
Automatic sync delays the sound by the time the picture spends inside PushFPS. It cannot see how much later
than its sound your capture card hands over the picture, or what your screen, soundbar or wireless headphones
add afterwards. If voices come before the mouths move, press Later 10 until they match.
- It adds to automatic sync. In manual mode, or with sync off, it does nothing, and the row says so.
- Sound cannot be played before it arrives: when Earlier 10 has no more effect, the row says so.
Choose before you record
Click Record and you first choose what the recording will be:
- Shape: horizontal, as the picture is, or vertical 9:16 for TikTok, Shorts and Reels.
- Vertical: Fill (the picture fills the frame, its sides are cut) or Fit (the whole picture, with
bars above and below). - Size: the picture's own, 4K, 1440p or 1080p.
- Quality: Best (constant quality: stays sharp however busy the picture gets, the largest files),
High (the standard bitrate, about 149 Mbps for 4K at 60 FPS) or Smaller files (half of it).
A line under the choices says exactly what will be recorded: size, frames a second, codec, bitrate and
megabytes a minute. If a platform preset from Settings → Recording is in force, you see its bitrate
there (the YouTube 4K preset is 60 Mbps, which looks softer than the standard) and one tap changes it.
- The recording shortcut never asks: it starts at once with what you chose last.
- Don't want the question? Switch off Ask before every recording in the dialog or in
Settings → Recording. The buttons then start at once, as before. - These are the same settings as in Settings → Recording, so the two always agree.
A clear line in "compare to original"
The live split comparison now has a line where the two sides meet: white between two dark edges, so it
shows on bright and dark pictures. It is as high as the picture and scales with the resolution.
Put the latency readout where you want it
With Show latency on screen on, drag the readout anywhere over the picture. It stays there after a
restart and when the window changes size, and it cannot leave the picture. A double click sends it back to
the top left corner. While mouse input goes to the game it cannot be moved.
Capture cards
- Sound for a new capture card. A card that was never set up started with Don't capture audio, and
the sound input had to be picked by hand. That is what the "no audio" reports came from. A new card now
starts with its own sound input chosen, when it is beyond doubt which one that is. You see the choice in
the capture dialog before you connect. A microphone or headset is never chosen. - A card you already set up keeps its setting, also Don't capture audio. If its own input is found, the
capture dialog offers it, and connecting without sound is said (three times at most). - Reported working by users and added to the list: Elgato HD60 Pro and ezcap Game Link Raw.
PS5 Remote Play
- A video frame that arrived at the very moment the queue was read could be taken for too old, which
started a recovery (a short freeze and a new keyframe). It is now treated as new. - Controller input: a quick press and its release between two sends both reach the console, analogue
values use the newest reading, and an input older than 100 ms is dropped by itself instead of with
everything behind it. - The log now says what started each recovery.
Video files and HDR
- AV1 files use the graphics card's AV1 decoder when it has one (software decoding as before when not).
- Dolby Vision profile 8.4 files whose base layer is marked wrongly are shown as HLG, as they should be.
- A display that reports the HDR format's limit (10,000 nits) instead of its own peak is no longer believed
by the automatic tone curve.
Also
- Log files are named after PushFPS.
pushfps-qml.log,pushfps-last-session.txt,
pushfps-last-failure.txt,pushfps-crash-*.dmp,pushfps-hang-*.dmp. Files from an older version
are taken over once at the first start. - Performance report: it now includes how the picture reaches the screen and the time from PushFPS
handing a frame over to the refresh that shows it. The on-screen latency figure ends at the hand-over;
this is the step after it.
What was tested where
Everything above passed the Windows build's automatic tests, which run on a software renderer: for the HUD
rule the shaders are compared with the rule's plain code pixel by pixel, the 60 → 30 logic is replayed
against the old one, the sound input choice is tested on device names as Windows writes them, and the
record dialog's choices are checked down to the preferences the recorder reads (no file is encoded in
these tests). The HUD
figures were measured on PushFlow's shipped models with drawn pictures. Real graphics cards, capture cards
and games come next, with your reports.
Known limits
- Ghosting around a moving character, and in the world right beside a still one, is not improved.
- The capture device list that never answers on some PCs with two Elgato cards is still open: we need a
log from 3.2.6 or newer to see where it stops.
Install
- Download PushFPS-4.0.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: 3B61C57D4449089A4E558BADC55D70DEF35544F818159C25FF2758F37A9BF19A PushFPS-4.0.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: cae3b234330f2802bb669037ff92eaab3a151d388626104686d1e5737b4a82de 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 v4.0.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.