This repository has been archived by the owner. It is now read-only.

requestAnimationFrame passes wrong timeStamp in latest Chromium build #126

Closed
customlogic opened this Issue Jan 5, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@customlogic

customlogic commented Jan 5, 2017

The VR display's "requestAnimationFrame" function should pass a parameter to the callback that represents the current time (docs). However, in the latest Chromium ( Oct 29 build) with an HTC Vive i'm seeing a bogus time being sent. The time starts at -92 seconds and counts up to 0 then continues on as normal. This problem didn't exist in previous builds (Sept 23, etc).

I've created a quick example to show what's going on:
https://jsfiddle.net/zs4j5s3j/4/

If you open this in regular chrome, or previous builds, you'll see the current time reported correctly. In the Oct 29 build, you'll see the negative time I'm talking about:
chromium_bug

@machenmusik

This comment has been minimized.

machenmusik commented Feb 17, 2017

Actually, I believe this is resolved in the early Feb 2017 build...

@Sebkasanzew

This comment has been minimized.

Sebkasanzew commented Feb 26, 2017

I can confirm that the time in the example (https://jsfiddle.net/zs4j5s3j/4/) is positive again in the Chrome Feb 17th build.

@customlogic

This comment has been minimized.

customlogic commented Mar 13, 2017

I checked as well, and it does appear to be fixed. Thank you!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.