Forum Replies Created
-
Posts
-
Rise of the Tomb Raider seems to be another victim of recent updates adding openvr_api.dll to it’s directory. This disables steamvr access somehow.
Unlike with the Source games, removing the dll in this case refuses to launch the game at all. Again, probably something to look into if this trend among games continues.
Fortunately, I encountered a workaround from a post mentioning that RotTR is one of the few games on steam that lets you roll back to previous game versions. I gave this a try and it seems to work just fine.
Right click the game in steam for properties, go to Betas tab, and choose a build (I chose recommended 753.2).
After a quick update (that also happens to remove that pesky dll), vorpX should hook fine.
Hopefully the new TR coming this week will work ok. Looking forward to it.
It seems Valve have been updating openvr parameters for launcing their games recently (a sign of native vr support in the future??), forcing them to close when steamvr is active.
Hopefully Ralf can take a closer look into this, might be a simple line of code.
Until then, I’ve discovered that by simply renaming “openvr_api.dll” to something else like “XXopenvr_api.dll”, you can get the game to launch in the headset.
Steam\steamapps\common\Black Mesa\bin openvr_api.dll
Give that a try. Now I’ve got to figure out where my game saves went, as it wants me to start over after a cloud sync :/
Oh yeah! Just tried G3D Main Eye right on Insurgency, Farcry 2, Arma 3, Red Orchestra 2, and Fallout 4, and they all worked beautifully.
Aiming feels more natural now, just as I had hoped. Thanks again for this. Very useful!
@olistreet – Maybe you just need to turn up the headtracking sensitivity in the vorpX menu. Push the Delete key while in game and experiment with higher values on the headtracking slider. If it’s not on the front page, arrow through to the tracking page.
Just adding that my testing also returns a “could not initialize” error for RotTR, though It was working fine earlier this year.
Figured I’d give Firewatch a go finally, but none of the 3D options appear to work. Perhaps this years patch done messed it again.
Just a heads up. If it’s a simple fix, let us know. Thanks.
Make sure you’re playing the original Bioshock (DirectX9 version).
The Remastered versions only work in 2D as you describe.
Rising Storm 2 uses EAC (Easy Anti Cheat), which blocks vorpX injection :(
It’s a shame, because otherwise it probably would have worked pretty well.
Sorry man, I wanted this as well.
Yep I’ve been using this trick, thank you. But ArmA showed me that it looks cooler in 3D :)
Just wondered is all, if nothing difficult.
On the note of camera height, I’ve wondered recently playing a lot of shooters in G3D, if a side to side camera adjust could be beneficial as well – for more natural ironsights.
Other than performance cost, the awkward cross-eyed sights are the only thing that bother me about G3D. If there were a way to snap the actual center to a preferred eye by toggle, or manually adjust the camera sideways same as height, perhaps this could be alleviated.
I realize this might include the same danger of artifacts as changing height, might not even line up at perfect angles even. Could still be a useful option to mess with.
It’s neat how in some games with positional tracking like ArmA, you can physically lean to one side to use the sights more naturally, but most games the gun is glued to your face, so you can’t.
This is what was said reguarding former NMS updates.
But who knows, the NEXT update seems to change a lot graphically, maybe we’ll get lucky.
I used to play DoDS just fine with vorpX a year ago, though in testing today I get the same result as you. Game attempts to load, but stops seconds later. Starts fine without vorpX.
I think there is a conflict with recent updates to either the HL2 profile, or the game itself (had a game update today even).
After messing around some, I found error calls to sourcevr.dll found in the “Day of Defeat Source\bin” folder. So I simply removed sourcevr.dll to an external folder, and was able to hook with vorpX.
(Steam may attempt to reinstall the dll upon launch, but so far I’ve only had to remove it twice and it has stopped)I’ve learned that you must launch DoDS through steam client to get servers to show in the browser. Launching via hl2.exe directly wont populate the browser.
I am unsure about DirectVR at this point, but can say that the game can hook with working Geometry 3D. You just might need to do some scale and fov adjusting in game.
Having a wide enough Field of View is important to avoid getting dizzy. Running a DirectVR scan during gameplay can help this if available. Otherwise you’ll need to find ways to greatly increase FOV in a games settings.
Battlefront 2 has FOV slider in the video options. For fullVR you generally want it somewhere between 100-130.
If you are still having trouble getting used to the headtracking of FullVR mode, maybe try out the cinema modes from the Delete key menu to see how that feels. You can adjust the size of the screen, and also the strength of the 3D depth and still get an immersive experience. There are also sliders for sharpness and brightness, this can help make it less blurry.
If you want an example of this, search my name on the Cloud Profiles of vorpX config app and import my SWBF2 profile (not the beta one). In game set FOV around 95 and see if it feels ok.
Sounding like you might need to get the vive setup fully first, base stations included. Run SteamVR room setup and try some native vr games (like The Lab).
Lets make sure your vive is working as intended before fiddling with vorpX. Don’t forget to close vorpX before testing native vr games.
Turn off all monitoring programs like afterburner, evga precision, fraps etc.