08-14-2014 12:53 PM
It uses SDK 0.4.1
The SteamVR Beta has been updated with the following changes.
General:
Added support for Rift Dev Kit 2 HMDs. Positional tracking is supported on Windows and OSX.
Fixed some cases where vrserver would stay running whenever Steam was running.
Fixed cases where vrserver would start to consume CPU over time.
Windows:
vrserver.exe will no longer run on machines that don’t have a VR HMD connected.
Known Issues:
Positional Tracking on the DK2 does not work on Linux
If the Oculus OVRService_*.exe is not running but an HMD is attached calls to init SteamVR will take a few seconds to return failure.
Only “Extend Desktop” mode is supported.
08-22-2014 12:56 AM
"rupy" wrote:
Yes, but what about when the background (= 3D stuff) renders all black and the resolution is wrong?
08-22-2014 01:29 AM
"Simpanra" wrote:"firstdayreviews" wrote:
Yeah im stuck, ive followed 5 sets of instructions.
I have steam VR (big picture mode) which works great, I can launch HL2 VR from here...
Problem is, once ive launched HL2 I CANNOT enable VR mode under the "Video" section, the drop box is just greyed out saying "No HMD Detected"
What the hell am i doing wrong?
(Keep in mind ive followed every guide in this thread already)
Just to absolutely clarify;
You get to SteamVR, it works fine, you go to HL2, it should say "Play in VR" but it sounds to me like it says "Play in 2d" to you? (if it says the VR option then it is working just fine and you just need to start playing, if not then continue reading).
So if you are reading this far then it says play in 2d,
Quit SteamVR.
Make sure your launch options for HL2 are set to -vr,
make sure both HL2 and SteamVR are opted into the beta builds,
make sure that steam itself is in beta,
if all of that fails, also make sure that in display mode you are set to extended WITH dk1 legacy enabled.
If SteamVR still says "Play in 2d" then run HL2 from normal steam with the -vr launch option and you should be able to change the setting to VR mode in game from there, then restart HL2 and see if it works. If it now works you can launch it from SteamVR from now on.
Hope this helps! 😄
08-22-2014 01:33 AM
"firstdayreviews" wrote:
Nope says "PLAY IN VR" but still have no option to enable VR mode, try all the launcher (-vr -Console) Im in every beta that steam has to offer, ive tried extended, direct, primary secondary, disable OVR enable OVR....
No idea
08-22-2014 02:38 AM
"Simpanra" wrote:"rupy" wrote:
Yes, but what about when the background (= 3D stuff) renders all black and the resolution is wrong?
That is normal in the menu, you have to try loading into the game, like a level.
Also somebody else I spoke to said they spent some time on the menu playing with graphics settings and when they changed AA and Ambient Occlusion it just fixed it.
08-22-2014 12:45 PM
"Simpanra" wrote:"firstdayreviews" wrote:
Nope says "PLAY IN VR" but still have no option to enable VR mode, try all the launcher (-vr -Console) Im in every beta that steam has to offer, ive tried extended, direct, primary secondary, disable OVR enable OVR....
No idea
If it says play in VR then it is working, go to the menu -Which is 2D- start a new game -2D cutscene- and then spawn on the train -2D for about 10 seconds- and then it flashes and you are in full 3D ^^
08-22-2014 06:31 PM
08-22-2014 10:19 PM
08-22-2014 10:53 PM
08-22-2014 11:41 PM
08-23-2014 02:02 AM
"Quixote" wrote:
From Reddit:
For those who have tried other suggestions and still cannot get it to work: The game may be defaulting to Directx 8. In my developer console, I found the following message: VR mode does not work with DirectX8. Please use at least "-dxlevel 90" or higher. To change your directx settings, you'll need to modify your launch options: In Steam, go to your games and right-click Half-Life 2 [Beta] Select Properties In properties window (General Tab) click on 'Set Launch Options...' Add the following launch option: -autoconfig You should now be able to enable vr in options. If it is still greyed-out, click the 'Advanced..." button and verify that you are using DX9.0 or above. If not, then instead of the '-autoconfig' launch option, try using '-dxlevel 90' to force it.
This sorted it all out for me...