Forum Replies Created
-
Posts
-
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.
Please first make sure that you use the latest version of both the game and the mod. The mod utilizes the Cyber Engine Tweaks modding framework, each CET version only ever works with the Cyberpunk version it was released for.
If things still don’t work after checking the above, check the huge instructions panel to the right of the tutorial screen. In case the game got an update that requires a CET update, you’ll find all you need to know to update CET there.
Please first double check whether the game really has TrackIR support. If you are 100% sure about that, check whether you maybe have to enable it somewhere in the game options. In some games it’s not on per default. If TrackIR is actually enabled in a game, vorpX does auto-detect it reliably under normal circumstances.
If it still doesn’t work once you are sure TrackIR is both available and actually enabled, the only thing I can possibly imagine is that maybe this specific game implements TrackIR differently than newer games with TrackIR support. Not much could be done in that case unfortunately.
If the game has TrackIR support, you should be able to easily switch it on yourself in the vorpX ingame menu. vorpX can detect if TrackIR is available in a game and displays according options in the menu in that case.
Extremely unlikely that 24.1 is responsible for your hooking issues. The general hooking mechanism hasn’t changed at all. Check what else might have changed on your system. There almost certainly is something else going on.
Oculus Link restarts itself when the Windows display config changes, which happens occasionally due to the new virtual vorpX monitor. Not a bug on vorpX’s end, just some weird behavior of the Oculus app. Easily avoidable by starting vorpX before the Oculus app, not really an issue at all.
That said, you can roll back with the procedure mentioned in the 24.1.0 release post on the front page. (1. Uninstall vorpX, 2. Reinstall with the regular installer). If you didn’t keep your original web installer, check the support FAQ for how to get a new one.
That sounds definitely wrong. Please check whether maybe something is running in the background that also hooks into games, eg. some overlay, GPU utility, screen recording app, messenger etc.
More detailed information on the topic can be found in the help under ‘Trouble Shooting’
1. If I understand the question correctly, that would basically the same as switching to FullVR mode and then scaling down the image with the ImageZoom setting.
2. You should be able to use mouse emulation head tracking with the desktop viewer as well by adjusting the head tracking sensitivity. Switching to FullVR and scaling down the image like described above should also work.
The hooking related wish doesn’t really make sense. vorpX already automatically inserts hooks on game start (and destroys them on exit). Otherwise it wouldn’t work (obviously). The only thing in that respect vorpX *may* do afterwards is that in case the normal hooking fails it displays a trouble shooting assistant that among other things offers to install hook helpers. That’s a good thing, otherwise there wouldn’t be an *additional* fallback hooking method.
As far as external docs in addition to the in-app tooltips and notifications are concerned: there are HTML help docs with additional information that can be accessed either from within the config app, a shortcut on the desktop or a shortcut in the start menu. I’ll consider adding even more documentation as soon as I get the impression that more than 0.05% of you guys actually read the already easily available information. ;)