Open LaG1924 opened 5 years ago
Thanks reporting this issue. I've submitted a fix for this problem: https://github.com/bombomby/optick/commit/0245eb056f6960fd246c855bc195bd5d4a30fd94. The problem was related to the non-standard DPI-scaling settings which was causing some rendering problems. Now Optick picks up correctly DPI settings and scales all the controls accordingly.
To answer your first question - Optick is optimized for capturing hundreds of frames (standard scenario - 10 sec x 60 FPS = 600 frames). Some of the controls dont scale well to thouthands of frames yet. I'll keep this issue opened for now to see what I could do to optimize 'thousands' of frames scenario. You could also try to run 'Release' configuration with Visual Studio detached - in this case GUI performance will be much better.
Oh, ok. Thanks. About first question: My use-case is rarely high frametime. Is Optick can capture only >Nms frames?
Oh, ok. Thanks. About first question: My use-case is rarely high frametime. Is Optick can capture only >Nms frames?
+1 to this. I have a game with occasional peaks occurring from time to time. Is there any way to capture only these problem frames and maybe a few frames around?
I just captured few thousands of frames and Optick.exe stuck on "Generating summary".... Am I using Optick properly? Or it should collect only few dozens of frames?
UPD: In few hundreds of frames it freezes less, but there is still some kind of incorrect fonts rendering (it's really hard to read).