Search Results for 'The Void'

[Ralf]

You have to press F11 in the game to switch to the new FOV after applying the Game Optimizer setting. In some cases additional steps like this one are unavoidable. If that is the case, the additional steps are mentioned in the according optimizer entry.

If applying the FOV automatically fails for some reason, you can also do these tweaks manually in many cases by googling for “FOV + Game name”. For Mirrors Edge you can find multiple tutorials, one of thhem here: http://steamcommunity.com/sharedfiles/filedetails/?id=138177233

Alternatively you can use the 3D FOV Enhancement in the vorpX ingame menu. Directly setting the FOV in the game is usually better though.

[Ralf]

Usually the performance hit of Geometry 3D in vorpX should be in the range 50-60%, which is true for any 3D driver BTW. For smooth gameplay at 60/75fps in Geometry 3D your PC has to be able to run a game with 120/150fps in 2D.

For games like Bioshock 1 or Jericho, probably even Dishonored, this should be possible with a gfx card in the range of GTX770/780.

If your card has something like that, you should enable Adaptive VSync to avoid falling back straight to 30fps if 60fps are not possible. Also consider reducing Antialising settings, 60fps are more important.

And of course there is always Z-Buffer 3D in vorpX, which works almost as fast as 2D rendering. In VR high framerates can be more important than the better Stereo 3D effect with Geometry 3D.

[jayarpeggios]

Would it be possible to restrict the mouses y coordinate but allow the head to move the mouse input in the x and y coordinates? That way you can avoid looking up with your head but be looking at the ground in game. Considering vorpx already modifies mouse input, I’m guessing this can be done. However, your head is still locked to the cross hairs as I assume that would have to be done in the game code, but it would still improve controls.

[Ralf]

Hello sonaki,

Sorry for the inconvenience. Your key was sent twice already to the second e-mail address you mentioned above: on August 4th, only seconds after we received your request, and a second time on August, 7th.

I resent it again to both the addresses mentioned above. Please check your spam folder in case the messages are treated as spam for some reason.

If that still doesn’t solve the issue, please contact support |at| vorpx com, ideally using another e-mail address to avoid similar issues.

[Ralf]

Hello Solmors,

You can get the current version of vorpX to work by setting the Rifts render mode to Extend Desktop and configure the Windows monitor configuration accordingly. The Rift should be displayed in landscape orientation in the Windows monitor dialog (which means setting it to portrait mode). It also should be set up to clone mode or as primary monitor since most DirectX games automatically start on the primary display. Alternatively you can try to force games to a specific monitor through the vorpX config app, but that doesn’t work for all games.

Please be aware that head tracking does not work with the current build on the DK2. This will require a build with the latest Oculus SDK. Also lens distortion parameters aren’t optimized for the DK2 yet.

We will be as fast as possible in regard to a version with more official DK2 support (and more), but there is only so much that can be done without access to the actual hardware. Stay tuned.

PS: I would also recommend to disable all additional monitors except your main display when using vorpX to avoid any possible issues that may arise from that.

[Ralf]

Merging this into the existing thread to avoid clutter.

@ all: Usually it takes less than an hour until you get your key after sending your request. In some cases it might take a few hours (for example over night).

[Ralf]

Without seeing the actual order: if you received this message from our billing service MyCommerce and nothing else, your order *did not complete* and your credit card was not charged for the purchase.

Please check your credit card account, whether you where actually charged, and contact me directly instead of using the MyCommerce support (ideally with your order id) via support |at| vorpx com to sort this out.

—
On a sidenote: I will merge your other thread into this one to avoid clutter, just in case you wonder where it went.

[Ralf]

You can adjust the Separation to your liking if you want, nothing wrong with that. In some games (including Skyrim) it’s currently a bit too high to give a realistic sense of scale per default, so it might make sense to set it lower until this is fixed.

The IPD usually should not be touched though once it is calibrated. It’s quite important to have this set right to avoid eye strain while using the Rift over a longer time. Calibrating it with the Oculus utility is the best way to do this.

[Ralf]

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.

[Tankshell]

Hi guys,

Can somebody tell me how well the current Vorpx beta works with these codemaster games?

I have been using Vireio for the last few months in conjunction with opentrack to play Dirt 2/3 which works quite well, but I have to disable shadows in the game settings as there are problems with rendering them in stereo. Currently Grid is totally unsupported in Vireio so I can’t play it at all.

I konw Vorpx supports Grid, so that is a good start. Does Vorpx do anything specifically to help with the shadow rendering in these games whilst in geometry mode? Or will I still need to disable them to avoid the strange flickering issues?

Based on the answer to this question I might purchase a copy of the beta.

[Vang]

DickDastardly wrote:

Whilst I agree that it would be nice to be able to remap hotkeys, the specific problem you’re having can be avoided by toggling edge peek mode (by clicking the MMB rather than holding it down i.e click MMB to activate edge peek, mouse over the menu item you want and LMB click it then click MMB to deactivate edge peek).<br>
Cheers,<br>
DD

Huh, good point, I’ll try that. I think another problem that still wouldn’t help is in Skyrim there are several “hidden hard keymappings” one of those is unfortunately MMB = use item when you bring up the inventory.

Letting the user softmap the edge peek key is probably the only solution that would work for any given quirky gaming situation that may come up.

[DickDastardly]

Whilst I agree that it would be nice to be able to remap hotkeys, the specific problem you’re having can be avoided by toggling edge peek mode (by clicking the MMB rather than holding it down i.e click MMB to activate edge peek, mouse over the menu item you want and LMB click it then click MMB to deactivate edge peek).
Cheers,
DD

[Ralf]

Thanks for menu hint. That shouldn’t happen of course.

Feedback is welcome, of course! Just one request: It would be great if you could mention whenever you talk about unsupported games to avoid confusion.

[Inscius]

I use Avira Free Antivirus, as soon as I install Vorpx, it detects the trojan virus TR/Crypt.XPACK.Gen3 within the file “Vorpx.DLL”. Anyone else have this issue? I have re-installed Vorpx and the same problem occurs. Is the virus checker mis-identifying the virus, due to the way Vorpx works?

I can’t imagine this file atually containing a virus, given the number of people who must be using Vorpx by now. My apologies if this is being discussed else where, I can’t find any other posts relating to this problem.

[Admin Edit: ‘False Alarm’ was added to the topic title to avoid mass panic]

[Ralf]

Laszlo, vorpX beta is out for barely three days. Of course we will investigate this. What did you think? Also vorpX beta is and was sold as beta software, which is also displayed on screen the whole time, to avoid possible misunderstandings.

I’m really sorry that Bioshock Infinite right now is not working for you. Mind if ask if other games work for you?

You may also take at look at the following general trouble shooting guide, maybe it contains something useful for you:

First and foremost: If you happen to use any DLL override (like ENB Series, SweetFX or similar) for a game you want to try: Get rid of those. There should never be any d3d9.dll, d3d10.dll, d3d11.dll, dxgi.dll, xinpunt or any other system dll override in a games directory that does nor belong there. vorpX ‘hooks’ into these system DLLs, additional overrides can create all sorts of conflicts.

The same is true for any other kind of injector (like the script injectors for various Bethesda games). They might or might not work. if in doubt, disable them.

Disable any other stereo driver you might have running (nVidia 3D Vision for example).

If in doubt, disable all programs that can show content over DirectX. Skype, Mumble, Fraps, SteamOverlay are typical cases. This should usually cause no issues, but if you have problems, it’s always worth a try to temporarily disable those programs or their in-game windows.

Same as above for Desktop Streaming Applications like Splashtop. Try to disable and see whether things work better this way

vorpX only works with 32bit application at this time. This is important for example in WoW, which also has a 64bit version. The latter will not work with vorpX.

If a game has different .EXEs for DX9 and for example DX11, try both. Usually both should work to some degree, in some cases there are hints displayed on startup which one works better. If one completely refuses to work for you, maybe you have better luck with the other one.

If you have an SLI or Crossfire (dual graphics card) system disable this. It might or might not work, but is currently completely untested an thus not supported.

Disable any graphics ‘accelerator’ (Lucidlogix Virtu for example) if you use something like this.

If you use an Intel graphics chip, you’re on your own, at least for now. System requirements for vorpX include nVidia/ATI graphics. Judging from feedback, many things seem to work with Intel, but this is completely untested. Also for some things there are distinctive nVidia/ATI rendering paths in vorpX, those things won’t work at all on Intel.

Final note: There are a games that work great for some people but cause problems for others. Nothing uncommon in the wonderful world of Windows. We are trying to resolve those issues, but fixing things that can’t be replicated consistently, is sometimes tough. There might (and will) be cases were fixing issues that apply only to some will take some time.