Looks like it is definitely the Direct VR mode. Switched off and scopes work as normal ..read more

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 Foverated rendering would only be applied to this second step, which only requires a relatively tiny fraction of work compared to the actual game rendering. Most likely you end up with the drawback of foveated rendering (blurry screen edges), but won’t see an ..read more

Thank you willjcs, I will test this next time I can. Probably in a week. I will try all these extra steps you sis which I didn’t do ..read more

vorpX is on the market since over 10 years. Don’t you think someone would have noticed during these 10 years if noone gets their activation keys? ;) Your key has been sent automatically to your hotmail.co.uk mail address. I have resent it manually just now, just in case the first mail didn’t go through for some reason. If it still didn’t reach you, let me know ..read more

Are you playing the original version or remastered one? I played the original version with vorpx years ago and never finished the game, it seemed to be very crash happy with vorpx back then. In the back of my mind I all ways wanted to make a new playthrough ..read more

im having same issue i am a new to this and not even got my key and yes check all emails spam ect and nothing i feel like this guy that this is a scam if if that is the case will had to my uncle as he works in the police force in cyber frund uk ..read more

update 17/5/24: Finally it seems that it does not crash in Windows 10 with this configuration: -Without installing my AMD RTX specific software – Preliminary steps: – Start the game without vorpx and adjust all settings as you require – close the game and secure bioshock.ini and user.ini to prevempt changes: even if you set vorpx to not change the game settings, it CHANGES the user.ini every time the game crashes… To fix it I had to set both files to read only AND change permissions to disable inheritance AND allow ONLY my user to have permissions, and not SYSTEM or any other user. – In VORPX ..read more

Hello, I think I’ve got it ! After applying your settings, the crashes were still happening, but after changing vorpx to SteamVR there is no error at all, apart from the minor issue about having to press ctrl+alt+del and esc after the initial load for the latest savegame. So, my settings are the ones mentioned from @Boblekobold except my own resolution, AND use this sequential steps: – IN VORPX, USE STEAMVR. Launch Vorpx -Connect the quest 2 to the pc with Virtual Desktop (the one in the oculus store, not the one from Steam) using VDXR. Launch the game: Vorpx will attach to it and will launch ..read more

The last supported version is Windows 10 (which is almost 9 years old now already). Older versions are not supported anymore ..read more

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 ..read more