mirror of
https://github.com/PlayCover/PlayCover.git
synced 2026-04-26 00:05:52 +03:00
[GH-ISSUE #2046] [Bug]: Zenless Zone Zero incorrect frame limit #1365
Labels
No labels
UI
app-support
bug
bug
documentation
duplicate
enhancement
game-support
good first issue
help wanted / caution
inactive
invalid
macos-beta
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PlayCover#1365
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Hunor64 on GitHub (Dec 23, 2025).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/2046
Describe the bug
In Zenless Zone Zero running via PlayCover, setting the in-game frame rate limit to 120 FPS results in the game being hard capped at 90 FPS when my external monitor is set to 180Hz refresh rate. Dropping the monitor refresh rate to 120Hz allows the game to correctly cap at 120 FPS. Switching back to 180Hz immediately drops it back to 90 FPS half of 180Hz.
Steps to reproduce
Expected behaviour
When my monitor is set to 180 hertz the game should have an fps cap of 120 not 90
Crash log
What version of PlayCover are you using?
3.1.0
What version of macOS are you using?
Other (please specify)
Issue Language
@ohaiibuzzle commented on GitHub (Feb 12, 2026):
I suspect this is actually a bug in Apple's Vsync and just that no one noticed it yet