Forum Replies Created
-
Posts
-
@ jtwxlii: Additionally to using the Oculus runtime 0.5/0.6, you may have to go back to an earlier version of your nVidia driver from before the 0.7 Oculus runtime release. For example 352.86. This was the official driver from the time vorpX 0.81 was built, so it’s the safe bet.
To be extra sure, please uninstall Oculus runtime and driver you are using now before installing 352.86.
vorpX 0.9 with Oculus runtime 0.7 support will be released next week.
Tried it already, unfortunately there was an issue when switching to video playback. If there is enough time before the 0.9 release, I’ll try again with the new DX11 Kodi, which will be the default API for the next major Kodi release anyway if I understand things correctly. Can’t promise anything though, may or may not be possible.
Quality wise VLC will be probably the best option though since it allows to avoid the double scaling issue described earlier in this thread. At least on Windows 8+, on Win7 it seems to a bit prone to occasional frame skips.
Yes, normally vorpX auto updates. The only way to prevent that is forbidding vorpControl.exe access to the internet using a firewall rule.
If you are on Windows 7 or 8, I would suggest to either switch between runtimes or use a side by side configuration for 0.5/0.6 and 0.7 runtimes (described here) instead.
This way you can use both 0.5/0.6 and 0.7 apps without too much hassle.
Please contact BitDefender about this issue and inform them that it’s a false positive. They will then check the issue.
Most AV programs try to guess whether a program may be malicious, and apparently BitDefender guesses wrong in case of vorpX. Maybe because it “injects” other programs to work. Most AV vendors offer a web form or mail address to inform them about false positives.
Thanks for the heads up both of you. I removed my recommendation above to make sure no one falls into this trap.
I’m not sure why you currently aren’t able to use Xpadder & Co. unfortunately, shouldn’t be a problem with the internal vorpX gamepad emulation disabled.
For the next version the whole gamepad handling has received a major overhaul and provides all sorts of new options ranging from completely hiding gamepads from the game (good if you prefer external tools) to a selective override of specific axes/thumbsticks (primarily good for just swapping the right stick if it interferes with mouse input).
So chances are good that you’ll be able to find a mode that fits your needs.
Following the procedure suggested by NipOc earlier in this thread you should be able to use 0.7 and 0.5/0.6 side by side without too much hassle until the next vorpX version is released.
Please send a mail to support |at| vorpx com to get an older version for your DK1 that does not rely on the Oculus runtime.
That will be easy enough. Not as nice as full blown scenes with dynamic lighting, but still a good thing for everyone who likes to have different environments. Also good for gaming purposes where every extra polygon in an evironment diminishes the game performance. Probably won’t make it into 0.9, but I’ll definitely look into it afterwards.
There are no plans to stop work on vorpX. If technically possible, which almost certainly will be the case, vorpX will work with the Rift consumer version.
There are no plans to stop work on vorpX. If technically possible, which almost certainly will be the case, vorpX will work with the Rift consumer version.
The Enterprise bridge probably would require a license from CBS or Paramount, so I don’t really see that happen. Other environments *may* follow, we’ll see. The video player support in vorpX does not have the highest priority though.
There are quite a few dedicated VR video player apps out there that do the basic job almost as well, probably indistingishuable to most people, and will always have a few advantages over an injection based solution in other areas, like being able to provide a full UI in VR and similar things.