ovr_sdk
annotate LINUX_README @ 0:1b39a1b46319
initial 0.4.4
| author | John Tsiombikas <nuclear@member.fsf.org> |
|---|---|
| date | Wed, 14 Jan 2015 06:51:16 +0200 |
| parents | |
| children |
| rev | line source |
|---|---|
| nuclear@0 | 1 WHAT SETUP IS REQUIRED? |
| nuclear@0 | 2 |
| nuclear@0 | 3 * Appropriate permissions for Oculus hidraw devices. See |
| nuclear@0 | 4 LibOVR/90-oculus.rules and ConfigureDebian.sh. |
| nuclear@0 | 5 * Use a multihead setup with one X screen spanning both displays (such as |
| nuclear@0 | 6 NVidia TwinView) or place the rift on an independent X screen. |
| nuclear@0 | 7 * Ensure oculusd is running when using the rift. |
| nuclear@0 | 8 |
| nuclear@0 | 9 BUILD INSTRUCTIONS |
| nuclear@0 | 10 |
| nuclear@0 | 11 After installing the appropriate packages issue 'make' in the root of |
| nuclear@0 | 12 the SDK directory. This will build a release version of Oculus World Demo |
| nuclear@0 | 13 (OWD). To generate debug symbols use 'make DEBUG=1'. |
| nuclear@0 | 14 |
| nuclear@0 | 15 HOW DO I RUN OCULUS WORLD DEMO (OWD)? |
| nuclear@0 | 16 |
| nuclear@0 | 17 Either run the binary directly from the output directory, or use 'make run'. |
| nuclear@0 | 18 |
| nuclear@0 | 19 SHOULD I ROTATE MY DEVICE'S SCREEN? |
| nuclear@0 | 20 |
| nuclear@0 | 21 Manual screen rotation is not recommended. If your window is fullscreen on a |
| nuclear@0 | 22 rift device, set the ovrDistortionCap_LinuxDevFullscreen distortion cap to |
| nuclear@0 | 23 have the SDK automatically rotate the distortion mesh on appropriate devices. |
| nuclear@0 | 24 Be aware you will have to account for window size. You can use |
| nuclear@0 | 25 OVR::SDKWindow::findDevScreenForHMD (Displays/OVR_Linux_SDKWindow.h) to |
| nuclear@0 | 26 return the screen offset and dimensions necessary to size your Linux window. |
| nuclear@0 | 27 See Samples/CommonSrc/Platform/Linux_Platform.cpp for an example. |
| nuclear@0 | 28 |
| nuclear@0 | 29 TWINVIEW |
| nuclear@0 | 30 |
| nuclear@0 | 31 You must sync to the Rift's display device for a smooth experience when using |
| nuclear@0 | 32 TwinView. To consistently sync to the rift with TwinView setups, set the |
| nuclear@0 | 33 __GL_SYNC_DISPLAY_DEVICE environment variable to the appropriate display |
| nuclear@0 | 34 device before X starts. For example in your /etc/profile you could place the |
| nuclear@0 | 35 following: |
| nuclear@0 | 36 |
| nuclear@0 | 37 export __GL_SYNC_DISPLAY_DEVICE="DFP-1" |
| nuclear@0 | 38 |
| nuclear@0 | 39 if your rift corresponds to DFP-1. |
| nuclear@0 | 40 |
| nuclear@0 | 41 STARTING THE TRACKING SERVICE AUTOMATICALLY |
| nuclear@0 | 42 |
| nuclear@0 | 43 Start the tracking service when a user is logged in using Xsession files. |
| nuclear@0 | 44 |
| nuclear@0 | 45 UBUNTU USERS |
| nuclear@0 | 46 |
| nuclear@0 | 47 There was a ubuntu-specific kernel bug which affected HID devices in 14.04. |
| nuclear@0 | 48 If you are receiving feature report failures try upgrading your distro |
| nuclear@0 | 49 (dist-upgrade). |
| nuclear@0 | 50 |
| nuclear@0 | 51 KNOWN ISSUES |
| nuclear@0 | 52 |
| nuclear@0 | 53 * OWD vsync initially disabled on Radeon proprietary. |
| nuclear@0 | 54 * Frame loss on NVidia TwinView setups. Use an independent X screen for an |
| nuclear@0 | 55 optimal experience. |
| nuclear@0 | 56 * Mesa DK2 latency tester does not function properly in OWD. |
| nuclear@0 | 57 |