Forum Replies Created
-
Posts
-
vorpX requires the Oculus runtime 0.8. If you need a vorpX version that works with an outdated runtime, please send a mail to support |at| vorpx com.
I would suggest to switch runtime versions as required though instead, costs literally just a minute (and a reboot).
You can download all Oculus runtime versions here: https://developer.oculus.com/downloads
You can always use the ImageZoom in the vorpX ingame menu (or with [SHIFT][MOUSEWHEEL]) if there is no way to set the FOV. Works with almost any game.
If you kept a copy of the web installer that you received when you purchased vorpX, you can simply use it to install again.
If you didn’t keep a copy of the web installer, please send a mail to support |at| vorpx com to get a new one.
Such crashes can be caused by other programs causing a conflict with vorpX by also hooking into games/apps. There are quite a few programs that do such things, not all are obvious. Things to look out for are: virus scanners, any kind of GPU/CPU utility or graphics driver add-on, chat programs that can show messages in games, video recording/streaming apps and generally everything that has the ability to display in-game notifications.
If this is happening with the DX11 version of the game, you might have to try a few (or many) times, or better switch to DX9. In DX11 there is a long outstanding issue with frequent startup crashes in FC3 and some other Ubisoft games.
This will finally be fixed in the next vorpX release, but for now trying often or switching to DX9 is what you can do.
I’m not 100% sure ATM, but I think the game has both DX9 and DX10, maybe one works better for you than the other. Please try to switch between them. Requires a manual ini edit in Codemasters games. Off the top of my head: [Documents\My Games\Formula1 2013\hardwaresettings\hardwaresettings.xml]. Look for a setting called ForceDX10.
Apart from that please check the things from trouble shooting guide in the help regarding not hooking games in case you haven’t done so already.
Please contact support |at| vorpx com explaining the situation. This cannot be resolved on the forum. Thanks.
Please contact support |at| vorpx com about commercial licensing options if you need vorpX for your job. Standard licenses are valid for private, non-commercial use only. Thanks.
Valve/HTC unfortunately thought otherwise as it seems. I’ll preorder as soon as possible, so leave the first 10 minutes after preorders start to those who really need one. ;)
You should have received your new key. If it didn’t reach you, please send a mail to support |at| vorpx com.
In case you don’t do so already, please make sure to use the latest Oculus runtime 0.8 for vorpX 0.9.1.
Only fairly old OpenGL games have 3D, which use the so called fixed function pipeline. There are a few exceptions like Amnesia, but that’s the probably the last one using this. Newer OpenGL games will probably display in the headset, but almost certainly in 2D.
vorpX works just fine with the DK1. Not sure what the OPs issue may be unfortunately, or how vorpX could cause a blurry image. If there would be a general issue with the DK1, you can be sure that there would be also a lot more reports of such a problem here.
The current vorpX build 0.9.1 released last November uses the latest Oculus runtime 0.8 and this build was tested and is working with Oculus Rift DK1 and DK2. There will be no future DK1 specific development anymore though.