Forum Replies Created
-
Posts
-
The forum software uses Gravatar images. Never tried that myself, but you should be able to change the image on http://en.gravatar.com/
Let us know whether that worked!
There is a purchase from you, but we never received your key for some reason. Please resend your request code using the contact form in the support menu above. Apparently there is an issue with receiving mails from you.
You can use any resolution that works best for you.
5:4/4:3 are recommended for the reasons outlined above and because for most users they are easier to handle. If for you other things are more important, there is nothing wrong with using whatever meets your requirements.
Yes, like mentioned in the license dialog.
Just in case: if you are very inexperienced in using computers and have trouble sending an e-mail, vorpX might not be the right thing for you. Using it requires a certain amount of computer skills.
You can send this mail like any other mail. Gmail will work just fine.
1. Open your mail program or browser based mail service, whatever you normally use
2. Create a new e-mail
3. Enter the the mail address from the license dialog into the recipient (To:) field
4. Enter a subject, e.g. vorpX key request (doesnt really matter)
5. Copy and paste the request code from the license dialog to the e-mail body
6. Send the e-mailShortly after you will receive a mail with your key.
The original text was for DK2 which has a 16:9 screen (hence 8:9). It is still used by many. If you are after a perfect match, you of course have to choose a resolution that matches your headset’s screen aspect ratio.
5:4/4:3 aspect ratios are still better BTW. At least the Rift CV1 has a feature called partial overlap, which introduces some left/right asymmetry. 5:4/4:3 provides some extra pixels for that as well as for vorpX’s async timewarp.
Hence 5:4/4:3 are the recommended aspect ratios now. All things considered they not only are easier to handle, but also work best.
There is no key in the screenshot!?
Please FOLLOW THE INSTRUCTIONS on top of the license dialog and SEND AN E-MAIL WITH YOUR REQUEST CODE to the mail address mentioned in the dialog.
After doing so, you will receive an e-mail with your key that you have to paste into the dialog additionally to the name.
Normally you should be able to copy and paste directly from your e-mail program.
If that does not help, please send a screenshot of the dialog after you pasted in the data to support |at| vorpx com like suggested above so I can take a look at it.
Use COPY AND PASTE to paste the data into the dialog. Do not type anything manually. Also check for leading or trailing white spaces, which might cause an issue.
If that does not help, please send a screenshot of the dialog after you pasted in the data to support |at| vorpx com. There almost certainly is something typed in wrong if the registration fails.
I merged the two threads.
This is an AMD issue and unfortunately there is no easy fix for it (except not using an AMD card). OpenGL in vorpX relies on OpenGL extensions to get the image from OpenGL to the DirectX based rest of vorpX. Support for some of these extensions is rather flaky in AMD drivers unfortunately.
A possible workaround is using the vorpX Desktop Viewer instead of vorpX hooking directly into OpenGL. This won’t give you Stereo 3D, but the game will be playable otherwise.
1. Start the vorpX Desktop Viewer.
2. Pause the vorpX watcher (right click menu of the vorpX tray icon).
3. Start the game windowed! Fullscreen OpenGL will not work with the desktop viewer.
4. Move the game window to the center of the view.
5. Turn off Virtual Cinema Mode in the vorpX ingame menu to play in full VR.If you create cutom resolutions anyway, why not create one that exactly fits the headset instead of a 8:9 res (which was an exact fit for DK2)?
For CV1/Vive that would be 1080×1200 or 1286×1440 for example. This way you can easily reach your goal without the need for any image zoom.
In that case please double check that you have the latest Oculus software installed. This error usually occurs with older runtimes.
You need to make sure that no remnants of an older runtime is present on your system. Make sure to completely uninstall any beta runtime that you may have installed and DO NOT use a runtime switcher.