<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#FF0000" bgcolor="#FFFFFF">
<span id="result_box" class="short_text" lang="en"><span class="hps">I</span><span
class=""> quite</span> <span class="hps">agree with</span> <span
class="hps">what</span> <span class="hps">Seth</span> <span
class="hps">wrote</span><span>.</span><br>
<br>
<span class="hps">GCI</span></span><br>
<br>
<div class="moz-cite-prefix">Le 09/11/2015 16:05, Seth Nygard a
écrit :<br>
</div>
<blockquote cite="mid:5640B650.1090904@gmail.com" type="cite">Let
the FPS wars begin so there can be confusion everywhere...
<br>
Now those that want to can set a ridiculous fudge factor and show
11000000FPS - WOW, look, waaaaaaay faster than "that other grid"!
<br>
<br>
I firmly disagree in adding anything that allows artificially
inflated metrics for any value. At this stage the configurable
fudge factor is an even worse "fix" IMHO.
<br>
<br>
The correct fix is really to communicate the correct value(s) and
put pressure on the viewer developers to fix their lag
calculation(s). People can be expected to update their viewer(s)
which is not an unrealistic expectation. People running old
and/or unsupported viewers already have a plethora of issues they
need to be aware of and things that don't work right, so why is
the lag indicator any different?
<br>
<br>
If we must have this user configurable then, instead of a fudge
factor value it should be a simple boolean setting such as;
<br>
ShowArtificiallyInflatedAndIncorrectFPS = false;
<br>
ShowArtificiallyInflatedAndIncorrectFPS = true;
<br>
<br>
On my grid I have made it a point to inform everyone that the
calculated lag indicator is broken and the 11FPS is in the correct
and normal value. I also point out that what used to be shown was
in fact a falsified and artificially inflated value to make things
look like "that other grid". Most people simple say "Oh yeah, I
never paid attention to that anyhow. It doesn't work right any of
the time anyhow". Many then say they looked at the wiki but
couldn't find any information on what to expect.
<br>
<br>
If whenever people ask for documentation the standard reply from
the dev community is "read the code" then why is it so hard to ask
for, and expect the viewers to be fixed and updated?
<br>
<br>
-Seth
<br>
</blockquote>
</body>
</html>