Forum Replies Created
-
Posts
-
For now please use mouse and keyboard. The issue is confirmed, but not resolved yet. A supposedly working workaround is using an external gamepad emulation tool like Xpadder. Hasn’t been tested here though.
Please make sure to apply the Game Optimizer setting for VLC in the vorpX config app. That should solve this. The optimizer sets the VLC video output to OpenGL which works better in this regard.
Alternatively you can switch the video to fullscreen to make it show correctly in vorpX if you want to use the default D3D output for some reason.
Does the same thing happen when you use the ingame menu with the keyboard (cursor keys for navigation, ENTER to commit)? It’s just a guess, but this might be a mouse focus issue. Sometimes the mirror window freezes when the main window loses focus.
Apart from a GeForce 850m being clearly too slow for many newer games with vorpX, laptops in general are not officially supported anymore by Oculus since runtime 0.7.
Please send a mail to support |at| vorpx com requesting an older vorpX version. For cases like yours we can provide a version that uses the Oculus runtime 0.5, which has better compatibility with laptops.
Use a 16:10 res if possible (e.g. 1920×1200). With that the top/bottom bars after using the ImageZoom are small enough to be entirely forgotten within minutes while playing. Not playing this one because of such a minor quirk is a crime.
You can use the vorpX ImageZoom to compensate for FOV like described above. Works quite well as the game’s original FOV isn’t too low. After seeing this thread, and since I really liked the game when it came out, I played it quite a while myself this weekend. It’s a very good fit for VR and definitely deserved to be a lot more successful than it actually was.
BTW: While being at it I added HUD scaling and recalibrated the 3d strength to a better default value. Will be available with the next vorpX version.
Did you read the FAQ above? Please send a mail with your new request to support |at| vorpx com or the mail address in the license dialog.
The performance hit of the Fallout 4 G3D profile is ~50% compared to Z3D. You’ll need an *extremely* beefy machine to make this at least barely playable, and even with that it’s far from ideal. Even the fastest machines available today have to rely on async timewarp heavily, which is not how things should be.
With the recommended Oculus specs (decent i5/i7, GTX 970) and medium settings it’s halfway playable in most interiors (>45fps raw performance), but often dips below 30fps outside (in some parts of the map even below 20fps), which isn’t really enough even with async timewarp. For comparison: 75fps are ideal for DK2, 90fps for CV1. A faster GPU helps, but not as much as one would think. As with all Bethesda RPGs, the CPU is as much a limiting factor as the GPU.
I don’t have a date yet for the next vorpX version that will include this, but there probably (BUT NOT NECESSARILY!) will be another update before the CV1 is released.
That is only possible under special circumstances. Please send a mail to support |at| vorpx com for further information.
No, vorpX does not work with OSVR yet. It’s on the list, but there is no timeline set for when it will be available.
vorpX 0.9.1 still works with the DK1, but we are not developing or testing for it anymore, which means there are no guarantees that future versions will also work with it.
Please read the Essential Game Hints in the vorpX help. Among other important information there you find all possible ways that vorpX offers to deal with the field of view (“zoomed in”).
For Portal 2 that is particularly easy as all you have to do is to apply the Game Optimizer tweaks for Portal 2 (vorpX config app).
Can’t say anything in regard to HUD scaling, sorry. I assumed I had done that already, but apparently didn’t (hence the non working optimizer profile).
In BF4 there are GstRender.ScreenSafeAreaHeight and GstRender.ScreenSafeAreaWidth in the config file which can be used to move the HUD, but those don’t seem to be present in the Battlefront config.
Adding those values might be worth a try, but I suspect it’s not possible in Battlefront since they aren’t present per default. I will look into it, but can’t do this right now.
BTW: A way to work around a non-scalable HUD is often the use of a 4:3 res like 1600×1200 (or ideally a 8:9 custom res), which also can improve performance. That’s always at least worth a try.
No hotkey for disabling head tracking, but that’s a good idea. Probably only makes sense in rare cases, but would certainly help here.