Forum Replies Created
-
Posts
-
You need the latest Oculus runtime 1.3 for the new vorpX version. Neither vorpX nor any other future Oculus software will work with beta runtimes.
Please do a fresh install using the web installer that you got when you purchased vorpX. If you didn’t keep it, send an e-mail to support |at| vorpx com.
If the Oculus software does not support your graphics card, I can only offer rolling back to vorpX 0.9. For that please send a mail to support |at| vorpx com.
You need the latest Oculus software, which includes the Oculus runtime 1.3, for this version of vorpX:
Please make sure to install the latest Oculus software. It is required for the new vorpX version. Note that you need a Rift DK2 or CV1 for this. DK1 does not work anymore.
https://www.oculus.com/en-us/setup/
If you still use a DK1, send a mail to support |at| vorpx com for another solution.
That usually means that another runtime version is present than 1.3, or (the other way around) vorpX was not fully updated.
Please uninstall vorpX (keep the license when asked about it), reboot (important!), and then reinstall using your web installer. if you don’t have it anymore, send a mail to support |at| vorpx com.
If you by any chance have the runtime switcher installed, please make sure that it is set to use the 1.3 runtime, or ideally remove it completely.
It should work with CV1 just fine normally. vorpX 16.1.2 was built and tested with CV1.
Could you please provide the *exact* error you get? Ideally please make a screenshot of the error message. Thanks.
Also please make sure to allow “Unknown Sources” in Oculus Home if that is not the case.
A change in the versioning system after the beta phase: year.release.subrelease. Read it as vorpX 2016 1.2 and it starts to make sense.
It *might* work with the OpenGL renderer of these games.
You can now create custom profiles in the vorpX config app. Set the game to use OpenGL, and then make a copy of an existing OpenGL profile (e.g. Quake) and apply the UT99 exe to it.
No guarantee that this will work, but trying it only costs 5 minutes.
Profiles are now stored in a database. Right now this database is completely overwritten when reinstalling. A better way to handle this is on the list.
You can however export important settings to the cloud (or a file on your PC) and re-import them later in the config app.
For serious Fallout 4 playing over a longer time I would highly recommend to switch to Z-Buffer 3D. Runs a lot smoother that Geometry 3D.
Some people don’t like Z3D, hence G3D is now the default. But in my honest opinion, games as demanding as Fallout 4 are way better played with a slightly flatter Stereo 3D than with a low frame rate around 30fps. Your mileage may vary, of course.
Hello,
As far as I can tell you received an answer to your first mail yesterday about 6 hours after you sent your first support request – on a Sunday.
Right now everything is pretty busy over here. Please allow three days for answering further e-mails.
Thanks for your patience.
I will release an update later today that contains a potential (emphasis on potential) fix for the DK2 Desktop Viewer issue. Any feedback on that is highly welcome.
Logs and some other trouble shooting info can be collected in the config app (trouble shooting page).
No, absolutely not, quite the opposite. Do not even think of doing that.
If the Oculus screen shows “Waiting” for more than a few seconds, the game almost certainly hangs for some reason.
Prior to the latest vorpX version this would just result in a black screen, but now you would see exactly this. The most likely cause of a program hanging on start is an injection conflict.
Please consult the trouble shooting guide for possible programs that may cause conflicts with vorpX. No. 1 candidates are virus scanners, but there are more. The guide list a few things to look for.
DK2 owners who had no problems with vorpX 0.9, please contact support |at| vorpx com for a way to get 0.9 back.