Search Results for 'directvr'

[moarveer]

that’s AWESOME! I’m a big fan of Borderlands but I hadn’t tried Borderlands 3 since I wanted to play it VR but it was expensive. Now after reading this I’ve used the 10 euro coupon of EGS with Borderlands 3 and got it for 9,79 euro, really sweet for a game that can easily give you 30-40 hours of gameplay with the base game alone.

I can’t thank you enough Ralf, this kind of product support is incredible, no matter if any of those improvements get into the game, for you to even check it out and see if it can be improved is great.

Even if DirectVR doesn’t end making it into the profile, it was still good enough as it was so I will play it anyway in VR, however I really hope you can make DirectVR and FOV work. The thing is that after testing B3, when I go back to Bioshock Infinite DLC and play with perfectly smooth VR, no shaky cam effect, how easy is to forget how amazing DirectVR is.

[Ralf]

Thanks for the FOV hint. Not sure why, but looks like the profile is borked in that respect. ‘Letterbox 1’ is a little bit too much, the ideal settings would be aspect at ‘Pixel 1:1’ and ImageZoom at 0.68. I’ll adjust the defaults for the next update.

I halso have DirectVR tracking working. Needs a bit more testing to make sure it works in more than one spot, but I’m 90% sure that won’t be an issue, that should allow you use G3D without a super higend GPU.

An update with the updated profile will be released early next week.

[Zel1984]

Neither, DirectVR mode.

[CrazyDolphin]

Update:
– Bioshock 2:Vanilla continues to be a pain in the tuckus (repeatedly crashing at random times).
– I downloaded Bioshock 2 Remastered, plain in desktop first, then applied the default VorpX profile. The game wouldn’t reliably hook, so I had to use ‘Hook Helper’ to get the game to boot up.

Results of playing the Remastered game so far:
– One one crash in 3 hours of playing (yay!).
– The graphics are not as good as the vanilla version, and the scale is a bit off (my weapons are larger and I feel like I’m short in the game. I did increase my height via VorpX.
– Going to the next level in the game causes me to redo DirectVR (which can take a couple of times).

I do miss the cleaner graphics and more accurate scale of my character in the Vanilla version, but at least the game reliably operates, for myself, in the Remastered version.

If anybody does have any hints on how I can make the Vanilla version work more reliably, please let me know.

[moarveer]

For anyone interested the game is free to try this weekend on Steam, I checked it out and it hooked fine. Set it up to max res on Vorpx, FSR works at high and overall the game looks great, performance is not too good in geo3d as expected, but quite playable in z3d, slowly i’m starting to get used to z3d, it’s pretty solid and performance is just on another level, even though nothing beats geo3d for real depth and scale.

The only “bad” thing is that I’m completely spoiled with direcVR tracking, and since afaik Borderlands 3 doesn’t support it, there’s always some short of small shaky cam effect and no amount of mouse sensitivy tweaking seems to fix it. It’s playable but DirectVR tracking is just too good.

I had to use Letterbox 1 since it was too zoomed in for my liking even after setting FOV to max as suggested by the profile, and with letterbox 1 it’s basically perfect.

There’s an interesting tool called Unreal 4 engine unlocker that lets you access the console and set FOV by injecting the dll to the game: https://framedsc.github.io/GeneralGuides/universal_ue4_consoleunlocker.htm I gave it a try but didn’t work too well with Vorpx when activated, maybe someone will have better luck.

Overall pretty good, but since Borderlands 2 got a VR version, i thill i’ll hold since maybe PSVR2 for PS5 could get a B3 VR version, we’ll see.

[madcap]

I’m having the exact same issue with the new weapon fov/hide feature with Black Mesa. I tried reinstalling the game, restoring settings and profiles, even restoring Vorpx to factory default settings and it didn’t work. The only way to get it to work is by lowering Image Scale in Vorpx to exactly 0.90 from its default 1.0. It doesn’t appear to be impacting the world fov too much whilst still using the cached directVR. There is still a slight positional flicker with the gun, but it’s a hell of a lot better than having a 6 foot gun.

[CrazyDolphin]

Currently playing on a i7-8700, 16GB RAM. GTX1070Ti. Observations are as follows:
– I did play the Steam version of the game on a monitor briefly before applying the VorpX profile. I am using the default VorpX profile .
– In FullVR, I am getting inverted head tracking (if my head turns left, the image goes right, etc).
– Attempting DirectVR Scanning results in a failure 99.9% of the time (1 time the DirectVR scan worked, but the game crashed with a few seconds).
– I try to invert the X and Y axis tracking under the Helmet Tracking sub-menu, but it does not change anything.

Now Immersive and Cinema Mode works just fine, but my biggest joy comes from the FullVR mode.
Has anybody gotten the head tracking to work properly, and if so, could you please let me know how you did it?

Thanks for listening.

[Mazzle]

G3D immediately and completely corrupts the video for me. Video was just a bunch of colored horizontal lines. I was surprised it didn’t crash. I’m not sure why the profile says it’s G3D compatible and works with DirectVR scanning.

Z3d looks great from the 10 minutes I played. I saw a bit of ghosting on some characters, but it was pretty minor.

[Ralf]

Please check whether the same happens happens when you switch to SteamVR. Also if you happen to have the WMR developer tools installed, please always make sure to NOT use the developer version of the OpenXR runtime. Always use the stable release build.

As far as Bioshock Infinite is concerned, please make sure to set the FOV slider to max in the game options as suggested by the message shown in the top/left corner of the game window. Otherwise vorpX can’t set the FOV right. The DirectVR scan may fail occasionally unfortunately. Scanning through a game’s memory to find single a addresses for head tracking is a fairly complex process. There is no 100% guarantee that it always succeeds. Hence the message in that respect that is shown during each scan.

[Ralf]

Sounds as if the scanner might have picked up a wrong address. Please try to empty the cache in the vorpX menu (‘DirectVR’) and run the scanner again.

[Ralf]

Unfortunately there is no margin for what the right FOV is in FullVR mode, there only is one. The game FOV has to precisely match the headset FOV, any deviation from that causes distortion, either in the form of a zoomed in image or the opposite.

First please make sure to run games at 4:3 resolutions (e.g. 1600×1200, 1920×1440, 2400×1800) in FullVR mode whenever possible. Or even one the ‘Narrow’ resolutions from the recommended custom resolutions list if a game works with them. Weapons being entirely out of sight usually is a sign of using a widescreen res, which in FullVR mode unnecessarily renders pixels that never show up in the headset.

If that doesn’t help and you are willing to live with the distortion mentioned above, you can apply an up to 20° FOV offset on the DirectVR page of the vorpX menu.

Alternatively use the ImageZoom option. That preserves the right FOV, but introduces black top/bottom bars.

Caveat: Depending on how vorpX handles FOV for a game, changing FOV related options may require a game restart, so make sure to read any notifications that might get shown in that respect.

[Ralf]

Please reset the profile to default and don’t do anything except selecting a resolution quality on the DirectVR page of the vorpX menu that works for you performance wise. vorpX handles everything automatically.

Since a few versions it even comes with a dedicated mod for the game that provides perfect 1:1 headtracking, decoupled walk/look/aim, auto switching to EdgePeek in cutscenes and menu screens for improved comfort, and unique VR optimized cameras that get rid of nauseating head bobbing and whenever possible the equally nauseating moments where the games briefly take away control, e.g. when entering a car.

[Ralf]

Just saw this. The option is on the DirectVR page of the vorpX menu.

BTW: probably of no interest for you, but there is also an option to *try* a vertical lock in games without DirectVR head tracking. That can be found on the Input page of the menu.

[Ticlon]

Hello community,

I am experiencing issues with running a freshly installed (Steam) copy of GTA V with vorpX 21.2.3 and Valve Index controllers. I did not change the default profile, as such I assume I use the new profile with the vorpX connection mod.

The game crashes shortly after starting the game when my Valve Index controllers connected to SteamVR already. If I connect one of the controllers with the game already running it crashes shortly after. Both crashes occur without error message nor crash report.

The crashes also happen if I change the default controller type in the vorpX settings.

Running another DirectVR game (Fallout 4) works fine, including using the Index controllers. Starting GTA V and beginning the story works fine when my controllers are not connected, too, though I cannot use mouse and keyboard controls to control my character. Both work fine in the GTA V menu/settings/map, so I assume locking the controls during playing is intended?

Has anyone a hint how to fix this problem or how to go on troubleshooting?

Thank you in advance!

[Ralf]

Can’t replicate that here, but in case you haven’t done that already, try to save the settings without vorpX first.

On a sidenote: Make sure to run the DirectVR memory scanner for better head tracking and automated FOV setup. If you happen to use the Remastered version, try the original Bioshock if possible. DirectVR support is a tad bit better with the original version.