Forum Replies Created
-
Posts
-
1) The game resolution is the single most important setting in regard to image quality. 1440p roughly means native quality in full VR mode. The higher the better.
2) Whether playing a game in full VR mode makes sense is defined by the type of game. As a rule of thumb first person games with mouselook are full VR candidates while most other games are better played in immersive screen/cinema mode. Also interface heavy games (i.e. games where you spend a lot of time clicking buttons/icons) are better suited for cinema mode.
3) If the game has no option to enable free mouselook, vorpX typically can’t add that.
nVidia has options for that built into the driver, with an AMD/ATI card however it’s more complicated than it should be unfortunately. Someone posted the tutorial link below recently. It’s possible on AMD too but definitely more work than for nVidia:
https://forums.guru3d.com/threads/downsampling-with-amd-crimson-demonstration.404125/
Most do, but some games don’t capure the mouse while running windowed. Add the resolutions in the “Custom Resolutions” section of the vorpX help to your PC. After doing so running games windowed isn’t really important anymore since then you can run games at resolutions higher than your monitor allows fullscreen.
General advice: do not tweak too much. Default settings typically are chosen carefully. In a lot of cases it’s easier to break everything than to improve anything by tweaking settings.
I think I can help with that. I’ll simply send you an invoice charging a typical hourly rate of a reasonably well qualified C++ programmer. Then you don’t have to feel guilty anymore. ;)
As fast as the VR runtimes are still evolving that is impossible to maintain. You (and to an even greater degree I who had to figure out for hours what was wrong) experienced that first hand just a few months ago when you assumed vorpX wouldn’t work while in fact the problem was the outdated SteamVR version you used.
The only viable way to prevent having to deal with incompatibilities like that on a regular basis is to make sure everyone uses the most recent versions as far as possible. Neither Valve nor Oculus offer downgrade options for precisely that reason. While for you such issues may be an unfortunate nuisance, for devs like me (or those at Valve/Oculus) it’s far worse since valuable time is lost for nothing.
Once the runtimes have matured in a few years your wish might be something worth considering, until then everything stays like it is. At Valve, at Oculus and also here.
No of course not, that’s why I replied that the issue doesn’t occur anymore. Just kidding :). Whenever you see a reply about a specific issue, you can safely assume that the issue has been checked before making the reply.
The game is not officially supported anymore though, 3D doesn’t work since they switched their engine to DX11. You can find the list of supported games here.
There might be an issue with the desktop viewer on Windows 8.1. If possible please update to Windows 10. Theoretically it should still work on 8.1, but apparently doesn’t. Will be investigated later, but due to the extremely small number number of Win8 users (0.8% in the lastest Oculus survey) this issue doesn’t have a high priority currently. Thanks for your understanding.
Please first check whether your issue maybe is caused by an external factor, many issues seemingly appearing after vorpX updates proved to be pure coincidence in the past. First steps should be: 1. reboot PC, 2. ensure that SteamVR and display drivers are up to date.
If the issue still occurs afterwards, create a trouble shoot data archive in the config app and send that to support (at) vorpx com.
Still coming in 19.1.0. Unfortunately I lost a full week to fix everything related to the recent SteamVR issue(s).
Fingers crossed that no more unplanned fixes will be necessary before the next regular update.
Update 2018/12/15
vorpX 18.3.2.2 has been released. This (hopefully) concludes the series of fixes related to issues with the most recent SteamVR version.
Changes/Fixes:
- Improvements for WMR headsets related to issues with most recent SteamVR.
- Fallout 76: FOV did not work since the game got official FOV change support.
- OpenVR updated to 1.1.3b
@ RJK: Just in case: you may encounter the same openvr_api.dll issue that you encountered a few months ago. If so, please update SteamVR. Unfortunately this time it’s not possible to revert to an outdated OpenVR version just for you.
Reinstalling is the way to fix this. There is no other possible reason for the error message than the one described above.
This error means that the 64bit vorpX injector is missing. If you didn’t delete it yourself, it probably was removed by some overzealous virus scanner. Reinstalling is the only way to fix this.
Might make sense exclude the vorpX program folder from your AV scanner before reinstalling.
Are you using a Windows Mixed Reality headset? WMR unfortunately blocks the mouse while it is rendering to the headset. You have to press WINDOWS+Y to allow mouse input.
To make matters worse that doesn’t always work while a game is active, you may have to ALT+TAB out of the game, then press WINDOWS+Y and ALT+TAB back into the game.
To avoid this procedure you can cover the headset’s proximity sensor with a piece of tape before using vorpX. Then you only have to press WINDOWS+Y once. Otherwise WMR annoyingly resets this every time you take off the headset.
There is something wrong with your individual machine/setup. If repairing DotNet or using the installer linked above does not help/work, the only viable option probably is reinstalling Windows.
Alternatively you can use vorpX without the config app, the only thing that strictly has to be set up with the config app is the headset type. To do that mannually:
1. Navigate to C:\ProgramData\Animation Labs\vorpX
2. Open vorpX.ini with an editor
3. Set sDeviceIniName like described below.For all SteamVR headsets (Vive, WMR, Pimax etc): sDeviceIniName=HTCViveCV1
For Oculus headsets: sDeviceIniName=OculusRiftCV1If you can’t see the C:\ProgramData folder, enable ‘Show hidden files’ in the Windows Explorer options.