Forum Replies Created
-
Posts
-
This gets stranger every minute. :) The ‘Smart’ mode distorts the top and the bottom of the image quite heavily, and it’s the only AR-mode that does apply this kind of distortion…
Could you please make some screenshots from the same scene (with FRAPS for example) using the various AR modes and send them to support |at| vorpx com . I’d like to check whether they show anything that can be considered abnormal. I need something I can refer to.
@Cylon: Most videos are almost certainly done with the default settings, which include the ‘Smart’ AR mode, the asymmetrical distortion in this mode is on purpose.
BTW: What cups are you using and which value for the vignette scaling do you use? Also: Are you near- or far sighted? Maybe there is some kind of pattern.
Yeah, with A cups extremely close to your eyes you might see a slight hint of a black bar ijn letterbox mode even with a vignette scale of 1.3.
Provided nothing extremely weird goes on your system, the above scenarios are the only ones that cause asymmetrical distortion. The shader definitely only applies additional distortion with the above mentioned options. Not sure what to recommend otherwise unfortunately.
I will take a look at the matter though, maybe there is some arcane bug that activates the non-linear scaling when it is not supposed to be activated under certain circumstances.
vorpX only introduces additional top/bottom distortion in two scenarios:
1. When using the default ‘Smart’-AR-Mode
2. When using 2D-FOV correctionIn all other scenarios the standard Rift SDK warping shader is applied.
The only *possible* reason that comes to mind regarding any asymmetrical distortion apart from the above mentioned cases is maybe a display resolution that isn’t displayed fullscreen on your Rift. If you happen to use other resolutions than the Rifts native 1280×800, sticking to 1280×800 might be worth a try.
BTW: You can counteract black bars in letterbox mode by raising the Vignette Scale value. If you set it high enough, you shouldn’t see any black bars at all, even when using letterbox.
There is no problem with adding useful functions, but I’m not sure whether I understand the need for this one.
Is your x-axis mouse sensitivy different than your y-axis mouse sensitivity due to some special mouse driver, or what causes the difference between x- and y-axis for you? Normally both do behave the same in vorpX. Just trying to understand.
@ Dakrid: Sorry for the inconvenience. 48hrs. is a sefety margin, usually it takes less than an hour. You should have your key in the meantime.
@ all: Although we do the best we can to send out the keys as fast as possible, in the worst case it can take a few hours until your key arrives. Please be patient, thanks. If you have questions, please send an e-mail to support |at| vorpx com .
Forcing DX9 is exactly what you have to do, G3D should work that way.
Just to be sure, please check first whether there is a d3d9.dll present in your Dirt 3 directory. Remove it if you find one.
If you checked that, and it still doesn’t work, try to create a vorpX shortcut for Dirt 3 (see the trouble shooting sticky for details). Despite not working correctly with some Steam/Uplay/Origin games these shortcuts hook more reliable than the auto detection.
Hope that helps.
@ sunny: Sorry for the inconvenience. You should have your key in the meantime.
@ all: Sometimes it can take a few hours until your key arrives. Please be patient. If you have questions, please send an e-mail to support |at| vorpx com .
Hello djcharly,
Simply follow the instructions in the dialog that is displayed on first startup of vorpX Control.
I also sent you an e-mail with more detailed instructions, please check your mail.
If you have further questions, please send an e-mail to support |at| vorpx com .
Hope that helps.
Left for Dead is not officially support in the current vorpX version, that’s why there is no Stereo 3D. vorpX tries to run even unsupported games, but in most cases without S3D. Normally a message is displayed on startup whenever that is the case.
The next update of vorpX will have full support for L4D2.
That sounds quite odd, especially since it worked earlier. Works still fine here with the latest GeForce driver, so that’s not the cause of the issue.
Please check that ‘3D-Reconstruction’ is not set to ‘Off’ and ‘Eye Separation’ is set to a value higher than 0.0. These are the two settings that influence the stereo effect.
BTW: vorpX uses two very different approaches for creating Stereo 3D. All supported games have Z-Buffer 3D, many of them Geometry 3D. Geometry 3D offers the most lifelike 3D experience, while Z-Buffer 3D is twice as fast (but has ‘less 3D’). Especially in resource hungry games you should consider the Z-Buffer mode. Smooth and silky 60fps are very important for a great Rift experience.
Sorry for the inconvenience. You should have received your key already.
If you can’t find the key in your mailbox (also check your spam folder!), please write to support |at| vorpx com, ideally with an alternative e-mail address, since something must have gone wrong.
@tutovid: Sorry for the inconvenience. If you already sent your request code and are waiting more than 3 hours for your activation key, please check your spam folder for the mail with the key.
If you can’t find the key in your mailbox, please write to support |at| vorpx com, ideally with an alternative e-mail address, since something must have gone wrong.
Hi NeoXian,
There is also an option to get headtracking without external programs through vorpX’s gamepad emulation for games without mouselook. This should also work with NFS SHIFT2 Unleashed.
Setting it up is a bit unintuitive ATM, you can find a guide here: https://www.vorpx.com/forums/topic/headtracking-issues-tips-and-tricks/#post-10646 .