W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

Re: GamepadObserver (ie. MutationObserver + Gamepad)

From: Florian Bösch <pyalot@gmail.com>
Date: Tue, 7 Aug 2012 12:29:45 +0200
Message-ID: <CAOK8ODhMOGdYcaXxHsYcNX2rdisTvCPEOp2u=NOZXcYSqmjmcg@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: Scott Graham <scottmg@chromium.org>, Rick Waldron <waldron.rick@gmail.com>, olli@pettay.fi, Webapps WG <public-webapps@w3.org>, Ted Mielczarek <ted@mielczarek.org>
On Tue, Aug 7, 2012 at 2:29 AM, Glenn Maynard <glenn@zewt.org> wrote:

> 5ms is an *eternity* when you're aiming for 60 FPS, where you only have
> 16.6ms per frame to play with.  That's 30% of your CPU budget just for
> memory management.  It doesn't matter if it's 5ms every 100 frames, since
> it's the worst case you have to optimize for.  (I've spent a lot of time
> optimizing non-web games to stay at 60 FPS, and it's a battle of
> microseconds, optimizing away .1ms here and .2ms there, so calling 5ms
> "quite low" is a bit troubling.)
On a sidenote, the coming Oculus Rift (VR headset with wide FOV) will be
quite sensitive to lag/jitter and the aim to support that is to have a
total RTT from input -> display of no more than 20ms per frame, for every
frame at preferably 120hz (the dev kit display ships @60hz)
Received on Tuesday, 7 August 2012 10:30:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:37 UTC