borismus
commented
8 years ago Sounds like you might be dropping frames. You can check if this is happening in the devtools.
On Tue, Oct 25, 2016 at 9:51 PM epascal notifications@github.com wrote:
I'm developping a 3D viewer in WebGL that works fine at 60fps very stable (added a stats display to ensure stability afterward). I enabled Gear VR developper mode for low persistence and it removed completely the blur phenomenon I had. Now I see clearly a phenomenon that is strange, there is every second a slight jump in the display as if the head pose skip a position. As I use pose prediction, it seems to me strange that the transitions are not perfectly smooth and the periodicity of the jump make me think that it's not due to external applications. Do you have any idea on the reason of this phenomenon. Except for that, it really a very good algorithm you have implemented. Here is my configuration:
window.WebVRConfig = WebVRConfig = { // Flag to disabled the UI in VR Mode. CARDBOARD_UI_DISABLED: true, // Default: false
// Forces availability of VR mode, even for non-mobile devices. FORCE_ENABLE_VR: false, // Default: false.
// Complementary filter coefficient. 0 for accelerometer, 1 for gyro. K_FILTER: 0.98, // Default: 0.98.
// Flag to disable the instructions to rotate your device. ROTATE_INSTRUCTIONS_DISABLED: false, // Default: false.
// How far into the future to predict during fast motion (in seconds). PREDICTION_TIME_S: 0.0, // Default: 0.040.
// Flag to disable touch panner. In case you have your own touch controls. TOUCH_PANNER_DISABLED: false, // Default: true.
// Enable yaw panning only, disabling roll and pitch. This can be useful // for panoramas with nothing interesting above or below. YAW_ONLY: false, // Default: false.
// To disable keyboard and mouse controls, if you want to use your own // implementation. MOUSE_KEYBOARD_CONTROLS_DISABLED: true, // Default: false.
// Prevent the polyfill from initializing immediately. Requires the app // to call InitializeWebVRPolyfill() before it can be used. DEFER_INITIALIZATION: false, // Default: false.
// Enable the deprecated version of the API (navigator.getVRDevices). ENABLE_DEPRECATED_API: true, // Default: false.
// Scales the recommended buffer size reported by WebVR, which can improve // performance. BUFFER_SCALE: 0.5, // Default: 0.5.
// Allow VRDisplay.submitFrame to change gl bindings, which is more // efficient if the application code will re-bind its resources on the // next frame anyway. This has been seen to cause rendering glitches with // THREE.js. // Dirty bindings include: gl.FRAMEBUFFER_BINDING, gl.CURRENT_PROGRAM, // gl.ARRAY_BUFFER_BINDING, gl.ELEMENT_ARRAY_BUFFER_BINDING, // and gl.TEXTURE_BINDING_2D for texture unit 0. DIRTY_SUBMIT_FRAME_BINDINGS: false // Default: false. };
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/googlevr/webvr-polyfill/issues/168, or mute the thread https://github.com/notifications/unsubscribe-auth/AAQ8gDeCJ5hgdT58kTnfwakLlUHQEIiTks5q3txRgaJpZM4Kgwcp .
epascal
dustinkerstein
devmobileaim
jsantell
I'm developping a 3D viewer in WebGL that works fine at 60fps very stable (added a stats display to ensure stability afterward). I enabled Gear VR developper mode for low persistence and it removed completely the blur phenomenon I had. Now I see clearly a phenomenon that is strange, there is every second a slight jump in the display as if the head pose skip a position. As I use pose prediction, it seems to me strange that the transitions are not perfectly smooth and the periodicity of the jump make me think that it's not due to external applications. Do you have any idea on the reason of this phenomenon. Except for that, it really a very good algorithm you have implemented. Here is my configuration:
window.WebVRConfig = WebVRConfig = { // Flag to disabled the UI in VR Mode. CARDBOARD_UI_DISABLED: true, // Default: false
// Forces availability of VR mode, even for non-mobile devices. FORCE_ENABLE_VR: false, // Default: false.
// Complementary filter coefficient. 0 for accelerometer, 1 for gyro. K_FILTER: 0.98, // Default: 0.98.
// Flag to disable the instructions to rotate your device. ROTATE_INSTRUCTIONS_DISABLED: false, // Default: false.
// How far into the future to predict during fast motion (in seconds). PREDICTION_TIME_S: 0.0, // Default: 0.040.
// Flag to disable touch panner. In case you have your own touch controls. TOUCH_PANNER_DISABLED: false, // Default: true.
// Enable yaw panning only, disabling roll and pitch. This can be useful // for panoramas with nothing interesting above or below. YAW_ONLY: false, // Default: false.
// To disable keyboard and mouse controls, if you want to use your own // implementation. MOUSE_KEYBOARD_CONTROLS_DISABLED: true, // Default: false.
// Prevent the polyfill from initializing immediately. Requires the app // to call InitializeWebVRPolyfill() before it can be used. DEFER_INITIALIZATION: false, // Default: false.
// Enable the deprecated version of the API (navigator.getVRDevices). ENABLE_DEPRECATED_API: true, // Default: false.
// Scales the recommended buffer size reported by WebVR, which can improve // performance. BUFFER_SCALE: 0.5, // Default: 0.5.
// Allow VRDisplay.submitFrame to change gl bindings, which is more // efficient if the application code will re-bind its resources on the // next frame anyway. This has been seen to cause rendering glitches with // THREE.js. // Dirty bindings include: gl.FRAMEBUFFER_BINDING, gl.CURRENT_PROGRAM, // gl.ARRAY_BUFFER_BINDING, gl.ELEMENT_ARRAY_BUFFER_BINDING, // and gl.TEXTURE_BINDING_2D for texture unit 0. DIRTY_SUBMIT_FRAME_BINDINGS: false // Default: false. };