Forum Replies Created
-
AuthorPosts
-
RalfKeymasterHello GarrWolfdog,
Sorry for the inconvenience. To receive your activation key, you have to send us your request code. See the license dialog for details.
If you already sent your request code, and still did not receice your key yet, please write a mail to support |at| vorpx com, so we can sort this out as soon as possible.
Just in case: please also check your spam folder.
RalfKeymasterHello vivid,
You have to start ‘vorpX Control’ not ‘vorpX Config’. It displays a tray icon in your taskbar when it is running.
The config GUI isn’t that important currently. Almost all settings can be changed ingame after pressing [DEL].
However, there also is a potential solution for the config crash: Please delete/rename the following folder C:\Users\
\AppData\Local\Oculus. This will most likely resolve the issue. The AppData directory might be hidden, you have to enable “Show hidden files” in Windows Explorer to see it.
RalfKeymasterHello Hammerschaedel,
You need a new authorization key after an OS reinstall, since the request changes in this case. Simply follow the instructions in the license dialog like before to get a new key.
RalfKeymaster@ Dino Dad : The 48hrs. are just a safety margin. Usually keys are sent within an hour. In the worst case it can take a few hours until your key arrives.
If you are already waiting longer than a few hours, please check whether you have sent us your ‘Request Code’, like mentioned in the license dialog. This code is required to create your key.
If you have questions, please send an e-mail to support |at| vorpx com .
RalfKeymasterPlease take a look at the quickstart help that comes with vorpX, head tracking sensitivity is covered there. You can open the quickstart help either from the config app or via right clicking the tray icon (choose ‘Show Help’).
General tips and a trouble shooting guide are covered in the according stickies above.
RalfKeymasterThe behaviour you expeience when clicking TESV.exe directly seems to be normal, it’s the same here. Looks like Steam detects that and then starts the launcher app rgardless what you clicked.
Regarding your original issue: did you check your Skyrim folder for a d3d9.dll (from an ENB mod for example)? While that is present vorpX will not work correctly. In case you use mods it might make sense in general to try a mod-less install first and then reinstall mods one by one. Most mods shouldn’t be a problem, but there might be some (especially when using the ‘Skyrim Script Extender’) that interfere with vorpX.
RalfKeymasterThe only thing that comes to mind is that you might have accidentally disabled the headtracking roll. It can be activated/deactivated separately from the rest of the head tracking.
You can check this either in the vorpX Config panel or in the ingame-menu (input page)
RalfKeymaster@ Mert7: Everything is fine. l3eerme sent the request code before making his post, and he got his key.
RalfKeymaster@ l3eerme: 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 .
RalfKeymaster@both of you: If you’d be willing to invest a little bit of time, I’d like to run some tests with you either next week or the week after that. Please send me a mail (address above) in case you are interested. Since you are both using an ultra large vignette scale I have a suspicion what *might* be going on, but that needs to be verified by using some test (grid) images that allow you to easily describe the distortion you see.
RalfKeymasterThis 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.
RalfKeymaster@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.
RalfKeymasterYeah, 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.
RalfKeymastervorpX 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.
RalfKeymasterThere 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.
-
AuthorPosts
