Forum Replies Created
-
Posts
-
Skyrim is CPU bound with vorpX in Geometry 3D mode unfortunately.
The biggest FPS gain can be achieved by switching to Z-Buffer 3D, which doesn’t look as good, but is a lot faster.
It’s quite likely that this is an injection conflict. Maybe you overlooked something.
Please try to start a few games, then create a trouble shoot data archive in the vorpX config app and send this archive to support |at| vorpx com. I will check whether I can find something that you may have overlooked.
Are you using an AMD graphics card? Z3D in Skyrim seems to be broken with AMD, this will be looked into. For now please either use G3D or switch off 3D.
There probably is 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.
Neither Prince of Persia nor Gears of War have a profile. As always with unsupported games they might or might not hook. While vorpX can hook many games without a profile, that’s not something that you can expect for every game.
Adding the launcher .exe to the exclude list in the vorpX config app might help. This way vorpX would only try to hook into the main program. No guarantee that this will help, but worth a try.
You can’t compare vorpX to monitor S3D rendering. vorpX is quite a bit more demanding since 1. It renders two full res images instead of two half res images and 2. a second render thread is running in parallel that copies the final image from DX9 to the DX11 based rest of vorpX, which is necessary since the Oculus runtime does not support a DX9 direct mode. On top of that the Oculus runtime itself drives yet another render process.
22fps still looks very low. You should get ~45fps on medium to high settings normally with Geometry 3D in most parts of the outside map (less in towns and areas with dense vegetation, more in dungeons). Just in case you are using an insider build of Windows 10: go back to a non-beta Windows 10. Insider builds may break parts of vorpX at any time.
Nothing I can recommend here despite not using the mod, sorry. The message you see is not from vorpX, but from the mod you are using.
You can play GTA V without any mod installed. To configure it for full VR mode, please check this thread.
Might sound stupid, but did you select the HTC Vive in the vorpX config app?
Also please make sure that the headset is configured for direct mode in SteamVR, vorpX does not work in extended mode.
You can’t compare vorpX performance to your normal monitor gaming performance.
Playing games with vorpX is a lot more demanding than playing them on your monitor. For one vorpX has to render everything twice in Geometry 3D mode, which lowers the framerate by ~50% compared to playing on a monitor. On top of that there is another small frame rate drop (10%-20%) because of a second rendering process taking place in parallel that renders the image to the headset. Depending on the game the limiting factor can be the CPU. In such cases a GTX 1080 will not provide any advantage at all.
For better performance lower a game’s graphics settings and/or switch to Z-Buffer 3D, which doesn’t look as good but is a lot faster since it doesn’t have to render everything twice.
Games with Geometry 3D and positional tracking support can be played standing despite the headset being initialized in seated mode. Whether that makes sense or not is another question, but with a gamepad you can also play standing. The next vorpX version will also allow to map WASD for movement etc. to the Vive controllers.