You should be able to automate large parts with a batch file and some command line tool that can change the resolution. An alternative would be AutoHotkey, which can change display resolution itself, I think. Never used it, but many consider it quite useful for Windows automation tasks.
I’ll add a selection for a preferred virtual display res in one of the next updates. Probably not directly the next, but that sounds like a useful idea.
You can give Tomb Raider a try—that game has built-in 3-D settings and the effect is fantastic. Have fun!
Thank you very much! I did find this profile on the cloud vorpx and have already applied it—really appreciate your help.
However, the 3-D effect isn’t very pronounced; I was hoping there might be a better patch available.
Found about the 1st person mod for Mass effect legendary 1 and 2. It seems that we dont have Vorpx profiles for Mass effect legendary 2 and 3 yet? Any chance they will come?
Great news !
Did you try with “SteamVR” or “OpenXR” in “Device Selection” ?
Note you can still use WMR + OpenXR with Windows 11 as long as you don’t update too much (23h2 should be fine).
It is very optimized and reliable, never freezes, and works with 32 bit games. I don’t know exactly what Oasis can do and if it’s as optimized as WMR but I guess it’s SteamVR only (according to the description, you can use OpenXR, but probably only the SteamVR’s version, so it may not always work as intended, especially with 32 bit games – In this case you’ll probably have to use “SteamVR” option). I may be wrong since I didn’t try yet (I would prefer to keep using WMR but I’m glad we have another option now). Let’s hope it will keep working as long as we need to.
PimaxPlay now has it’s own implementation of openXR they call Pimax OpenXR, which is a derivative of the indie developed PimaxXR app. From what I understand, they collaborated with the guy to get a version of his project into PimaxPlay, as a seamless integration. how exactly they differ I don’t exactly know, only that some claim the original PimaxXR still preforms a bit better.
PimaxPlay has a toggle to set your preferred openXR runtime, and tells you which one is currently active (Steam/Pimax/PimaxXR).
I tested all 3 with vorpX 24.1, but the only one that hooked properly was the Steam openXR wrapper, and was more sluggish than SteamVR proper, as you said.
I have since tested in 25.1, and Steam’s runtime didn’t seem as bad, but perhaps because vorpX redirected it like you said.
Sorry the answer is messy, but yes, Pimax has some sort of separate runtime to circumvent Steam. That is the whole point of it.
Hello, I’m a new VorpX user and I’m eager to get a 3D patch for the game WUCHANG: Fallen Feathers. What should I do, or when will the VorpX developer update the game list to include a profile for this title?
Just realized that the issue might have been caused by a small change in the installer I made yesterday, will probably work now if you try again.
If not:
If you didn’t keep your web installer, you can get one from the link below.
If the issue is caused by your antivirus, that might not work either though. If you use something else than Defender, really just get rid of it. There is zero reason to use some extra annoying third party AV since many, many years.
Request New Download
If you happen to use any other antivirus than the built in Windows Defender, try to
- Disable it (might be hard for the extra annoying ones)
- Exclude the vorpX program folder (usually C:\Program Files (x86)\Animation Labs\vorpX
- By far the best option: get rid of it. Windows Defender for all intents and purposes is more than good enough since more than a decade and I usually make sure any new release gets whitelisted by Defender if necessary.
I just started using the mod with everything default and noticed a big black area at the bottom of my view. Looking into it, I saw other people saying the same thing but found no solutions. It looks like it’s an issue with the aspect ratio of the quest 3, which is 1.87 (taller) compared to the other oculus headsets which are at 1.80. I changed the fScreenAspect variable in the Oculus.ini file, so no harm there. But that wasn’t enough, since it produced no change in game. I eventually found the iAspectRatioCorrection variable in the vpxCP2077.user.ini file and set that to zero, and that worked! It looked wonky because of something (maybe fov) but the bar was gone! However, as I opened up the in game vorpx menu it was set back to it’s original value of one instantly (I checked the file again). This instantly caused the black bar to come back. I haven’t been able to test further because of this (need the menu to change fov and stuff to see if this is the real fix) so there may be a better way to change the aspect ratio that I am not aware of, if so let me know.
The fix, I would imagine, would be something like one of these:
1. A config profile for the quest 3 different than the “Meta Quest Link: For Meta Headsets, eg. Quest or Oculus Rift”, that would be exclusively for the quest 3 and would make it work properly.
2. A way to turn off the automatic override of the .ini file when opening the in game vorpx menu. While I am not positive my small adjustments fixed all the issues, the main problem is that I can’t actually adjust the .ini file with current logic.
3. Some other way to change the Aspect ratio in the in game vorpx menu. I saw online references to user profiles or something in your full paid software so it may be possible in that, but not in the free cyberpunk mod.
I am aware that this particular game mod is a free mod, but it sucks to have a popular headset like this unable to be fully immersive due to the black area at the bottom taking significant space.
I see. I settle this issue then. Please try some other games. Preferably some with official profiles.
@Ralf
Thanks for reply, sent troubleshoot data to e-mail.
I know such kind of issues difficult to track, but from my experience helps to give to the user different old versions till find one which have issue. Then compare code, make minor changes and give again for testing. As I already found vorpControl64.dat is culprit most likely, could be easier and safer swapping it than sharing entire old builds. I can live with old version of Vorpx with internet disabled (don’t remember if any game need to be online), but don’t mind to test as described above. In that case, better to connect in some chat application to make the testing quicker, discord f.e.
SpaceEngine do have native vr, I just have it installed, so used it as one of testing applications which do not have native Vorpx support and quick to start. Not sure if there is any benefit to add vr via Vorpx to it, unless there are some exotic helmets which can’t run it by default.
@Ralf
Uninstalled, rebooted then installed again – no luck. Also noticed with SpaceEngine (running in windowed mode) after game is loaded height of the game window is reduced maybe by 10-25 pixels (can’t tell for sure about width). Also vanilla game allow mouse cursor go to any area, while with Vorpx it’s limited to client area where game front buffer is displayed.
Here is the list of the process in the task manager, as you can see I keep pc clean as much as possible, so there are no other apps which could mess with input or hooking graphics:
View post on imgur.com
Interesting, never heard of that. vorpX does use GetAsyncKeyState(), but not in the hooked game. It updates the keyboard state in the vorpControl app and then relays that to the game via interprocess communication. It does hook the function though inside the game for various reasons. I’ll check TR3 in Windows 10. If I find something unusual, I’ll let you know.
BTW: vorpX quite heavily relies on interprocess communication like the one described above between all its parts, which makes mixing components from different versions dangerous and likely to cause havoc. Don’t do that.
Just in case you may also try a uninstall/reboot/reinstall like I suggested to Dellrifter above. Just to be 100% sure everything is really at 25.1.1.
@Ralf
Regarding issues with non functional input. If I keep old version of vorpControl64.dat, then issues do not happen. Maybe there is another combination of files, didn’t test more.
The same problem happens in A Hat in Time. Reinstalling Vorpx via web setup multiple times – no difference. Even Vorpx own ctrl+alt+shift popup message ignores keyboard in A Hat in Time game. The only thing suspicious to me is when first time after long break started Vorpx and it initiated an update, at some stage of installation terminated it manually because was busy with other pc tasks. Still, that don’t explain why problem remains after executing web setup later, after reboot as well. As mentioned earlier, in the SpaceEngine some actions do work in certain moments, like game first popup warning with Esc button to hide it fails, then main menu works for cursor and mouse buttons both, then in-game cursor works but mouse buttons and keyboard are dead. I know some of the last patch(es) of Win11 (I’m on Win10) have changes to GetAsyncKeyState, breaking some apps, maybe workaround was done on Vorpx and it do not works in my case.