Forum Replies Created
-
Posts
-
Menus that are outside your view are best used in EdgePeek mode (press the mousewheel), which temporarily switches to a cinema like view.
Enhancing the FOV is crucial for full VR mode. What can be done in this regard varies from game to game. In many games this is solvable perfectly, in others you may have to live with compromises. The Essential Hints Guide in the vorpX help lists the various options vorpX provides to deal with the matter.
For Far Cry 3 please make sure to disable the Uplay ingame overlay in the Uplay options. Some Ubisoft games don’t hook with it enabled unfortunately. Also try both the DX9 and DX11 version of the game. One might work better for you.
Arma III requires BattleEye to be disabled. Since a BattleEye update some time ago vorpX does not work anymore with it.
You can get it look good on Vive too by following the hints given above. I would really like to understand what doesn’t look good in your opinion, but I honestly can’t. Sorry.
The latest versions won’t work with DK1 anymore since the 1.x Oculus runtime doesn’t support it, but you can contact support |at| vorpx com to get the last vorpX version that does.
Are you using a Vive? If so, flickering means frame rate being too low. The OpenVR runtime is made for 90fps with a 45fps fallback option. Below that things fall apart unfortunately. vorpX can deal with these situations to a degree with its custom async timewarp, but there are limits to that.
While performance will be OK in many areas, you definitely will always encounter areas with a frame rate below 45fps with Geometry 3D in Skyrim unless you severly reduce detail (at least the medium quality preset is required). Either that or switching to Z-Buffer 3D are the only options to get the Vive working reliably with Skyrim under all circumstances unfortunately. No way around one of these.
Works also with Vive, but not as good as with Oculus, which now has driver level timewarp, by a long shot.
With OpenVR vorpX can handle short dips or a few frames below 45fps with its own timewarp, but that’s it. OpenVR doesn’t really take the possibility of low frame rates into account unfortunately.
vorpX works with two distinct render threads to provide its custom async timewarp. The first value is the frame rate that the game runs with, the second value is the frame rate of the thread that does async timewarp and finally pushes the image to the headset.
If you are tweaking game options for performance, Game FPS is the important value. It should reach 45fps for a comfortable experience. If that is the case, direct mode fps in most cases are OK automatically.
This thread explains why it opens in Virtual Cinema Mode per default and also has instructions how to play it in full VR.
For some games you can scale the HUD with vorpX. If this is available for a game, you find HUD Scale and HUD Depth options on the image page of the vorpX ingame menu.
There might be an injection conflict with some other program on your PC. Many programs also hook into games and can cause such an issue. Not all of them are obvious.
Hottest candidates are: virus scanners, any sort of CPU/GPU utilities, game video recording/streaming software, chat programs and generally everything that can show notifictations in games.
Best way to trouble shoot is to disable/uninstall every background program that would not be there after a fresh, Microsoft only Windows install.
If you can’t solve the issue this way, please try to start a few games, then create a trouble shoot data archive in the vorpX config app and send me this archive. I will then check whether I can find something that you may have overlooked.
Games not showing on the monitor is intentional, they should show in the headset though.
Please first make sure that you have selected the right headset in the vorpX config app. If you use a Vive, please also make sure that SteamVR is running.
In case you are using a setup with multiple graphics cards make sure that the monitor and the games run on are connected to the same graphics card.
Apart from that please go through the trouble shooting guide on top of this forum.
There might be an injection conflict with some other program on your PC. Many programs also hook into games and can cause such an issue. Not all of them are obvious.
Hottest candidates are: virus scanners, any sort of CPU/GPU utilities, game video recording/streaming software, chat programs and generally everything that can show notifictations in games.
Best way to trouble shoot is to disable/uninstall every background program that would not be there after a fresh, Microsoft only Windows install.
If you can’t solve the issue this way, please try to start a few games, then create a trouble shoot data archive in the vorpX config app and send me this archive. I will then check whether I can find something that you may have overlooked.
Sounds like either positional tracking has to be recentered (ALT+SPACE) or you maybe accidentally changed the Camera Height Modifier option in the vorpX ingame menu.
Please switch to DirectX 9 in the game’s options before launching it with vorpX. The game supports multiple DX versions, DX9 is the only one that vorpX handles for the STALKER games.
Resolution:
As said a few times above, the default res of 1280×1024 is a general compromise between quality and performance.
For the best possible image quality use 4:3/5:4 resolutions like 1600×1200 or 1920×1440. If you know how to do that, you can also use custom resolutions with the exact aspect ratio of the headset screen, which will be slightly faster. 1080×1200 or 1296×1440 for example. The latter is quite close to the Rift/Vive internal render resolution and provides the same image quality as native apps do.
In Skyrim and a handful of other games you can alternatively supersample with the “Internal Resolution Upscale” option in the vorpX ingame menu.
If you want foliage antialiased, you need to activate AA and also force transparency AA in your graphics driver. This will reduce performance noticably though. Skyrim itself does a hard on/off transparency on foliage, nothing vorpX can do about that.
Performance:
Skyrim with Geometry 3D is mainly CPU bound with vorpX. Since it has to render everything twice and on top of that there is an additional overhead, performance in Skyrim isn’t exactly great.
With an unmodded Skyrim at medium to high settings you should get about 45fps in most parts of the outside map with Geometry 3D (more in interiors, less in towns and areas with dense vegetation).
To enhance performance you need to lower graphics settings (especially object draw distances) and/or switch to Z-Buffer 3D, which doesn’t look as good but is a lot faster.
TBH I think something is not correct on your end, whatever that may be.
While the default resolution recommendation (1280×1024) is indeed slightly lower than the perfect res would be since it is intended as general compromise between performance and quality, this is not true in the slightest for 1920×1440 (provided your PC can handle that), which provides the same image quality as native apps.
And if you have an extremely fast PC, you can even go beyond that with vorpX and supersample with the highest possible res your PC allows. vorpX can handle any resolution you throw at it.
In Skyrim and a handful of other games you can also supersample using the “Internal Resolution Upscale” option in the vorpX ingame menu.