Forum Replies Created
-
Posts
-
DX12 won’t work with vorpX for the time being (and probably doesn’t really bring any substantial improvemnts for a game as old as WoW anyway).
In regard to the beta client: please use the regular client for vorpX. Unfortunately it’s not feasible to keep track of and adjust vorpX profiles for a beta version game client.
If you use anything else than Windows Defender, please make sure that your AV software is really disabled. Some AV-programs make it very hard for their users to fully disable them unless they are uninstalled.
vorpX can only provide stereo 3d for dgVoodoo if games use Direct3D (and thus dgVoodoo) for geometry transformations. S3D obviously still can’t be done for games that only use Direct3D to raster already transformed vertices, which is the case for many very old games that were designed for both software and hardware rendering.
My guess is that probably most D3D8 games and some D3D7 games but no D3D1-6 games can get stereo with the dgVoodoo profile. Unlikely that this will change in the future.
Also please keep in mind that the dgVoodoo profile, as mentioned before, is meant purely as a playground for experiments. While a significant amount of time went into creating the profile there is no official support for dgVoodoo (and never will be). Best general way to approach dgVoodoo with vorpX is not expecting any dgVoodoo game to work at all and enjoying the ones that still do.
The name field in the image you sent is not correct.
Please make sure to enter the data in the name field correctly. It has to look exactly like in the key e-mail, your name followed by the e-mail address in parantheses.
Use copy and paste to avoid typos. The key e-mail has an example image attached that illustrates how it’s supposed to look.
vorpX works perfectly fine with Windows 7. Just the desktop viewer, which comes as a free bonus add-on, doesn’t.
vorpX supports SteamVR (HTC Vive and others) just as well as Oculus since the Vive was released two years ago.
If MyCommerce did not send you a download link, your order probably failed or was not completed for some reason. You can easily check whether you have been charged in your PayPal/credit card account.
If against the odds you have been charged, please send an e-mail with your order id and your PayPal receipt (or a screenshot of your credit charge) to support (at) vorpx com, so we can check what is going on.
I’m not 100% sure, but IIRC FEAR is either CPU bound or maybe capped to a max framerate, so the GPU update probably won’t improve the framerate.
Not directly related, but worth a try: if you are using a Vive, make sure to disable Fluid Sync in the vorpX menu, on Vive it’s always enabled per default.
I noticed the menu issue too a few days ago. Will be looked into before the next update. As a workaround for now please don’t use the gamepad to open the menu. As far as I can tell opening the menu via DEL or with VR controllers doesn’t seem to be affected.
What you could try is disabling the Uplay overlay. Should not be necessary, but is worth a shot. Just checked whether there may be a general issue, but here it hooks fine by simply starting it from Uplay.
You can only assign single key presses to the VR hotkeys in vorpX, not entire sequences. If the game in question allows to assign macros to a keyboard shortcut, you could do that and then assign the shortcut to the VR hotkey in vorpX.
There is functionality to send macros directly through vorpX, but there is no way to configure that for a user. These macros are hard coded in C++ if needed.
@ matteo: Too many to list, but all minor tweaks. For the most part related to the changed gamepad functionality and a shader fix here and there.
@ RJK_ : This does the same as “Keep game specific options” did before, just allows to treat shader/DirectVR options separately now.
Important: keeping shader definitions does not make sense in 99% of cases if you make a copy of a profile for another game. They are almost always game specific. Make sure to read the tooltips for both options.
vorpX 18.2.3 has been released. This is a maintenance release that addresses the issues below.
- Better VR controller/gamepad interoperability
- Gamepad override didn’t work as intended with DirectVR head tracking. Among other things this enables use of a gamepad in Portal 2.
- Unwanted gamepad vibration should no longer occur while VR controllers are used
- Shader definitions and DirectVR scan settings can be kept/removed separately when copying a profile
- Some hotkey settings were only applied after a game restart
- Various profile fixes
No such problem here with Antichamber/Steam.
Start issues like this one likely are caused by an injection conflict with other programs on your PC that also hook into games, especially if they occur with multiple games in a similar manner. Most likely candidates are: virus scanners, any sort of CPU/GPU utilities, game video recording/streaming software, chat programs and generally everything that can show notifictations in games.
Best way to trouble shoot this is to disable/uninstall programs running in the background.
Exit crashes are avoided as much as possible, but can happen especially with some older games. That’s the nature of the beast. A game might exit before the Oculus/OpenVR runtime has a chance to unload for example, which may cause problems in some cases.
The warning is perfectly normal, always happens on submitting the first frame with OpenVR, nothing to worry about. Warnings in the log aren’t errors, a warning usually is just meant to highlight certain messages.
In general please don’t report problems with unsupported games as vorpX issues here unless you verified them with a supported title. Thanks. Unsupported games may or may not work or show all kinds of unusual/unintended behavior.