Forum Replies Created
-
Posts
-
@ BlindingLightVR : I have to talk to The Destructor about this, but I think he’s polishing his mandalas right now. So I can’t reach him.
Hi nvstewart,
You could try to ALT-TAB to the desktop and back, which resets the rendering device. Very strange though that this happens with all your games.
Also make sure to try the safe settings for the display configuration: Clone mode in Windows and ‘Use system settings’ in the vorpX Config Utility.
To get a new download link, please send a mail to support |at| vorpx com .
Whitelisting false positves is usually no problem, might take a few days though. In the meantime you could try to also add vorpX.dll as an exception, that’s the second file that might be falsely detected by some scanners. Maybe that’s the case with AVG.
Glad that this is solved.
Instead of completely deactivating the scanner, it might be better to add vorpControl.exe as an exception. Almost all virus scanners allow this. This way you don’t compromise the security of your system.
BTW: What scanner are you using? I’d like to contact the vendor for whitelisting the false positive.
Unfortunately it’s not possible, or better feasible to separate head tracking from the crosshair. Head tracking does always the same that the mouse does.
Technically there would be a way to move the ‘head’ independently, but that would result in heavy graphical errors in almost all games, since you would be able to look at parts of the scene that aren’t actually rendered by the game. So unfortunately that’s nothing that makes sense in practice.
Hi clawjelly,
There is indeed a file missing in your vorpX directory. It should have a file named vorpControl.exe, which is the most important one. Starting vorpControl.exe will enable vorpX, including the tray icon.
Please try to reinstall vorpX. Maybe the installation went wrong. it somehow looks that way, since the .tmp file shouldn’t be there normally.
Hope that helps.
I’m not too surprised about that, this is pretty much the same with the general Steam issue, that also happens on seemingly random machines (with seemingly random games). What surprises me more is that it happens thirty seconds into the game. But who knows what Steam does…
Be it as it may, there is a good chance that the coming update will solve this, provided it is indeed related to the general Steam problem.
Hi Korun,
Updates are issued similar to Steam updates. When you start vorpX and an update is available, it will be installed automatically.
The current version no. is displayed in the bottom left corner of the screen whenever you play a game with vorpX.
Hi pac0master,
Your DeusEx problem might be related to a general Steam issue, which affects random games on random machines. Most likely a conflict between Steams copy protection and the way vorpX attaches itself to games. The next update, which is due sometime this week, has some changes in this regard, so there is a chance that your DXHR issue will be resolved, provided it is related.
Not sure what the issue with Black Mesa might be, since I don’t think it uses any copy protection. Can’t replicate the issue here, unfortunately.
If that is the case, then there is some hope that the changes done to avoid startup crashes with some Steam games will also help with this issue. It would fit in so far as these issues also do not affect everyone.
Keep your fingers crossed, the update will be available within a week.
vorpX tries to attach itself to every DX9-DX11 game, which works in most cases, even if a game is not directly supported. Unless there is a profile for a game there is no guarantee though, since some games need special treatment.
If an usupported game doesn’t hook with the auto detection, you can try to create a vorpX desktop shortcut (right click the vorpX tray icon, select “Create Desktop Shortcut”). There is still no guarantee for unsupported games, but the chances are higher this way for games that aren’t detected otherwise.
Hope this helps.
Yes, Geometry 3D Eye Separation is clearly too high in Skyrim (and various other games) per default. Something around 0.4-0.5 sounds perfectly reasonable. A last minute bug that somehow slipped in… The default values will be corrected with the next update.
Hi youngneil,
You can’t set values higher than their max values that are shown in the menus due to safety checks that are done when values are imported.
Under normal circumstances you shouldn’t touch the focal offset value unless you know 100% what you are doing :) . That’s why it’s an advanced setting that doesn’t show up normally. The technical term for this value is convergence, and it is pre-configured in a way that is correct for use in an HMD. Changing it might improve the GUI in Skyrim, but the cost for this is high: Stereo 3D is not displayed like it is supposed to be this way.
I’ll check whether it’s possible to exclude the Skyrim GUI from the 3D-calculations.
Hope that helps.
Is already on the list. In the meantime you can try to rename the main .exe (dxhrdc.exe) to dxhr.exe. Not sure whether everything works correctly this way, but there is a good chance it will.