Here is an update focused on compatibility. Now, users can easily use framepacer with their controllers and handhelds, use framepacer alongside ReShade.
Patch Notes:
NEW Controller Support: Hold View for 1.5 seconds to show/hide framepacer while you're in a game. View on Xbox / Share (or Create) on PlayStation. (Not supported in Exclusive Fullscreen)
NEW ReShade Support: framepacer now works alongside ReShade, no setup needed.
Upgraded Render Engine: Better UI.
Improved support for MS Store games.
Improved status text: No more explorer.exe
Stability and various game fixes
How to use framepacer with frame generation (DLSS, FSR, LSFG):
Many people complain about input lag with Frame Generation. Its actually because their base (real) framerate drops too low. Frame Generation may increase your frames, but your inputs and game physics only respond to the base frames.Recommended Minimum FPS (target at least 50–60 base FPS):
2× Frame Gen: 100–120 FPS (Base: 50–60 FPS)
3× Frame Gen: 150–180 FPS (Base: 50–60 FPS)
4× Frame Gen: 200–240 FPS (Base: 50–60 FPS)
Lossless Scaling (LSFG): Set framepacer to 50–60 FPS (LSFG will scale this up externally).
Why? With in-game DLSS / FSR, framepacer limits total output frames (real + generated). If you set a 60 FPS limit with 2× Frame Gen, your real base framerate will only be 30 FPS, resulting in delayed inputs. Always ensure your base framerate stays at 50 FPS or higher for responsive controls.
Community Spotlight: Upload your tests on YouTube to get featured. Here is an informational video by our Brazilian friend. You may want to use the English dub or subtitles.
How to report bugs: Open the framepacer app folder, find the framepacer.log file, and email it with a description of the bug to [email protected]
For video tutorial: I Can't Believe Nobody Made This Before
For more info: https://framepacer.com