Oculus CV1 connect but crash

Last week we were super happy to notice an update to Oculus support in April. We pulled out the Oculus CV1 headset and set up a new laptop to try it out.

 

The Oculus is all set up and Psychtoolbox seems to connect but the demos exit out with some kind of complaint about having the wrong rect.

 

Below are two versions of the error from two different demos

 

Hope you can shed some light.

 

 

Cheers,

Tamara Watson (Western Sydney Uni)

 

Try 1

 

>> VRHMDDemo

PsychOculusVR1: Opening the first connected Oculus VR headset.

Copyright (c) 2018 Mario Kleiner. Licensed under the MIT license.

The underlying PsychOculusVRCore1 mex driver uses the Oculus SDK, which is “Copyright © Facebook Technologies, LLC and its affiliates. All rights reserved.” A copy of the Oculus SDK license, its terms of use and thereby redistribution terms for the PsychOculusVRCore1 mex file can be found in the

PsychtoolboxRoot()

folder under:

Psychtoolbox/PsychHardware/PsychVRToolbox/LICENSE_OculusSDK1.txt

 

 

PsychOculusVRCore1-INFO: Oculus VR runtime (version '1.36.0') initialized.

PsychOculusVRCore1-INFO: At startup there are 1 Oculus HMDs available.

PsychOculusVRCore1-INFO: Opened Oculus Rift with deviceIndex 0 as handle 1.

PsychOculusVRCore1-INFO: Product: Oculus Rift CV1 - Manufacturer: Oculus VR - SerialNo: WMHD303J5010ED [VID: 0x2833 PID: 0x31]

PsychOculusVRCore1-INFO: Firmware version: 7.9

PsychOculusVRCore1-INFO: Panel size in pixels w x h = 2160 x 1200 - Refresh rate = 89.998001 fps

PsychOculusVRCore1-INFO: Caps: Debug device=0

PsychOculusVRCore1-INFO: Fields of view (Fov): [left, right, up, down] in degrees follow:

PsychOculusVRCore1-INFO: Max Left eye Fov:     [55.286181, 40.981596, 50.964488, 63.651332]

PsychOculusVRCore1-INFO: Max Right eye Fov:    [40.981596, 55.286181, 50.964488, 63.651332]

PsychOculusVRCore1-INFO: Def Left eye Fov:     [55.286181, 40.981596, 50.964488, 63.651332]

PsychOculusVRCore1-INFO: Def Right eye Fov:    [40.981596, 55.286181, 50.964488, 63.651332]

PsychOculusVRCore1-INFO:

----------------------------------------------------------------------------------

PsychOculusVR1-Info: Overriding onscreen window framebuffer size to 1136 x 1600 pixels for use with VR-HMD direct output mode.

PsychImaging-Info: Stereomode 12 required - Enabling it.

 

 

PTB-INFO: This is Psychtoolbox-3 for Microsoft Windows, under Matlab 64-Bit (Version 3.0.15 - Build date: Feb  7 2019).

PTB-INFO: Support status on this operating system release: Windows 10 (Version 10.0) supported and tested to some limited degree.

PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version information.

PTB-INFO: Most parts of the Psychtoolbox distribution are licensed to you under terms of the MIT License, with

PTB-INFO: some restrictions. See file 'License.txt' in the Psychtoolbox root folder for the exact licensing conditions.

 

PTB-INFO: Most graphics cards will not support proper syncing to vertical retrace when

PTB-INFO: running in windowed mode (non-fullscreen). If PTB aborts with 'Synchronization failure'

PTB-INFO: you can disable the sync test via call to Screen('Preference', 'SkipSyncTests', 2); .

PTB-INFO: You won't get proper stimulus onset timestamps though, so windowed mode may be of limited use.

 

 

PTB-INFO: OpenGL-Renderer is NVIDIA Corporation :: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 :: 4.6.0 NVIDIA 430.64

PTB-INFO: VBL startline = 1080 , VBL Endline = -1

PTB-INFO: Beamposition queries unsupported or defective on this system.

Using basic timestamping as fallback.

PTB-INFO: Timestamps returned by Screen('Flip') will be therefore less robust and accurate.

PTB-INFO: Measured monitor refresh interval from VBLsync = 0.000000 ms [inf Hz]. (0 valid samples taken, stddev=0.000000 ms.)

PTB-INFO: Reported monitor refresh interval from operating system =

6.944444 ms [144.000000 Hz].

PTB-INFO: Small deviations between reported values are normal and no reason to worry.

PTB-INFO: Stereo display via dual-stream stereo for special consumers with imaging pipeline enabled.

PTB-WARNING:

==============================================================================================================================

PTB-WARNING: WINDOWS DWM DESKTOP COMPOSITOR IS ACTIVE! ALL FLIP STIMULUS ONSET TIMESTAMPS WILL BE VERY LIKELY UNRELIABLE AND LESS ACCURATE!

PTB-WARNING: STIMULUS ONSET TIMING WILL BE UNRELIABLE AS WELL, AND GRAPHICS PERFORMANCE MAY BE SEVERELY REDUCED! STIMULUS IMAGES MAY NOT

PTB-WARNING: SHOW UP AT ALL! DO NOT USE THIS MODE FOR RUNNING REAL EXPERIMENT SESSIONS WITH ANY REQUIREMENTS FOR ACCURATE TIMING!

PTB-WARNING:

==============================================================================================================================

PTB-INFO: All display tests and calibrations disabled. Assuming a refresh interval of 144.000000 Hz. Timing will be inaccurate!

PTB-INFO: Using usercode override framebuffer rect [0, 0, 1136, 1600] for image processing.

PTB-INFO: Psychtoolbox imaging pipeline starting up for window with requested imagingmode 11535361 ...

PTB-INFO: Will use 8 bits per color component framebuffer for stimulus drawing.

PTB-INFO: Will use 8 bits per color component framebuffer for stimulus post-processing (if any).

PTB-INFO: No image processing needed. Enabling zero-copy redirected output mode.

PTB-INFO: Using external 2D npot-textures as sinks for redirected output mode.

PTB-INFO: Enabling sRGB rendering (= gamma ~2.2) into suitable framebuffers if supported.

PsychOculusVRCore1-INFO: Right eye swap chain created. Switching to stereo mode.

Error in function TextBounds:     Usage error The external text renderer plugin failed to render the text string for some reason!

 

 

INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline

INFO: a total of 2 times out of a total of 5 flips during this session.

 

INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system)

INFO: if you provided requested stimulus onset times with the 'when'

argument of Screen('Flip', window [, when]);

INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator

INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least

INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the

INFO: examples in the PDF presentation in PsychDocumentation/Psychtoolbox3-Slides.pdf for more info and timing tips.

 

 

 

WARNING: This session of your experiment was run by you with the setting Screen('Preference', 'SkipSyncTests', 2).

WARNING: This means that some internal self-tests and calibrations were skipped. Your stimulus presentation timing

WARNING: may have been wrong. This is fine for development and debugging of your experiment, but for running the real

WARNING: study, please make sure to set Screen('Preference', 'SkipSyncTests', 0) for maximum accuracy and reliability.

Error using Screen

Usage:

 

[normBoundsRect, offsetBoundsRect, textHeight, xAdvance] = Screen('TextBounds', windowPtr, text [,x] [,y] [,yPositionIsBaseline] [,swapTextDirection]);

 

Error in DrawFormattedText (line 315)

blankbounds = Screen('TextBounds', win, 'X', [], [], 1, righttoleft);

 

Error in VRHMDDemo (line 77)

      DrawFormattedText(win, sprintf('HELLO\nWORLD!\n%i', eye), 'center', 'center', [0 1 0]);

 

Try 2

 

>> SuperShapeDemo

PsychOculusVR1: Opening the first connected Oculus VR headset.

PsychOculusVRCore1-INFO: Opened Oculus Rift with deviceIndex 0 as handle 1.

PsychOculusVRCore1-INFO: Product: Oculus Rift CV1 - Manufacturer: Oculus VR - SerialNo: WMHD303J5010ED [VID: 0x2833 PID: 0x31]

PsychOculusVRCore1-INFO: Firmware version: 7.9

PsychOculusVRCore1-INFO: Panel size in pixels w x h = 2160 x 1200 - Refresh rate = 89.998001 fps

PsychOculusVRCore1-INFO: Caps: Debug device=0

PsychOculusVRCore1-INFO: Fields of view (Fov): [left, right, up, down] in degrees follow:

PsychOculusVRCore1-INFO: Max Left eye Fov:     [55.286181, 40.981596, 50.964488, 63.651332]

PsychOculusVRCore1-INFO: Max Right eye Fov:    [40.981596, 55.286181, 50.964488, 63.651332]

PsychOculusVRCore1-INFO: Def Left eye Fov:     [55.286181, 40.981596, 50.964488, 63.651332]

PsychOculusVRCore1-INFO: Def Right eye Fov:    [40.981596, 55.286181, 50.964488, 63.651332]

PsychOculusVRCore1-INFO:

----------------------------------------------------------------------------------

PsychOculusVR1-Info: Overriding onscreen window framebuffer size to 1344 x 1600 pixels for use with VR-HMD direct output mode.

PsychImaging-Info: Stereomode 12 required - Enabling it.

 

 

PTB-INFO: This is Psychtoolbox-3 for Microsoft Windows, under Matlab 64-Bit (Version 3.0.15 - Build date: Feb  7 2019).

PTB-INFO: Support status on this operating system release: Windows 10 (Version 10.0) supported and tested to some limited degree.

PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version information.

PTB-INFO: Most parts of the Psychtoolbox distribution are licensed to you under terms of the MIT License, with

PTB-INFO: some restrictions. See file 'License.txt' in the Psychtoolbox root folder for the exact licensing conditions.

 

 

 

PTB-INFO: OpenGL-Renderer is NVIDIA Corporation :: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 :: 4.6.0 NVIDIA 430.64

PTB-INFO: VBL startline = 1080 , VBL Endline = -1

PTB-INFO: Beamposition queries unsupported or defective on this system.

Using basic timestamping as fallback.

PTB-INFO: Timestamps returned by Screen('Flip') will be therefore less robust and accurate.

PTB-INFO: Measured monitor refresh interval from VBLsync = 0.000000 ms [inf Hz]. (0 valid samples taken, stddev=0.000000 ms.)

PTB-INFO: Reported monitor refresh interval from operating system =

6.944444 ms [144.000000 Hz].

PTB-INFO: Small deviations between reported values are normal and no reason to worry.

PTB-INFO: Stereo display via dual-stream stereo for special consumers with imaging pipeline enabled.

PTB-INFO: Support for OpenGL 3D graphics rendering enabled: depth-buffer and stencil buffer attached.

PTB-INFO:

==============================================================================================================================

PTB-INFO: WINDOWS DWM DESKTOP COMPOSITOR IS ACTIVE. On this Windows-10 or later system, Psychtoolbox can no longer reliably detect if

PTB-INFO: this will cause trouble for timing and integrity of visual stimuli or not. You might be just fine, or you could be in trouble.

PTB-INFO: Use external measurement equipment and independent procedures to verify reliability of timing if you care about proper timing.

PTB-INFO:

==============================================================================================================================

PTB-INFO: All display tests and calibrations disabled. Assuming a refresh interval of 144.000000 Hz. Timing will be inaccurate!

PTB-INFO: Using usercode override framebuffer rect [0, 0, 1344, 1600] for image processing.

PTB-INFO: Psychtoolbox imaging pipeline starting up for window with requested imagingmode 11535361 ...

PTB-INFO: Will use 8 bits per color component framebuffer for stimulus drawing.

PTB-INFO: Will use 8 bits per color component framebuffer for stimulus post-processing (if any).

PTB-INFO: No image processing needed. Enabling zero-copy redirected output mode.

PTB-INFO: Using external 2D npot-textures as sinks for redirected output mode.

PTB-INFO: Enabling sRGB rendering (= gamma ~2.2) into suitable framebuffers if supported.

PsychOculusVRCore1-INFO: Right eye swap chain created. Switching to stereo mode.

PTB-ERROR: Setting wglSwapInterval(1) failed! Expect severe display timing and display tearing problems!!! See 'help SyncTrouble' for more info.

PTB-ERROR: Mismatch between requested display swap interval 1 and actual swap interval 0! Synchronization of Screen('Flip') to display refresh will likely malfunction!

PTB-ERROR: This is either a bug in your graphics driver or system setup, or some misconfiguration in the display setting control panel of your system. See 'help SyncTrouble' for more info.

PTB-ERROR: Setting wglSwapInterval(1) failed! Expect severe display timing and display tearing problems!!! See 'help SyncTrouble' for more info.

PTB-ERROR: Mismatch between requested display swap interval 1 and actual swap interval 0! Synchronization of Screen('Flip') to display refresh will likely malfunction!

PTB-ERROR: This is either a bug in your graphics driver or system setup, or some misconfiguration in the display setting control panel of your system. See 'help SyncTrouble' for more info.

PTB-ERROR: Setting wglSwapInterval(1) failed! Expect severe display timing and display tearing problems!!! See 'help SyncTrouble' for more info.

PTB-ERROR: Mismatch between requested display swap interval 1 and actual swap interval 0! Synchronization of Screen('Flip') to display refresh will likely malfunction!

PTB-ERROR: This is either a bug in your graphics driver or system setup, or some misconfiguration in the display setting control panel of your system. See 'help SyncTrouble' for more info.

Error using RectHeight (line 15)

Wrong size rect argument. Usage:  height = RectHeight(rect)

 

Error in DrawFormattedText (line 295)

    theight = RectHeight(Screen('TextSize', win) * vSpacing);

 

Error in SuperShapeDemo (line 67)

DrawFormattedText(win, 'Hang on, I am working on my first supershape :)', 'center', 'center');

 

>>

PTB-INFO: Enforcing script abortion and restoring desktop by executing

Screen('CloseAll') now!

PTB-INFO: Please ignore the false error message (INTERNAL PSYCHTOOLBOX

ERROR) caused by this...

 

 

 

 

Hello,

An ex-colleague left 2 CV1’s at our department when he left. I had given it a try back in 2017 (win7, matlab 2016, ptb3?), but the drivers did not work with ptb then. Now, 5 years later, I felt like checking back (win10, matlab2022)… Apparently, oculus’ 1.7 runtime no longer supports the mode in which ptb would utilize the stereo display… I cannot find any older runtime installers. I would love to play around with a head-mounted display, but I probably will not be able.

Any suggestions?

András

This was tested on Win10 only a few months ago with up to date Oculus install and worked fine on my CV1.

Also please don’t hijack only loosely related discussion threads for unrelated questions. I will close this topic for further discussions.

-mario