Forum Replies Created
-
Posts
-
With the Link cable there is no need for using SteamVR with a Quest usually except for some DX12 games. Try to run vorpX in native Oculus mode by selecting Oculus as your headset type in the vorpX config app.
SteamVR is only needed for Virtual Desktop. In that case you have to select SteamVR as headset type in the vorpX config app AND enable SteamVR capturing in Virtual Desktop.
The Go works with vorpX in SteamVR mode and an additional streaming app like ALVR that can stream SteamVR content to the headset.
Caveat: your PC is a bit on the low end of the spectrum of what makes sense for vorpX, so for newer, more resource hungry games you’ll be limited to the faster, but less accurate Z3D 3D method. Apart from that everything should work fine.
Just a heads-up that usually any settings changes vorpX applies are pretty important for a seamless experience. Even more so for FullVR games like Metro where vorpX makes sure that the game FOV precisely matches the FOV of your headset. Without automatic settings you would have to do that manually.
That said, if you want to experiment with games that already have an official profile, your best bet is making a copy of the game‘s .exe and then create a new profile for that copied .exe. You can find a short introduction in that regard in the vorpX help. For games with DirectVR support as good as the Metro games there isn‘t really any point in doing that though.
Gamepad: some games do not allow mouse and gamepad input at the same time. Whenever that is a known issue with a game, vorpX‘s built in gamepad to mouse/keyboard mapper is used as long as vorpX has to emulate a mouse for head tracking. the alternative to that in games that dislike simultaneous mouse/gamepad input would be no gamepad at all (or no head tracking).
The good news: in games with memory scanner head tracking support (like Metro) gamepads work natively again after a successful scanner run, since with memory scanner head tracking no mouse emulation is necessary anymore.
Rule of thumb: if the gamepad to mouse/keyboard mapper is enabled in a profile, there usually is good reason for that.
There is an unfortunate bug in the current version where vorpX can lose connection to the headset after minimizing a game (e.g. with ALT-TAB). Will be fixed in the next update. For the time being please run the game windowed as a workaround.
Please check for potentially interfering programs. The pinned trouble shooting post on top of this sub forum has more details on the matter. There isn’t really anything else to suggest than what is posted there already.
Most importantly:
If you happen to use any other AV program than Windows Defender, try to remove it for testing purposes. Some more invasive AV programs are fairly hard to disable, i.e. they may have several protection modules that have to be disabled separately. Some even actively block hooking functions.
There is no real need for invasive third party AV programs on Windows 10. Windows Defender is more than good enough for several years now and kicks in automatically when you remove third party AV.
@moarveer: that doesn’t really sound right. I played a start portion of the game for several hours years ago without encountering anything unusual performance wise. Either on a 1070 or a 1080, don’t remember anymore. Also the game is fairly popular, if there were any unusual performance problems, I’m sure I’d have heard about that in the past four years or so since the profile exists.
Might make sense to reset everything to default. The game options as well as the vorpX profile.
Check whether DX11 is set as renderer in VLC. vorpX normally does that automatically, but maybe that failed for some reason, e.g. if you disabled automatic settings or vorpX can’t locate the settings file.
If not even the attach dialog is displayed for a program that has a profile, something gets in the way big time. Also make sure to start the game directly from Steam, not with a shortcut (see above).
If you happen to use any other AV program than Windows Defender, try to remove it for testing purposes. Some more invasive AV programs are fairly hard to disable, i.e. they may have several protection modules that have to be disabled separately. Some even actively block hooking functions.
There is no real need for invasive third party AV programs on Windows 10. Windows Defender is more than good enough for several years now and kicks in automatically when you remove third party AV.
vorpX shortcuts usually don’t work with games that require a DRM client like Steam, Origin etc. If you start such a game directly instead of from the client, it closes itself, and then the DRM client restarts it. This procedure renders the shortcut essentially useless. vorpX shortcuts only work with games that aren’t bound to a DRM client.
You have two other options though in case of hooking problems:
The “Attaching to…” dialog shows two trouble shooting options after a while: installing a hook helper to the game folder or changing to a different hooking method. One of those should be able to help with most hooking conflcits without getting to the bottom of the matter.
If that doesn’t help, please check for potentially interfering programs on your PC. The pinned trouble shooting guide on top of this sub forum has more details on that.
Just a little heads-up that the next vorpX version will have the ability to show the actual cursor icon of hardware cursors in the headset instead of using the vorpX cursor.
That was actually something I had on my nice-to-have list for ages, so thanks for the incentive to finally look into it.
Please switch to Z3D (should be the profile’s default) if G3D is too glitchy. On some maps G3D works well, but on others apparently it doesn’t. With Z3D you won’t encounter such issues.
BTW: directly switching from Z3D to G3D causes additional glitches, so either way you’ll definitely have to follow the hint shown in the menu that recommends a game restart after switching to G3D.
It‘s not about the cursor having the wrong depth. The vorpX cursor only appears if a game uses a so called ‚hardware cursor‘ that is not part of the game rendering, but gets superimposed later by Windows. The actual alternatives if a game uses a hardware cursor are: vorpX cursor or no cursor at all in the headset.
Just checked this, but can’t replicate the issue here. You should see a vorpX cursor normally since the game cursor can’t be stereofied. If you see the normal game cursor instead, try to press ALT+C. That’s pretty much the only potential issue I can imagine.
Apart from that, please try to reset both the game settings and the vorpX profile to default (in the config app). That can never hurt.
Shouldn’t really be necessary normally, but glad you could solve it.
The game uses an unusual hybrid DX9/11 approach with the new UI, where the game is still DX9, but the menu is drawn with DX11. Maybe hooking DX11 failed on your machine for some reason.
If you didn’t do that already, please first try the options offered in the ‘Attaching to…’ dialog after a while, i.e. installing hook helpers to the game folder and the alternative hooking method. One of these options should help with the majority of hooking issues without having to get the bottom of the matter.
If that does not help, please try to launch a few games, afterwards create a trouble shooting data archive in the config app and sent that to support at vorpx com. Maybe I can spot something in the logfiles or your system config that you overlooked.