Closed TheWonderfulTartiflette closed 1 year ago
abrfilho
commented
1 year ago I tried to replicate here, the graph scaled down as soon as the high values disappeared from the screen.
The program is still beta, when I tried to replicate here, at first it didn't detected the process, I had to close PresentMon and open again, the worked without a problem.
Karen-Intel
commented
1 year ago I tried to replicate here, the graph scaled down as soon as the high values disappeared from the screen.
The program is still beta, when I tried to replicate here, at first it didn't detected the process, I had to close PresentMon and open again, the worked without a problem.
Same happened to me, I will add this behavior to a new report anyways :) Ty
Karen
TheWonderfulTartiflette
commented
1 year ago Along with fixing the not scaling down issue, I think it would be really nice to have the option to always make the graphs start at 0. Because right now, in FH5, the frametime graph is scaled at 6-10ms, which makes the GPU Busy line look like it's miles away from the frametime line, misleading the user into thinking that the game isn't GPU-limited
Karen-Intel
commented
1 year ago Hi guys! Just got info regarding Present Mon: The team would like to have everything centralized in a single GitHub so they requested us to help us to submit any PM issue in their GitHub issues forum In the meantime, we will be closing this case. @IGCIT could you do the honors please? TY
Karen
Checklist [README]
Application [Required]
Intel PresentMon Beta
Processor / Processor Number [Required]
Intel Core i5-13600K
Graphic Card [Required]
Intel Arc A770 16GB LE
GPU Driver Version [Required]
Rendering API [Required]
Windows Build Number [Required]
Other Windows build number
No response
Intel System Support Utility report
Intel SSU 18.08.2023.txt
Description and steps to reproduce [Required]
Try to use PresentMon with the frametime graphs. Make them go really high for a sec (like by changing a graphical setting), and you'll see that it won't go down, even though nowhere in the graph now gets even closer to that max value of the right axis
In this screenshot, I've enabled path tracing without any XeSS, which resulted in the worst frametimes you could imagine, they went up to around 230ms, but I've disabled since 5 minutes ago, and the scale doesn't go down, which makes the graph reading impossible as I'm now trying to see a difference of 0.5ms, in a graph axis that goes up to 109ms
Device / Platform
ASUS Prime Z790-P WiFi D4
Crash dumps [Required, if applicable]
No response
Application / Windows logs
No response