Forum Replies Created
-
Posts
-
You already mentioned the “fix” yourself in your original post, although I wouldn’t call it that way since nothing is wrong. When you max out the ImageZoom setting you can fill the entire screen, the correct vertical alignment in that case is ensured by some pixels of the original image being cut off at the upper edge.
BTW: The ImageZoom setting at 1.0 means that your vertical FOV is the same as Oculus uses for their headsets. They nailed the compromise between pixel density and FOV quite well, so my personal recommendation would be to leave it that way.
Using the controllers as pointers wouldn’t be hard, but isn’t implemented currently. One of those things on my eternal nice-to-have-list…
BTW: With the controller vizualization switched to ‘Hands’ in the vorpX menu the boxing game might be even more fun.
That is intentional and the correct way to handle it for vorpX. Unlike native apps vorpX’s rendering is done in two steps: in the first step the game gets rendered, in the second step the final image is rendered to the headset by vorpX.
The effect you noticed exists because in contrast to normal monitor games all VR headsets (to varying degrees) have a slightly asymmetrical view frustum, i.e. they render more below the camera than above. Headset vendors do that to gain a few precious pixels where it counts since the human brain tends to concentrate on the ground.
Now when vorpX in its second render step aligns the symmetrically rendered game image to the asymmetrical headset frustum, the effect you noticed arises. Just centering the game image on the headset screen instead causes distortion in FullVR mode when you rotate your head due to vertically misaligned viewpoints between the game image and the second render step. In other words: what you want to match between step 1 and step 2 are the camera centers, not the image/screen centers. Both are not the same since the game’s view frustum (first step) is vertically symmetrical while the headset frustum (second step) isn’t.
Controller bindings (and all other settings) are saved when you click the OK&SAVE button in the menu instead of just closing the window.
Boatloads of games installed: Yes. Savegames all the way through for all of them: No. Unfortunately my time-decelerator broke irreparably a few years back. ;)
My sympathy level for AV vendors slowly has been reduced to absolute zero over the past seven years, TBH. Some of these programs cause just as many problems as they pretend to solve. Not to speak of flatout unbelievable cases where a well known AV vendor sells the browser histories! of its users like recently Avast…
The major problem with some of these tools is that even if you think you disabled them, they aren’t really disabled. Same for exclusions. Adding an exclusion for the actual scanner doesn’t necessarily mean the program/folder is excluded from everything. BitDefender for example blocks Windows functions used by vorpX to hook into games unless you disable this block separetely. Wouldn’t really be surprised if your AV does something similar, so that might be something to look into.
If you are on Windows 10, my recommendation however would be to just use Windows 10’s built-in Defender to make your life easier. It kicks in when you remove third party AV. In most recent tests Defender is on par with the major third party AV programs while usually causing less hassle. As a bonus unlike others Microsoft always reacted super-fast in the past when there was a false positive detection.
Please remove Reshade and let me know if the issue still occurs afterwards. As much as I’d like to, I can’t really check issues that might just as well be caused by an intefering mod.
I would also need a savegame. IIRC Kingdome Come is a pretty slow game, I don’t think I will be able to play until I get a bow. You can send the savegame to support |at| vorpx com.
On a general note: removing mods, especially mods that hook into the render pipeline, should always be the very first thing to try in case of issues. Best avoid using anything that also hooks into games together with vorpX in the first place, that always bears a certain risk of causing major havoc.
I’ll check whether something has changed recently in the games you mentioned above.
Stuff like this usually is caused by other tools that also hook into the Direct3D ‘Present’ functions though. If you happen to have 3D-Vision installed on your PC, please also make sure that is disabled apart from any other tools and overlays.
Dolphin already has a working VR component.
That’s why I never cared to check it with vorpX. The VR build is fairly outdated now though and way more buggy than current regular versions, so a vorpX profile might still be useful. Also some may prefer the vorpX cinema mode. Wasn’t really a big deal due to the built-in stereo.
Possible to get an XBOX 360 EMU working or ps2? or ps1?
I tried PCSX2 a long time ago, but no dice as far as 3D is concerned. A lot has changed since then though, in vorpX as well as probably in the emulator, so it might make sense to check it again. Will do that before the next release.
Never heard of this before, but maybe the game changes some projection parameters when you aim with the bow. If the game zooms in when you aim with the bow, the behavior would be perfectly normal. Same as taking a photo with a telephoto lens. More zoom (less FOV), less depth.
Unfortunately Valve broke the existing workaround in the latest Steam version since they now check for the DLL on every game launch. I have it on my to-do list, for now try to switch to SteamVR, which might help somewhat. Nothing else I can recommend at this point.
In HL2 you might see a frame with the wrong FOV flickering in every once in a while, but that is not supposed to happen in the other two games.
Please make sure that you don’t have anything else running in the background that also hooks into games. Many other programs also hook into the same functions as vorpX to show ingame notifications and similar things, which can cause issues like this one. Best to disable everything you may have running in the background, especially any GPU/CPU tools, FPS counters, messengers etc.
ALso try to disable the Steam overlay.
If Dolphin has SBS output, you might be able to get it working with one of the vorpX profiles that handle native SBS, depending on the API Dolphin uses that would be for example:/del>Shadow of the Tomb Raider (DX11), SBS used per default.
MPC-HC (DX9), SBS has to be enabled in the vorpX menu
VLC (OpenGL), SBS has to be enabled in the vorpX menuI uploaded a profile to the cloud that utilizes Dolphin’s SBS output. Should work with D3D11 and OpenGL output. I’ll add automated settings with the next vorpX, for now please select D3D11 and stereo SBS in Dolphin’s graphics options.
That would be only the case if you added any of the .exe files to your copied profile that is already covered by the official profile. Shouldn’t be possible to do that though, vorpX is supposed to complain if you try.
When you make a copy of a profile that has e.g. ‘Some.exe’ assigned to it, and you then assign ‘SomeOther.exe’ to that copy, the copied profile is loaded when you start SomeOther.exe.
The game is quite popular and not known to be probelematic in any way as far as hooking is concerned. Almost certainly a conflict with some other program on your PC.
If you use anything else than Windows Defender your AV program the first and most likely candidate. Apart from that try to disable everything you may have running in the background, even if it doesn’t cause issues in other games. That’s the best way to trouble shoot a problem like this.
As a last resort you can also try to check the ‘Alternative Hooking’ checkbox in the config app. Don’t forgot to uncheck it again later even if it helps. It’s not better, just different, and some games will definitely fail with it.