© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
60 days is an absurd timeout, and I would complain loudly about that...
... If it weren't for the fact that I came back to this bug report to say that it seems to have very recently been solved. Had to have been in version 93 or 94, probably 94.
At least, for my own purposes, it seems completely solved. I'm looking at Shadertoy shaders, and getting a solid 60fps instead of wavering between 50 and 57. I look at these frequently, and feel like I would have noticed sooner than now if the fix happened any sooner than version 94 (or maayybe 93).
Can't say whether or not OP's problem is solved. I haven't done any rigorous benchmarking either, so it might just be Shadertoy improving their framerate detection code. I just know I suddenly no longer need to sit there for several minutes before seeing a framerate of 59 reported, for a single second, before going 57 or lower again the rest of the time.