Forum Replies Created
-
Posts
-
Only games that have a profile for stereoscopy are rendered in 3D. Quake has one IIRC.
For Starcraft 2 making a copy of the Diablo III profile in the vorpX config app and assigning the Starcraft 2 main .exe to it might be worth a try. That’s just a guess based on both games being from Blizzard though and thus maybe using the same graphics engine. No guarantee that it will do anything.
Provided vorpX can scale the HUD for a game, you can change its depth in the world on the image page of the vorpX ingame menu. In cases where that isn’t possible, check whether you maybe can disable the crosshair in the game’s options.
Some effects not being rendered at correct depth is a general issue of stereo injection. Whenever possible vorpX fixes these artifacts or sometimes disables such effects, but that isn’t always possible. For shadows you sometimes can decide yourself what to do. If so, there is an according option on the image page of the ingame menu.
As a general solution you can also switch to Z-Buffer 3D, which by design never has issues like these.
You can disable Virtual Cinema Mode on the main page of the vorpX ingame menu (press DEL to open it).
If a game opens in Virtual Cinema Mode per default, there usually is a reason for that though. Third person games for example open in that mode normally since they are better suited to be played this way than in full VR mode.
Just in case your post is related to GTA V, please check this link. The post contains instructions how to play the game in full VR.
First person games however should open in full VR mode right away normally. For these games you only need to adjust the field of view and the head tracking sensitivity for a comfortable ecperience. How that is done can vary from game to game and is explained in the Essential Hints Guide in the help.
You need to make sure to run the game at a high enough frame rate. Normally you should see a warning in this regard if necessary. Do not ignore this warning.
The OpenVR runtime isn’t very good at handling frame rates below its design minimum (45fps). Oculus is a lot better at this.
The suggested resolution of 1920×1440 means that one rendered pixel approximately correspondents to one screen pixel, which is how it works for most native apps. Nothing is downscaled unless you maybe have chosen a Image Zoom value snmaller than 1:0. Might make sense to do a factory reset (config app, trouble shoot page) if you already tweaked very much.
Choosing even higher resolutions like you did results in even better image quality (similar to using Dynamic Super Resolution when playing on a monitor), a similar effect occurs when you use EdgePeek.
1920×1440 basically leads to the same result as native apps image quality wise though.
Since this is so important I’d like to reiterate that a decent frame rate in the long run is the more important thing to consider. Always check your frame rate while experimenting with resolutions (ALT+F). There probably aren’t many recent games where 1920×2160 makes sense performance wise.
Mails sent to your mail address are returned with an error saying that the mailbox is full (mail quota exceeded). Please delete a few old mails and post here when you did that. I will then resend your key.
Not a known issue at all, sorry. Please try the trouble shooting steps outlined above and also those from the trouble shooting guide in the vorpX help. Double check especially for potential conflicts with other programs.
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 this archive to support |at| vorpx com. I will then check whether I can find something that you may have overlooked.
The resolution that is suggested per default is a compromise between quality and performance, but you can of course set games to any resolution you want if your PC allows you to do that. The perfect resolution quality wise would be 1920×1440.
Just be aware that many newer programs will not run fast enough when you do that. VR headsets are designed for 90fps ideally, which you won’t be able to achieve for many games even at the suggested 1280×1024 let alone at highr resolutions. This suggestion is not set in stone though, you can choose higher resolutions at any time if a game runs fast enough that way on your machine.
That sound rather odd. With the watcher disabled, vorpX doesn’t hook into the games at all. If I understand the isue correctly the desktop viewer doesn’t even work?
Considering that games also don’t hook, I would assume some general issue. 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 this archive to support |at| vorpx com. I will then check whether I can find something that you may have overlooked.
The best possible resolutions quality wise would be about 1400-1500 pixels high. All headsets render at a higher resolution than their display res to compensate for the lens-predistortion. If you are after the best possible quality, choose 1920×1440 (or an according 8:9 res if you want to do that).
Just be aware that VR needs MUCH higher frame rates than normal gaming. Rendered in stereo most newer games will not provide a high enough frame rate with such a resolution. At the end of the day a high frame rate is more important than image quality for a comfortable experience.
Using the recommended 5:4/4:3 resolutions makes your life easier while still providing most of the advantages of a custom resolutions. They are recommended for three reasons:
1. Not all games work well with unusual aspect ratios.
2. They are easier to handle since they don’t have to be added manually.
3. They leave some room for vorpX’s custom timewarp when you turn your head.Did you pause the watcher after activating the desktop viewer (vorpX tray icon context menu)? Without doing that vorpX tries to hook into the game normally.
I will have to check that, thanks for the heads up. The profile for the game was added very early on before the first vorpX release 2013. Never touched it again afterwards, so not impossible that a game update broke something.
Another option would be an injection conflict on your PC. Please try to close everything that potentially also hooks into games: virus scanners, GPU/CPU utilities of any kind, video recording/streaming softeware and generally everything that can show notofocations in games.
You only need to use the image zoom if you can’t adjust the field of view (FOV) for a game. If you can set the FOV to 120°, you don’t need the image zoom, allowing you to use the full screen area of the headset.
For BF4 for example the FOV can be adjusted with a single click in the vorpX Game Optimizer in the config app. COD Ghost has an ingame FOV slider IIRC. If a game or vorpX don’t provide an internal solution, an external tool like Flawless Widescreen or Widescreen Fixer can often be used to enhance the FOV.
The two games you mention indeed only have Z-Buffer 3D, many others allow to switch between Geometry 3D (rendering everything twice) and Z-Buffer 3D. Be aware though that G3D is a lot more taxing. In many newer games you will have a hard time to get VR compatible frame rates with G3D.
Star Citizen is not supported (and never was). It does crash on start since a SC update last year.
There is a workaround though that let’s you play it with the vorpX desktop viewer (Windows 8 or 10 required for this to be available). Follow this link for instructions.