Forum Replies Created
-
Posts
-
Since there were a few question about how to use this: here’s a video tutorial:
Disclaimer: Neither the video nor the runtime switcher is related to vorpX in any way. This information is provided for your convenience only. Make sure to read the instructions if you want to use the runtime switcher.
You can watch 3D movies with vorpX. It has a special video player mode that works with VLC and MPC-HC and allows you watch almost any movie that these players support. Quality wise this is one of the best solutions to watch movies on your headset.
——–
Unrelated: As a litle reminder for those who didn’t read the pages before: Vive support is not ready yet. As soon as it arrives, implememtation will begin.
I think about that once the vorpX Oculus 1.3 update is out and vorpX is working with the Vive. Not much time to actually play anything (besides testing) currently…
I received an e-mail from HTC a few days ago stating that my order is being processed, but haven’t heard anything more concrete since then.
As much as I would like to help you, I really can’t say anything else than above. Sorry. You normally can use external tools like X-Padder etc. if you wish. You may also be able to setup vorpX’s internal gamepad emulation (which basically is a bare bones version of what Xpadder etc. do) for your custom input device, which would be completely unsupported though.
X360CE seems to be regularly used by others in conjunction with vorpX, you can find multiple threads mentioning it here on the forum. Maybe one of those those threads can give you a hint in the right direction.
You may also be able to configure vorpX’s internal gamepad emultation for your needs instead of using an extra tool. It offers the most imprtant things that programs like X-Padder offer built directly into vorpX. That would be totally unsupported for your custom input device though.
Adding the additional utilities’ main .exes to the exclude list in the vorpX config app might be worth a try. Other than that I’m out of ideas, I’m afraid.
vorpX has it’s own fully configurable gamepad emulation that may override the same functions that the other programs override.
You can check whether it’s enabled for the games in question and try disabling it if that’s the case. Please note that for some games it may be required to have this enabled.
Please try switching to Z-Buffer 3D in the vorpX menu. G3D in Payday 2 was broken several times in the past by game patches. I’ll look into it, but no promises.
Checked it right away yersterday evening (Steam GOTY edition with the latest vorpX build). I experienced one crash during a loading phase, but that seemed more or less random and didn’t happen again afterwards. If it worked before, maybe it’s an issue with the runtime side by side configuration.
You might want to wait a little anyway. While being at it I fixed a few shader glitches and the messed up menu yesterday.
Due to the far more complex rendering pipeline direct mode did cost about 15%-20% of raw performance when it was introduced last year. This was however compemsated fairly well by async timewarp, which also reduces latency. So all in all this was a win in most cases despite the lower raw performance.
With the new driver side async timewarp in 1.3 that supersedes the prior custom solution things feel even snappier. In the mid term at least a part of the lost performance *may* (emphasis on may) be gained back. That won’t make it into the first 1.3 update though.
It’s not out yet. Keep an eye on the home page. An annoncement will be made there as soon as it is available.
Does this happen with the DX9 or the DX11 version? DX9 is the preferred mode in this case since it has Geometry 3D.
Please allow 48hrs. like mentioned in the license dialog. Usually it’s a lot faster though.
You should have received your key. If it still did not reach you, please report back.
Always a bit hard to guess without seeing anything, but what you describe sounds a lot like something that can happen when the GPU is overloaded. Please check your frame rate with [ALT][F]. Ideally both values should show 75fps (DK2). If the “Direct Mode FPS” drop below 75, you have to reduce graphics settings or resolution. This value has to be 75 at all times.
Some more performance optimization hints can be found in according guide in the help.
The next version should be more resilient to issues like this BTW, since the custom async timewarp that vorpX uses is now superseded by an async timewarp implementation in the Oculus driver, which can handle situations with heavy GPU usage quite a bit better.