New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crazy high framerates #7555
Comments
Commented by: kain88-de |
Commented by: daschuer e863 is the real time error counter. |
Commented by: kain88-de Ah now I remember something about it. YES we need to change that at On Mon, 2014-08-11 at 15:48 +0000, Daniel Schürmann wrote:
|
Commented by: kain88-de That does the realTimeError Counter actually count? The number of missed frames? |
Commented by: midzer I think the real time error counter has only marginal purpose for the user. |
Commented by: esbrandt +1 |
Commented by: rryan It counts vsync misses. It's useful for developers and useful to ask users On Mon, Sep 15, 2014 at 5:13 PM, Dennis Rohner wrote:
|
Commented by: kain88-de What are we doing when we miss a vsync? Do we just drop the frame or paint it anyway? Currently I would go with being accurate and renaming it to 'vsync misses'. It's also easy to understand and a better description then "Hiccups" or "Glitches" |
Commented by: daschuer The delayed frame is painted in the next frame (now current) . The frame for the current frame is dropped. |
Commented by: kain88-de Good then i suggest we rename it to "dropped frames". On September 16, 2014 1:21:11 PM CEST, "Daniel Schürmann" wrote:
-- |
Issue closed with status Fix Released. |
Reported by: kain88-de
Date: 2014-08-11T12:42:53Z
Status: Fix Released
Importance: Low
Launchpad Issue: lp1355159
Tags: easy, polish, waveform
Attachments: [awesome framerate.png](https://bugs.launchpad.net/bugs/1355159/+attachment/4174451/+files/awesome framerate.png)
There seems to be a problem calculating the current framerate. I get values near absolute zero or crazy large values. I attached a screenshot.
The text was updated successfully, but these errors were encountered: