3D Vision Blog

A normal user's look into the world of 3D Stereo Technologies

3D Vision Blog header image 4

Update Version 0.6.4 for the vorpX Beta 3D Driver for Oculus Rift

November 19th, 2013 · 1 Comment · 3D / AR / VR / HMD


If I did not read that an update for the beta of the VorpX 3D driver for Oculus Rift has been released I probably would not notice (the update is available for people that bought a beta license). According to the developers of the software should update itself automatically when you start it, but in my case it was not updating itself or at least it did not give any indication of downloading and installing an update. Fortunately after running the small executable setup file that I got when I purchased my license it downloaded and installed the update, though the control panel remained absolutely the same and since there is not even an about box or check for update option (there should be) the only way I could see that I have the update version 0.6.4 installed was the files dated 15.11.2013 and the text file containing the changelog mentioning what was changed in version 0.6.4, so below you can find the full changelog of the vorpX beta 0.6.4:

– Experimental 64bit support
– Added NullTracker to disable tracking completely
– Various Windows Vista related installer changes/additions

– Various changes to avoid startup crashes with Steam/Origin/UPlay games on some systems
– VR Keys mapping not working
– Gamepad mapping not working
– Default Eye Separation twice as high as intended in Geometry 3D
– Keyboard focus ‘ding issue’ with various games
– vorpX Control does not start in Windows Vista
– Disabling vorpX freezes screen in Geometry 3D (DX9)
– Disabling vorpX causes black screen in Z-Buffer 3D (DX9)
– Headtracking activates vorpX option freezes rendering under certain circumstances
– DX9 render time handling in Geometry 3D
– Potential crash issues while loading Oculus profiles
– Geometry 3D Draw Exception DeusEx HR and possibly more games (DX9)

Added Profiles:
– Battlefield 4 (Z3D)
– Bioshock 2 (G3D, Z3D)
– Call of Duty: Ghosts (Z3D)
– Dead Space 2 (G3D, Z3D)
– Dead Space 3 (G3D, Z3D)
– Outlast (G3D, Z3D)
– Q.U.B.E (G3D, Z3D)
– Splinter Cell Blacklist (Z3D)

Profile changes/fixes:
– Battlefield 3: no 3D after ALT-TAB/Resize
– Deus Ex: Human Revolution: Support for the Director’s Cut added
– Elder Scrolls: Oblivion: nightsky/stars look weird with Geometry 3D
– Elder Scrolls: Skyrim: nightsky/stars look weird with Geometry 3D
– Fallout 3: nightsky/stars look weird with Geometry 3D
– Fallout NV: nightsky/stars look weird with Geometry 3D
– X3: Should now support X3: Albion Prelude in 3D (untested)

The most notable changes are the improvements for games that had problems running due to some sort of launcher as well as the official support for Battlefield 4, Call of Duty: Ghosts and Splinter Cell Blacklist. There is also an experimental support for 64-bit game executables, though there are still not many games that come with a 64-bit version along the 32-bit executable. And while we see good improvements in the compatibility of the software and new features, the most basic things that are a must have are still lacking like for example a proper and complete list of games that are officially supported with information what 3D mode they support, more detailed documentation about the various features and options of the software… and even a simple About option giving you the version number would be nice.

→ 1 CommentTags:···

First Impressions From the VorpX Beta Driver for Oculus Rift

October 20th, 2013 · 1 Comment · 3D / AR / VR / HMD


Time to share some personal impressions from the VorpX beta driver that adds support for the Oculus Rift VR headset in games that do not have official support for the device. I’ve purchased a beta license soon after it has been released earlier this month and played a bit with the software, so I can share some experience about how it works, what I like and what I don’t and so on as a user. If you already have a Rift Development Kit or are planning to get one, then getting a license for the VorpX beta driver is definitely a must do thing (costs around $40 USD) as the software really works very well considering it is still a beta. Aside from the VorpX, there are other alternative solutions that offer similar support for playing games that are not specially designed to support the Oculus Rift HMD and these are the Vireio Perception (open source driver) and DDD TriDef 3D software that offers beta support (trial mode available, the software is commercial). Other than these three there is the Stereoscopic Player (commercial software with trial mode) that supports Oculus Rift viewing mode for 3D videos and the rest is pretty much games and software demos that have official built-in Oculus Rift support. Don’t forget that Oculus Rift is still in a development stage and that the consumer model shoudl be available by the end of next year (probably), so we should not be too harsh on a development kit hardware and beta software for it…

I’ll start with the most serious problem that VorpX has pretty much since day 1 – total lack of information. I know that the guy(s) behind the project are probably quite busy with the programming part of the software, and they are doing really good job now that I have finally seen the beta version of VorpX, but they should pay attention to other things as well… especially if they are going to be charging money for the software. To tell you the truth I was a bit skeptical at first when I read about the project, due to lack of information an updates on the progress it all seemed like it may not happen at all, so I was very pleasantly surprised by what I saw when the beta and tried it in action even though there is more work to be done. Unfortunately the problem with lack of VITAL information about VorpX still exists – the beta is here, people buy it and they are left with no manual or detailed documentation on all of the features and functions that the software offers and it has quite some. You are pretty much left to tinker with them in order to learn what they do and how they affect things. Next up in the list of problems is the game compatibility list, you may spend quite some time looking for it and you may end up not finding it, I have ended up finding it on another website. Don’t get me wrong, I like the VorpX driver, but when you are asking money for something you cannot have the most basic things like proper documentation and game compatibility list missing!


And now it is time for the good stuff. The software is quite easy to use, just install, register your license and run it. The registration part may take up a few days, because after purchasing the software you need to download and install it, run it to get a request code and then send that code over an email in order to get your registration license – this can surely be streamlined as you probably would want to try out the software immediately after you purchase it. Anyway, make sure to have your Oculus Rift connected when you run VorpX, otherwise the software will not start, though just giving you a warning and still running could be helpful when testing for games compatibility and you don’t actually need to use the Rift. If the software’s icon is in the system tray when you run a game it should normally run in a Rift friendly mode, though if it does not, you can create a Desktop Shortcut to run the game with VorpX enabled and that sometimes can help (use the “Create Desktop Shortcut” from the menu you get by right clicking on the VorpX tray icon). For the moment you can expect to have problems with some games if they are ran through Steam, Origin or even if they have their own game launchers before actually running the game, it is also possible that some other software that hooks up to DirectX calls such as FRAPS drawing overlays on the screen may cause problems though I did not have any when using FRAPS specifically.


According to the list of officially supported games VorpX should work with about 80-90 games (that means they have profiles and stereoscopic 3D support), but then again as I’ve said you may have trouble finding which ones are these and even if you do find the list you may have trouble understanding it. Unfortunately while the VorpX software should have profiles for all officially supported games with some settings preset such as the stereoscopic 3D rendering mode used, the control panel of the software currently does not offer even listing these profiles let alone allowing you to edit them, though it should offer that functionality apparently. You can edit the settings while inside a game by calling up the in-game VorpX overlay menu with the DEL key, that is if you are able to read it as it is semi-transparent and you need to find a good place with a darker image on the screen. Also a useful tip, you might want to disable the HeadTracking Roll option from the in-game menu in most if not all games as when it is not properly supported in a game it can cause some issues. Also you might want to play a bit with the Aspect Ratio option as the default Smart option may not always provide the best results in some games. The HeadTracking Sensitivity is another option that might help you get better experience while playing if the world “spins around” too fast or too slow when you move your head.


What makes difference is that in games that will work with VorpX, but are not yet “officially supported” (not have profiles) the stereoscopic 3D rendering will not be enabled and available for the user to enable through the in-game VorpX settings menu. The two rendering modes for stereoscopic 3D that VorpX supports are: Z-Buffer Mode that is the kind of “fake” stereo 3D effect that offers faster performance and decent results and Geometry Mode that is supposed to be full dual view rendering with better stereo 3D effect, but with more performance hit. Now, I completely get that if a game has not been tested to work with the two stereoscopic 3D rendering methods the VorpX supports things can get messy, but having it just disabled at start and still giving the user the option to try to enable it to test might actually help in finding faster what games work and what have issues. We all have played the profile game where you recognize the game by the name of the executable file and run an appropriate profile for it, so by just renaming the executable of a game to a supported game by VorpX you can get the stereo 3D rendering option back, but why should we have to do this. There are also some really useful features available some of which I find very useful, like for example the Edge Peek functionality that allows you to look around the corners of the screen that may normally not be visible when using the Rift as well as the Image Zoom function that allows you to zoom-in or out the whole image displayed on screen (good feature to compensate for the use of different lenses of the Rift).

You should have in mind that currently the VorpX software only works with 32-bit games , it will not work if you run a 64-bit game executable. The software does work just fine under 64-bit Windows, it will just not attach itself to 64-bit game executable, but fortunately there are not many of these and the games that come with 64-bit executable usually have a separate 32-bit ones as well. Other important things that the developers of VorpX note in their forum are that VorpX requires AMD/ATI or Nvidia graphics card and it may not work on Intel graphics (who would play games on an integrated Intel GPU anyway) and SLI or Crossfire multi-graphics card setups may or may not work (could not test that as I currently do not have a SLI/Crossife setup). Also disabling stereoscopic 3D support on systems using other stereoscopic 3D drivers before running a game with VorpX is recommended, so if you have a 3D Vision system for example don’t forget to disable the stereoscopic 3D support from the Nvidia Control Panel.

One more thing as last that is not yet very clear and that is how updates for the VorpX will be distributed. Since we are not downloading the software from anywhere directly and there is no Update option available anywhere in it we might have to use the web downloader to reinstall it by downloading a newer version or we may get notified by email with an update link. Again according to information in the VorpX forums we are most likely going to see the first update for the VorpX beta by the end of this month, hopefully addressing at least some of the issues mentioned above.

For more information though not much about the VorpX driver…
Click here for the list of officially supported games by the VorpX driver…

→ 1 CommentTags:····

The VorpX Beta 3D Driver for Oculus Rift is Now Available

October 1st, 2013 · 2 Comments · 3D / AR / VR / HMD


Finally we are going to see something from the vorpX 3D driver intended for providing Oculus Rfit support for games that do are not made to be used with the Rift – this means stereoscopic 3D rendering as well as headtracking mapping to the game controls. There was just an announcement that a VorpX Beta has been released an it is available for purchase for ~40$ + taxes with a time-limited demo version that is supposed to be made available in a few weeks for people that want to try before they buy the software. According to the developer of the software the vorpX beta is already compatible with about 80 DX9-DX11 games including support for games like Skyrim, Crysis, COD: Modern Warfare 3, Fallout 3 and many, many more. This license for the beta release includes free updates until (but not including) a future version 2.0 of the software and you are allowed to install the software on two machines at the same time.

I have not yet personally tested the software, but I do plan on buying a license for the VorpX Beta 3D driver to try it out, so I’ll be sharing more information and personal experience with it as soon as I’m able to test it for a bit, so stay tuned for more…

Meanwhile for more information about the VorpX Beta 3D Driver…

→ 2 CommentsTags:···