Forum Replies Created
-
Posts
-
I can’t really suggest much more than above, sorry. You can probably imagine that there would be quite a few more posts like yours if there was a general problem with running games from Steam. Also Steam versions are usually used when doing profiles here, so I can practically guarantee that Steam is not your problem.
Probably some weird coincidence. Please double check for everything I mentioned above. Also try the alternative hooking method in the config app. In some cases that can help without having to get to the bottom of a hooking conflict.
If after thoroughly checking everything (again) that is mentioned in the trouble shooting guide above you still can’t solve your issue, please create a trouble shoot data archive in the config app and send that to support at vorpx com. No promises, but I’ll check whether you maybe overlooked something in regard to potentially conflicting background processes.
vorpX can‘t really lag your OS normally. The only reason I could potentially imagine to cause such an issue is some obnoxious AV program that dislikes how vorpX monitors app launches, although even that sounds fairly unlikely.
If you use anything else than Windows Defender, try to uninstall your AV program for testing purposes and see whether that helps. Windows Defender will kick in instead, so there is no risk involved in doing so.
First please be aware that Guild Wars 2 is not officially supported, so I can’t say anything game specific. There should be no problem with hooking into Steam games under normal circumstances though.
For games with a profile loaded vorpX should display a dialog when the game starts that says „attaching to …“. if hooking into a game fails after a while this dialog offers various options how to deal with the matter. First thing you should try in such a case is installing a hook helper to the game folder. If that does not help, switching to ‚Alternative hooking‘ is worth a shot. You can do the latter either from said dialog or from the config app.
Apart from that please double and triple check for any potential conflict with some other program on your PC. disable everything running in the background, even if you think it has no impact on games. Hooking issues almost always are caused by some conflict with another program that also hooks into games.
You don’t need to import any settings for Portal 2, the default profile comes with full DirectVR support out of the box. Best to reset the profile to default in the config app if you already downloaded settings from the cloud.
No need to tweak anything besides setting the resolution to a 4:3 res as suggested by the vorpX start message, 1920×1440 will look great. If you don’t have this resolution on your PC, you might be able to add it as a custom resolution. Check the ‘Custom Resolutions’ section in the vorpX help for detailed instructions in that regard.
Not trying to change anyone’s opinion on G3D vs. Z3D, but for third person outdoor games like this one I strongly agree with dborosev’s post. Provided you aren’t after unrealistic over-the-top ‘dollhouse’ stereo 3D, in this type of game you rarely will encounter situations where you look at objects close enough for G3D being any better than Z3D in terms of the produced 3D effect. So in this particular case (and similar outdoor games) the performance benefits of Z3D indeed outweigh its disadvantages IMO.
I understand that you already did go through the trouble shooting steps, but this almost certainly is some kind of hooking conflict then. Ideally disable everything running in the background.
Did vorpX show a dialog that says ‘Attaching to: wow.exe’? If so, in case of a hooking fail after a while (about 30secs) this dialog should offer an option to install a hook helper to the game folder. That should be the first thing to try.
Apart from that: if you use any other AV program than Windows Defender, please try to remove it for testing purposes. Unfortunately some more annoying AV programs can’t be disabled unless you remove them. Windows Defender will kick in instead, so there is no risk involved. Third party AV is pretty much unnecessary in Windows 10.
If you happen to use a gaming laptop or some other dual GPU setup, please also (re-)check the related section in the trouble shooting guide. Desktop viewer working, but hooking into a game not working sounds a bit like a HMD-connected-to-wrong-GPU-problem.
I can’t really give you any other answer than the one to your earlier post re the same issue, sorry. No dice replicating this here, but I’ll revert a DX12 change that I suspect might affect stability for the next release.
However, considering that I can’t replicate the problem and so far noone else reported this since your original post, please also try to reset your game settings /vorpX profile to default, just in the case it’s an issue with your individual setup.
Maybe the game is not using the required API. Please make sure that the ‘Graphics API’ setting in the game options is set to ‘DirectX 11 Legacy’ (under Menu > System > Advanced).
Normally vorpX should take care of that automatically, but maybe that failed for some reason.
Also, just in case: always launch the current version from the WoW launcher, older versions played on custom servers may (and probably will) not work corectly.
Please don’t use any vendor specific features like DLSS currently. When in the future RTX cards become more widespread and more games get support for DLSS, I’ll look into that, for the time being please just don’t use it if it causes problems.
DX12 is currently disabled again for the game due to some issues with the DX12 Steam overlay for Oculus users.
Under normal circumstance there shouldn’t be any difference if you just mirror a game (i.e. vorpX doesn’t do 3D by itself). If you really experience a higher overhead while vorpX doesn’t do any 3D work, try switching between the old and new headset sync in the vorpX menu. In most cases the new headset sync should produce almost no overhead at all, but in some weird cases it may have the opposite effect unfortunately.
The profile now has automated FOV handling, there is no need to tweak it manually anymore. For FullVR mode the FOV is adjusted precisely to fit your headset FOV, in screen modes a reasonable value is chosen.
If for some reason you to want to change the defaults, you can apply an offset on the DirectVR page of the vorpX menu. No need to do that though.
No problem with Monster Hunter World here. If you start the game with Z3D enabled and then switch to G3D, you may have to restart the game. In more complex games live switching from Z3D to G3D doesn’t always work right since vorpX for performance reasons doesn’t do all the bookkeeping required for G3D in Z3D mode. Restarting such games with G3D enabled should usually help.
Apart from that please try to reset the game’s graphics settings to default, just in case.
I’d say both the 3070/3080 look like a good choice depending on your budget.
If you want to do more than gaming, the 3090 might be worth a look too. For GPU accelerated renderers in programs like 3dsmax/maya/blender etc. its 24GB of GPU RAM are probably worth the extra cost. For gaming alone however twice the money for ~20% better performance somehow doesn’t feel right to me.