Forum Replies Created
-
Posts
-
DirectVR rotation means that rotational tracking is directly translated into a game’s camera rotation. The main advantage over vorpX’s default head tracking is that it never has to be calibrated. In older games it also improves latency.
In most newer games, e.g. recent Battlefield titles ;), the default mouse based head tracking is almost as good as DirectVR rotation would be.
1) You can switch the controller mode to gamepad emulation in the vorpX menu (Touch Controller page). Be aware though that in some games gamepad and mouse (may be required for vorpX’s head tracking) can’t be used at the same time.
2) Not in vorpX but many games allow that when you use the VR controllers in gamepad mode.
3) Use the vorpX sharpening. It’s applied at the best possible time in the rendering pipeline.
4) Can’t remember the specific case, but running games windowed is generally a good idea in case of issues in fullscreen mode.
5) In many G3D games you can disable shadows on the image page of the vorpX menu if they are too glitchy. Also keeping the 3D-Strength within a sensible range (close to default) helps.
6) Can’t really answer that since I have never used one them. Generelly I would recommend to keep the number of tools running in the background as low as possible, ideally zero.
Hope that answers your questions.
Plaease check the Pimax section in the vorpX help and make sure to setup everything as described there.
If the game has DirectVR resolution support (indicated by an according message in the top left corner of the game window), you can change the resolution on the DirectVR page of the vorpX menu.
You also might want to add resolutions to your PC that it doesn’t support yet. How to do that is explained in the “Custom resolutions” section of the vorpX help.
That was true in the past on Windows XP, but since User Account Control (the nag screens when you want to do something that requires admin rights) has been introduced with Vista it’s pretty much pointless in regard to security concerns. A normal account doesn’t really have more rights than a restricted account unless you confirm the UAC dialog when it pops up.
When you start a game that requires admin rights (like The Witcher) from a restricted account, it is executed on your admin account, which probably is the reason why it can’t connect to the Oculus runtime. You’d have to contact Oculus support about that, but likely they won’t care since no native app/game requires admin rights.
BTW: Running vorpX as admin in your scenario is also less than ideal. Like many other apps/games vorpX stores a few things in a user specific folder (e.g. background images for cinema mode). Since running an app with admin rights on a restricted account always implies running it with a different user account, you have two different user folders and probably will wonder later why things behave differently when you run vorpX as admin/non-admin.
None of the above is a vorpX issue, just ‘perfectly normal’ side effects of running programs that require admin rights from a restricted account.
Bottom line: don’t use a restricted account on a home PC, doubly so if you want to use older games/apps that require admin rights. Doesn’t really have any security advantages since UAC was introduced in Windows Vista, but causes a lot of small and sometimes larger hiccups. Restricted accounts only really make sense if as an admin you want to limit another user’s access to the system. For an account you are using yourself restricted rights don’t make much sense these days.
If that happens for every game you try, it’s almost certainly an injection conflict with other software on your PC that also hooks into games.
If you already checked for potential candidates listed in the trouble shooting guide, but couldn’t fine one, try to disable/uninstall programs in the background even if you don’t think they might hook into games.
If you use anything else than Windows Defender, please also try to uninstall your AV program for testing purposes. Some more invasive ones can’t be fully disabled otherwise. Windows Defender kicks in automatically when you uninstall third party Av programs.
Hooking DX12 to apply some post effects (e.g. Z3D in vorpX) is not a big deal, a Geometry 3D implementation however is a bigger effort. Currently DX12 is still not required for 99.9% of games, so no need to rush anything. There is ongoing internal research, but no date yet and nothing else to share at this point.
Not really sure about your strobing issue, sorry. Try to switch to Z3D if G3D doesn’t work for you. Switching between windowed/fullscreen may also be worth a shot.
The low performance warning may just be displayed because the game caps the framerate in menus/loading screens. Many games do that. You can check the actual game frame rate with ALT+F in the game.
Glad you could solve it.
You can navigate/use the menu with the left touch controller. Left trigger is a button click. Just checked it with the Rift S controllers since I wasn’t entirely sure anymore myself.
BTW: I would be very careful with your rather aggressive firewall add-on. I wouldn’t be totally surprised if it even blocks internal communication between two apps if they use a network protocol. vorpX doesn’t, but others may.
Short official confirmation that the Rift S works fine with vorpX. I have one here now.
The only minor hiccup is non-working audio switching. Until vorpX can do it simply switch the playback device manually from the Windows taskbar if you want to use the internal speakers of your Rift S.
BTW: The Oculus init error -3003 means “Couldn’t connect to the OVR Service.”. Something is seriously messed messed up if not even the Oculus runtime can be initialized correctly.
BTW2: If you happen to use multiple GPUs, make sure both your monitor and the headset are plugged into the same GPU. If you use multiple monitors, disconnect all but your main monitor.