{"action":"created","issue":{"url":"https://api.github.com/repos/toji/chrome-webvr-issues/issues/73","repository_url":"https://api.github.com/repos/toji/chrome-webvr-issues","labels_url":"https://api.github.com/repos/toji/chrome-webvr-issues/issues/73/labels{/name}","comments_url":"https://api.github.com/repos/toji/chrome-webvr-issues/issues/73/comments","events_url":"https://api.github.com/repos/toji/chrome-webvr-issues/issues/73/events","html_url":"https://github.com/toji/chrome-webvr-issues/issues/73","id":159787038,"number":73,"title":"lag (or misapplied prediction?) in the HTC Vive HMD tracking","user":{"login":"jzitelli","id":350932,"avatar_url":"https://avatars.githubusercontent.com/u/350932?v=3","gravatar_id":"","url":"https://api.github.com/users/jzitelli","html_url":"https://github.com/jzitelli","followers_url":"https://api.github.com/users/jzitelli/followers","following_url":"https://api.github.com/users/jzitelli/following{/other_user}","gists_url":"https://api.github.com/users/jzitelli/gists{/gist_id}","starred_url":"https://api.github.com/users/jzitelli/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jzitelli/subscriptions","organizations_url":"https://api.github.com/users/jzitelli/orgs","repos_url":"https://api.github.com/users/jzitelli/repos","events_url":"https://api.github.com/users/jzitelli/events{/privacy}","received_events_url":"https://api.github.com/users/jzitelli/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2016-06-11T18:35:02Z","updated_at":"2016-08-14T23:13:23Z","closed_at":null,"body":"~~With the HTC Vive, I observe a lag between movement of the chaperone bounds and the rendered WebVR scene when the HMD is tracking.  It looks like the chaperone visual is lagging behind.  I tried to capture a video of the effect, recorded from the SteamVR mirror display, but the lag doesn't show up in the mirror display.~~"},"comment":{"url":"https://api.github.com/repos/toji/chrome-webvr-issues/issues/comments/239703891","html_url":"https://github.com/toji/chrome-webvr-issues/issues/73#issuecomment-239703891","issue_url":"https://api.github.com/repos/toji/chrome-webvr-issues/issues/73","id":239703891,"user":{"login":"bnolan","id":17499,"avatar_url":"https://avatars.githubusercontent.com/u/17499?v=3","gravatar_id":"","url":"https://api.github.com/users/bnolan","html_url":"https://github.com/bnolan","followers_url":"https://api.github.com/users/bnolan/followers","following_url":"https://api.github.com/users/bnolan/following{/other_user}","gists_url":"https://api.github.com/users/bnolan/gists{/gist_id}","starred_url":"https://api.github.com/users/bnolan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bnolan/subscriptions","organizations_url":"https://api.github.com/users/bnolan/orgs","repos_url":"https://api.github.com/users/bnolan/repos","events_url":"https://api.github.com/users/bnolan/events{/privacy}","received_events_url":"https://api.github.com/users/bnolan/received_events","type":"User","site_admin":false},"created_at":"2016-08-14T23:13:23Z","updated_at":"2016-08-14T23:13:23Z","body":"Yeah I've noticed this too. I guess it's either the webgl pipeline takes 3 frames to get the GPU, or somehow the function that returns the pose is returning something 3 frames behind. I assumed it's more likely the former, since it goes through a few compositing stages. It makes the vive pretty uncomfortable."}}
{"actor":{"display_login":"bnolan"}}