Runtime-generated FSR/AFMF presents may suppress simulation intervals and report 0 Simulation FPS
Les mainteneurs répondent en général sous 2 jours
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 45/100
- Type d'issue
- Bug
- Clarté
- Clairement spécifiée
- Activité
- Active
- Stack technique
- cpp
- Domaine
- performance
Piste de recherche
Start with ComputeMsBetweenSimulationStarts() and the UnifiedSwapChain state updates for lastSimStartTime; read PcLatencyFrameGenerationTests::GeneratedPresentDoesNotTakeApplicationPclData for the existing PCL behavior. Add an end-to-end test for generated/application presents sharing a timestamp, including repeated pairs and the listed regression cases. Done means marked application frames produce intervals while generated rows and missing-marker frames do not, with unit coverage and a live or PresentBench2 ETL confirmation.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Summary
Runtime frame generation using separate generated presents, such as FSR-FG or AFMF, may prevent PresentMon from producing msBetweenSimStarts samples when PCL simulation markers are enabled.
This is currently a source-supported hypothesis, not a confirmed live-hardware reproduction.
Suspected symptoms
Affected workloads may show:
MsBetweenSimulationStartasNA.- Missing
PM_METRIC_BETWEEN_SIMULATION_STARTframe values. - Simulation FPS or Simulation Frame Time reporting 0 despite active rendering.
- No valid simulation samples across repeated generated/application frame pairs.
This likely affects runtime-generated FSR/AFMF presents using PCL markers. It is not expected to affect ordinary presentation, application-provider markers, XeSS-FG's currently tested ordering, or generated displays attached to the application's own present.
Root-cause hypothesis
With FSR-style runtime frame generation:
- The generated present completes before its application present.
- Both presents receive the application's PCL simulation-start timestamp.
- The generated row emits no simulation interval because it is not an application frame.
- Despite that, it advances the swap chain's global
lastSimStartTime. - The application row then carries the same timestamp.
ComputeMsBetweenSimulationStarts()requirescurrentSimStartTime > lastSimStartTime, so the application row also emits no interval.
Repeating this sequence may leave the capture with no valid simulation interval samples.
Existing test PcLatencyFrameGenerationTests::GeneratedPresentDoesNotTakeApplicationPclData confirms the prerequisite that generated and application presents can receive the same PCL timestamp.
When this behavior arose
The underlying simulation interval logic has existed since at least commit ee39f134 on January 5, 2026.
The suspected duplicate-timestamp interaction took its current form in commit 081c989b on November 18, 2026, merged through #725. That change correctly allowed a generated present to read PCL data without claiming it, so the following application present could receive the same data.
Before #725, the generated present could consume the timing entry and leave the application present without PCL data. After #725, both presents can carry the same timestamp, exposing the lastSimStartTime interaction described above.
The existing CSV and frame-query simulation interval surfaces predate #741. That PR only makes the behavior more visible by deriving Simulation FPS and Simulation Frame Time from the same field.
Validation plan
End-to-end unit test
Construct a generated AMD_FSR_FG present followed by an application present sharing one PCL simulation timestamp, and feed them through UnifiedSwapChain in their expected completion/display order.
Verify that:
- The generated row has no simulation interval.
- The application row should produce an interval relative to the previous application marker.
- Repeated generated/application pairs continue producing application intervals.
- Missing-marker application frames, dropped frames, XeSS-style ordering, and source transitions do not regress.
This test should exercise actual state updates rather than assigning lastSimStartTime manually.
PresentBench2 experiment
Extend PresentBench2 with optional real FSR-FG support:
- Add a DX12
--use-fsr-fgmode and capability reporting. - Supply FSR-FG depth, motion-vector, and timing inputs.
- Emit
AMD_FSR_FGframe-type events for generated presents. - Run with
--emit-pcl-markers. - Capture ETL and inspect frame type, PCL frame ID, simulation timestamps,
MsBetweenSimulationStart, Simulation FPS, and Simulation Frame Time.
Compare frame generation disabled, FSR-FG enabled, and XeSS-FG enabled.
FSR-FG is cross-vendor, so AMD hardware is not inherently required. Use hardware explicitly supported by the selected FSR SDK version.
Fix proposals
Option A: Update simulation history only for application work
Prevent generated-only rows from advancing lastSimStartTime. Application frames without markers should continue leaving the previous valid marker intact.
This is the smallest fix, but all other users of lastSimStartTime must be audited.
Option B: Track application simulation history separately
Add a dedicated lastAppSimStartTime, update it only from application frames with valid markers, and use it for msBetweenSimStarts.
This avoids changing other consumers of lastSimStartTime and is likely safer, but requires coordinated V1, V2, bootstrap, dropped-frame, and reset handling.
Acceptance criteria
- Generated rows remain missing for application simulation interval metrics.
- Each marked application frame after initialization produces a valid interval.
- No CPU fallback is introduced.
- Missing markers do not erase prior valid application marker history.
- Existing PC latency, animation, XeSS-FG, CSV, and frame-query behavior does not regress.
- Unit coverage and a live or PresentBench2 ETL confirm the result.
- Langage dominant
- C++
- Étoiles
- 2.6k
- Forks
- 201
- Merge moyen
- 2 j 21 h
- PR mergées (30 j)
- 16
Préparer son environnement
Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de GameTechDev/PresentMon
-
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
GameTechDev/PresentMon#745 ·
Les mainteneurs répondent en général sous 2 jours
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 80/100
GameTechDev/PresentMon#684 · 1 commentaire ·
Les mainteneurs répondent en général sous 2 jours
-
Difficulté 4/5 3-5 jours Accessibilité débutants 45/100
GameTechDev/PresentMon#743 ·
Les mainteneurs répondent en général sous 2 jours
-
Reduce nonpaged memory reserved by the PresentMon ETW session at startupPeut-être pris @markgalvan-intel l’a pris il y a 3 jours. OuvertePresentData
GameTechDev/PresentMon#740 · 1 personne assignée ·
Les mainteneurs répondent en général sous 2 jours
-
CLI usability issuesPeut-être pris @planetchili l’a pris il y a 10 jours. Ouverte
GameTechDev/PresentMon#734 · 1 personne assignée ·
Les mainteneurs répondent en général sous 2 jours
Toutes les issues de GameTechDev/PresentMon
Issues similaires
-
needs-format
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Niko1221/Strata#6475 · 1 commentaire ·
Les mainteneurs répondent en général sous 6 jours
-
Refactor kinematic_links integration test to use EcmScopePeut-être pris @patelshivani2283-lab l’a pris aujourd’hui. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour
-
good first issue help wanted
Difficulté 2/5 1-3 heures Accessibilité débutants 79/100
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 85/100
eclipse-score/lifecycle#1061 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 80/100
Les mainteneurs répondent en général sous 1 jour