Forum Replies Created
-
Posts
-
Extended mode has long been deprecated. The DK2 should work in Direct Mode with the latest Oculus Software, it definitely did until quite recently. Oculus Home will show a warning that you use an unsupported headset, but that can be ignored.
If you have an older beta Oculus runtime installed (e.g. 0.8), make sure to remove it before reinstalling the Oculus software.
The obvious thing first: double check whether you have selected “Steam VR (HTC Vive)” as your headset type in the config app.
If that is the case and vorpX still does not hook into any game, there almost certainly is an injection conflict with some other program on your PC. The most likely candidates are virus scanners, any sort of GPU/CPU utility, video recording software, chat programs and generally everything that can show notifications/overlays in games.
Best way to trouble shoot is disabling all programs running in the background and then add them back one by one to see what’s the culprit. If you use anything else than Windows Defender, consider the virus scanner the most likely troublemaker by far.
@ dborosev: If you like platformers, get Ori and the Blind Forest. You’re in for a treat. This game looks absolutely stunning in 3D right in front of you, which alone was enough to make me play quite a while longer than I had to for creating the profile although I rarely play platformers normally.
My personal ‘insider tip’ for this release. Of course finding something beautiful or not is always a quite subjective matter, so maybe check a video or two first.
Please send your key request using the same mail address that you used to originally activate vorpX.
You’ll be able to disable it, but there isn’t really any reason to do so (except maybe potential trouble shooting). The new optimizer system let’s you choose a preferred quality in the DirectVR settings, vorpX then figures out the best resolution fitting this quality preset that is supported by your machine and the game.
To take full advantage of that some custom resolutions should be added in the graphics driver control panel. Which ones is explained in the help and you will be prompted to do so when you select a currently unsupported desired quality.
The FOV resetting after talking to an NPC is the one remaining annoyance with the game. [ALT][V] automatically types in the console command, so it’s not too bad. For playing standing map [ALT][V] to your controller and that shouldn’t be much of an issue anymore. IIRC that should work already with vorpX 17.2, but the auto typed FOV probably isn’t correct currently.
The previous cinema mode on/off setting is now called “Play Style” with the options “Full VR”, “Immersive Screen Mode” and “Cinema Mode”. If mentioned in the changelog for a game, that refers to what I think makes most sense and thus is selected as the default option.
@ markbradley1982 : like steph12 says, quite a few improvements for Oblivion incoming this weekend (see below). If you don’t want to wait: the correct FOV with default vorpX settings is 112.
1. Tree shadows are fully correct now.
2. Fire/torches rendered at correct depth now.
3. Mouse wheel block: no unwanted changes to 3rd person which messed up FOV.
4. Some ini tweaks: e.g. dialog camera doesn’t zoom in ultra close anymore.
5. HUD/menu scaling added.
6. Custom resolution auto-set via DirectVR.
7. FOV auto set after Direct VR scan.This can happen from time to time, but usually should go away when you try two or three times. If that is not the case I would suspect an injection conflict. Most likely a virus scanner (don’t use anything else than Windows Defender), but also any other tool that hooks into games might cause this.
What quisutdeus meant was the SW:BF1 profile in the vorpX config app. You can clone profiles on the “Local Profiles” page of the config app and assign unknown programs to such a cloned profile.
The next vorpX version will come with a SW:BF2 profile preinstalled. If you feel unsure how to do the above, just wait a week for the update. It’s quite easy though, so no harm in trying yourself.
There will be a better official list when the next vorpX version is finally out of the door, promise.
What I forgot to mention is that there also is a three step ‘quick and dirty’ setup explained in the help. That usually doesn’t provide the best possible result, but it’s a good way to hop into non-Direct VR games as fast as possible. Not perfect, but quite useful for checking things out.
Did you check the “Essential Hints” guide in the vorpX help? It explains the essential basics you have to know, e.g. what options you have if vorpX can’t automatically adjust the FOV for a game. Reading this guide really is essential (hence its name :) ).
Apart from that I would suggest to try Direct VR games first, which do everything automatically, so you just have to push a button after entering the game. Save the ones that require manual steps for later when you know a bit better how vorpX works.
BTW: the next vorpX version will have auto FOV for about 40 more games.
Good games to start are (in no particular order):
Skyrim (original DX9 version is usually the better choice)
Fallout 3
Fallout New Vegas
Fallout 4
Portal
Portal 2
Left 4 Dead 2
Mirror’s Edge
Bioshock (DX9)
Bioshock 2 (DX9)
Bioshock Infinite
Borderlands 2
Borderlands Pre-Sequel
Dishonored
Deus Ex Human Revolutions
Black Mesa Source
Half-Life 2
Half-Life 2 Episode 1
Half-Life 2 Episode 2
Aliens Colonial Marines
Dear Esther (Source engine version)
The Stanley ParablePlease try to exclude ‘home2-win64-shipping.exe’. That appears to be the actual new home environment .exe. The easiest way to do that is to use the ‘Add Process’ button in the config app while the new Oculus Home is running.
You can disable Direct VR temporarily with a hotkey (freely configurable in the config app). The second option is to disable the positional part of Direct VR in the vorpX menu, normal pos tracking wil kick in instead. For playing seated or standing without walking that works just as well.
Smaller than 16:10 aspect ratios cause various UI glitches with or without vorpX, that’s a general game issue. There is a neat trick though to get close to 4:3 by adding a few pixels to the width. 1604×1200 for example does work. The next vorpX will do this fully automated.
Only the original Dear Esther is supported by vorpX. That probably won’t change with the next update, sorry.
Skyrim SE you can fix yourself right now by disabling the gamepad, which makes the scanner more reliable. With the next vorpX that won’t be necessary anymore.
The rest of the answers is true for the next vorpX version and for unmodded games, so if in doubt, remove any mods.
There never was any ‘uncorrect perspective’ issue with GTA V though except the too strong 3D in vehicles.
RE7 works quite well without any mod, everything is (and always was) configured automatically. Slight top/bottom bars to account for a bit of missing FOV, but nothing too offensive. Make sure to restore the profile to default in the config app if you adjusted settings for use with an FOV mod before.
Not sure about your config app issue in the other VR desktop apps. Works fine with the vorpX desktop viewer.
Gone Home: fixed, + new auto FOV via ini change.
Fear: no auto FOV of any kind currently (never has been), apparently there is way via an ini edit, I’ll check whether that can be automated.
Skyrim SE: IIRC there was some glitch that could make the scan fail while a gamepad is connected, which is fixed.
Dear Esther: always had full Direct VR (Source engine version).
RtcW: made some changes (again). Should work with current Steam/GOG, probably not with old CD versions.
GTA V: has DirectVR FOV, which is perfectly correct. Too strong vehicle 3D is fixed, in case that is what you meant, also the infamous semi random no-G3D issue is finally fixed, which only took 30 hours or so…
Stanley Parable: works fine here. I’m aware of your report re this, but unable to reproduce.