Forum Discussion
DK2 as Single Display on Startup
Hey everyone,
I'm trying to create a setup with the DK2 attached as a single display.
The build consists of an Intel NUC5i5RYH the DK2 and some peripherals (keyboard and mouse, headphones). The HMD is connected through USB and an HDMI to Mini-HDMI adapter. On the software level, the computer is running Windows 8.1 with the 0.4.4 Oculus runtime and latest stock Intel HD6000 display driver. The system starts up by simply loading Windows to desktop and running a small batch file which waits 30 seconds and runs the application (just an uneducated guess, waiting for the Oculus runtime service to initialize).
Now, to the problem at hand -
When starting the system with a secondary display attached, everything works as expected.
When doing the same as above and disconnecting the secondary display after Windows loads, everything still works as expected.
The problem starts when trying to launch the system with only the DK2 connected - in this scenario the display on the HMD never turns on (only the orange power indicator led), no matter if the display is set to Direct to Rift or Extended Mode.
I'm pretty stuck at this point - would appreciate any feedback or ideas on how to troubleshoot and resolve this.
Thanks!
I'm trying to create a setup with the DK2 attached as a single display.
The build consists of an Intel NUC5i5RYH the DK2 and some peripherals (keyboard and mouse, headphones). The HMD is connected through USB and an HDMI to Mini-HDMI adapter. On the software level, the computer is running Windows 8.1 with the 0.4.4 Oculus runtime and latest stock Intel HD6000 display driver. The system starts up by simply loading Windows to desktop and running a small batch file which waits 30 seconds and runs the application (just an uneducated guess, waiting for the Oculus runtime service to initialize).
Now, to the problem at hand -
When starting the system with a secondary display attached, everything works as expected.
When doing the same as above and disconnecting the secondary display after Windows loads, everything still works as expected.
The problem starts when trying to launch the system with only the DK2 connected - in this scenario the display on the HMD never turns on (only the orange power indicator led), no matter if the display is set to Direct to Rift or Extended Mode.
I'm pretty stuck at this point - would appreciate any feedback or ideas on how to troubleshoot and resolve this.
Thanks!
1 Reply
- The problem you are having is you need a display attached for the dk2 to work properly, or atleast you need the computer to think there is a display connected. https://www.headlessghost.com/ With that device plugged into a computer the computer thinks that a display is connected basically. Then you can run virtual desktop, and set it up so it runs on start-up. Launch your demo from virtual desktop, and boom you have your hmd only demo box. Virtual desktop may be unnecessary for what you need, but it will sure save you alot of headache using the desktop to launch your demo. Direct to rift works best in that scenario as well, since virtual desktop does not do full screen extended mode with games.
