Forum Replies Created
-
Posts
-
@ Seph :
The virtual monitor is only active while vorpX is running. A few minutes after closing the vorpX control app it gets disabled. That is done on purpose to minimize potential issues with other software or multi monitor setups. Could that be your issue?
I had to disable the subscribe option, sorry. A couple years back one particular pinned thread over time got so many subscribers that in the end the amount of notifications sent after each reply made the mail provider think I was an e-mail spammer…
First please check the ‘Essential Hints’ and the ‘Performance Optimization’ sections in the vorpX help. Should answer the most common questions you may have as a beginner. You can access the help either from the config app or its desktop shortcut.
If that doesn’t answer your question, feel free to ask again here.
Please make sure to send the key request from the same mail address that you entered into the order form. The mail address you used to register here on the forum is not in our database.
I don’t recall to ever have seen this message, but it might be related to some overzealous antivirus program disliking vorpX.
If you use any other antivirus than Windows Defender, exclude the vorpX program folder from the AV scanner or – even better – uninstall the third party AV. Windows Defender will kick in instead.
Nothing wrong with trying, but it’s highly unlikely that foveated rendering will have any positive impact on performance with vorpX. Rendering is a two step process with vorpX:
First the game gets rendered at the resolution set in the game options. vorpX then processes the resulting image and sends it to the headset. Retroactively applied foveated rendering would affect only the second step, a relatively tiny fraction of rendering-work compared to the actual game rendering. Most likely you end up with the drawback of foveated rendering (blurry screen edges) without any noteworthy performance benefit.
The same also applies to anything else that sends flat games rendered on your PC to the headset BTW, just in case you are wondering.
The last supported version is Windows 10 (which is almost 9 years old now already). Older versions are not supported anymore.
Renaming the main .exe and assigning that to your profile works with a lot of games. The official one shouldn’t crash the game though. Probably something else going on.
If renaming the .exe doesn’t work, you can revert back to the last regular build by 1. uninstalling 24.1.0 and 2. reinstalling with the regular web installer. Do not leave out the uninstall step, but keep the registration when the uninstaller asks about that to avoid having to re-authorize.
If you didn’t keep your original installer, you can find a link in the support FAQ.
If a game as undemanding as the original Source version as Dear Esther is working poorly there definitely is something wrong. That should work perfectly fine even with a mid tier GPU from 7 or 8 years ago.
Please double and triple check for any stuff running in the background that may also hook into games.
Also if you are using a Quest headset, kame sure that vorpX is set to native ‘Oculus’ mode and do not use any extra app like e.g. Virtual Desktop. Use Quest Link instead.
Hmmm. First please try to reset the profile to default in the vorpX menu. All you should have to do for KCD is running the DirectVR scanner for FOV and 1:1 low latency head tracking, plus potentially adjusting the resolution in the vorpX menu.
If the issue still occurs after resetting the profile and running the DirectVR scanner, make sure that vorpX is set to native Oculus mode or OpenXR, not SteamVR. Shouldn’t really matter, but worth a shot. If that still doesn’t help, try to disconnect the PlayStation gamepad.
I can’t really comment on the game specifically because a while ago some clown deemed it appropriate to drag vorpx into his own legal fuckup with its publisher, sorry. From what I heard it still seems to work for others though.
Hooking issues means conflict with some other tool that also hooks into games in 99% of cases.
Check the trouble shooting post on top of this sub-forum for details.
If you happen to use Mod Organizer, you might have to check whether it stored MO specific .inis somewhere that it loads instead of the actual .ini in your documents folder. That tool does some seriously weird shit in regard to file access redirection without really explaining any of that.
Starting the Skyrim launcher from MO and changing the res there might also help in that case.
General hint: you can comfortably revert changes vorpX does to game .ini files in the vorpX config app. No need to search for the backup files on your PC manually.