https://bugs.kde.org/show_bug.cgi?id=409460
--- Comment #2 from Aaron Lavarnway <i...@ralek.art> --- The 'diagnostics' I'm referring to are the 'Debug logging of OpenGL framerate' outputs. Which as I said in the original post, do show 100+ fps (or 60 fps if vsync is forced on in nvidia settings) What Krita is 'theoretically rendering at' has no bearing on this issue as it's a frame distribution issue rather than an actual framerate issue. The canvas is rendered, somehow, in such a way that it gives the appearance to the naked eye as only being 30 FPS rather than the 100+ FPS that the debug logging talks about. I assumed that the canvas appearing to the naked eye was half the FPS of the screen it's on was unintentional so I decided to try and figure out what exactly is going on behind the scenes to cause it to act this way. I'm still not entire sure what is going on with it. I can record a comparison video of what Krita's doing vs what I expect it to do if it would help further explain my case. -- You are receiving this mail because: You are watching all bug changes.
