Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dying Light (DyingLightGame.exe), thread 1559610678497779734. Based on fix/dying-light-lsfg-loader-fix at 0c4361a to retain the verified white-screen fix. Legacy LSFG 2x with a 30 FPS limiter has recurring pacing variation; disabling only LSFG removes it and holds 30 FPS for 170 seconds without thermal throttling. LSFG-on report: 60 reported FPS, 4510/4857 base frame samples quantized and 4281 at 33 ms; these are not measurements of generated-frame spacing. Source inspection: paceBaseFrame refreshes vsyncPhaseNs but keeps incrementing pacerNextDueNs from the original phase indefinitely. Reproject the existing deadline to the nearest refreshed vblank (preserving the base divisor slot), and normalize signed modulo when reinitializing the grid. Add rate-limited base/output submission rate, stage timing, skip and phase-correction diagnostics. Candidate mechanism, not yet verified on device; missing vsync data retains the existing fallback. Validate with Legacy 2x and unchanged 30 FPS limiter on the same route for 120 seconds: recurring variation should disappear, base FPS should remain 30, output submissions near 60, and phase correction/late/skipped generation logs should identify remaining pacing faults. Only Android pacing changes; no shader, loader or native-backend changes.