Forum Replies Created
-
Posts
-
Mouse based head tracking is always enabled per default before running the DirectVR scan. If that doesn’t work for some reason, please try a full factory reset in the vorpX config app and make sure you didn’t accidentally disable mouse input in the game options if that is possible. BTW: disabled/broken mouse input can also be a reason for memory scan failures.
Your last key should still be valid. You only need a new key when the request code changes, e.g. after a Windows reinstall or hardware change.
I have sent you another one anyway.
If you are using an Oculus headset, please switch to SteamVR like suggested by the message shown in the headset when you launch the game in Oculus mode (‘If the games hangs at loading the game world, try to set vorpX to ‘SteamVR’ in the config app.’).
Had forgotten about that myself, but following my own advice did the trick. ;) I’ll add the message to the one shown in the top left corner of the game window instead of only showing it in the headset, just in case.
If you still encounter this issue after switching to SteamVR, let me know. Normally that should fix it.
Soma uses a custon OpenGL based engine. While vorpX has G3D support for older ‘fixed function’ OpenGL versions, currently that is not available for modern shader based OpenGL like used by Soma. *Might* happen at some point, but don’t hold your breath for it. There just aren’t enough popular OpenGL games to make this a priority.
For a lot of supported games vorpX can handle that automatically, so after adding the resolutions to your GPU driver you essentially just select a preferred quality in the vorpX menu. Rule of thumb: go as high as you can without sacrificing too much performance. 1440p typically looks fine, but no harm in trying something higher if that doesn’t hurt performance too much.
If vorpX can handle resolution automatically for a game, the above is all you have to care for.
If vorpX can’t handle resolution automatically, there is one other thing to consider: aspect ratio.
Play style Cinema/Immersive Screen Mode: a bit up to your personal preference, but generally I would prefer widescreen (16:10, 16:9) resolutions for these play styles.
Play style Full VR: to avoid rendering stuff that is never shown you typically want a ‘narrow’ res in FullVR mode (or 4:3 if a game doesn’t work with those) if possible. So far still easy, there is one potential exception though that makes Full VR a bit more tricky: if you have to lower ImageZoom a lot to compensate for missing FOV in a game, you may see black bars not only above/below the image, but also left and right with ‘narrow’ or 4:3. In that case widescreen would make sense even for FullVR.
Games have to run on the GPU that your headset is connected to, there is no way around that. If your graphics card has other ports besides the HDMI out (it probably will have at least one display port and/or DVI) you could use an adapter.
I read your other post. Every post gets read, unfortunately it’s just not feasible to check everything right away. Thanks for your understanding. If I can replicate the issue in a start area, I’ll see whether something can be done.
Unfortunately I can’t check the whole game though, so in a vast online world like WoW there might always be some offending shader somewhere. If the glitch only occurs in some areas, consider switching to Z3D in areas where it is most distracting.
You have to make sure that the games run on the same GPU as your headset is connected to. Ideally disable your onboard GPU entirely (e.g. in your PC’s BIOS if possible).
BTW: You can find infos like this that cover common issues and pitfalls in the trouble shooting guide on top of this sub forum (or in the vorpX help) without having to wait for a reply.
vorpX captures the video in MPC-HC before it gets fully processed by MPC-HC to ensure it doesn’t get re-sampled more often then necessary. Combined with vorpX’s own image processing that leads to a farily good quality, but it also means that almost certainly some of the things on your list are applied after vorpX grabs the image and thus will have no effect on what is sent to the headset in the end.
What exactly from your list is applied before vorpX grabs the image and what afterwards I don’t know, sorry. Judging from your list however my personal guess is that for a dedicated videoplayer buff like you no VR solution will be really good enough anyway. Unlikely that current headset display resolutions will meet your expectations, regardless how good the software is.
BTW: Even if all your filters are applied before vorpX grabs the image: filters that optimize the video for your desktop res and refresh rate don’t really make too much sense when the image afterwards gets send to a headset with a totally different resolution and refreh rate. Less is probably more here.
Try to uncheck the ‘Use headset audio’ checkbox in the config app. That way vorpX won’t change the output device.
Never noticed anything wrong with the distant land feature either. The distant land is probably just, well, too distant to have any noticable stereo effect. The farther away something is the smaller the difference in perspective between both eyes gets, resulting in less stereo.
The decreasing difference in perspective over distance is actually what mainly lets your brain derive depth from two images in the first place, be it in VR or in the real world. Since your eyes are only 6-7cm apart after a few dozen meters the difference in perspective between what you see in both eyes becomes so small that it isn’t really noticable anymore.
If you mean a Samsung Oddyssey then please make sure that vorpX is set to ‘SteamVR’ in the config app. Also SteamVR and Windows Mixed Reality portal have to be running.
If you continue to have problems, please first and foremost check for potential problems with other programs on your PC that may also hool into games. You can find more detailed information in that regard here.
In contrast to nVidia cards for AMD cards vorpX currently can’t check whether global VSync is on or off, so this message is always shown as a precaution. If you are sure that it’s not enabled, you can safely ignore the message.
BTW: most of the time it doesn’t matter anyway since usually vorpX can override VSync.
The FOV is computed automatically to fit precisely the FOV of your headset. Provided the setting still does what it is supposed to do, the FOV is correct once vorpX has adjusted it. Please reset the profile to default in the config app if you made any changes to related settings.
Just in case also make sure the game runs with a 4:3 resolution. Normally vorpX considers such things when it computes the FOv for games, but I’m not 100% certain at the moment whether the FOV would be right at other aspect ratios for Morrowind.