Forum Replies Created
-
Posts
-
Make sure that the game window has input focus by clicking into it.
If that doesn’t help and you happen to use some extra invasive third party antivirus (i.e. anything other than Windows Defender), get rid of it. Imaginable that one or the other super annoying AV program may prevent keyboard hooks.
Also make sure that you don’t have any background apps running that also hook into games, typical candidates would be any kind of CPU/GPU utilities, gaming overlays, PC vendor bloatware, messengers, recording software and similar things.
Yes, Q3 has a higher FOV than Rift S. The vertical FOV displayed in CP2007 is the same as with your Rift S though, the horizontal FOV is actually higher, horizontically the full screen is utilized. So playing the game shouldn’t really be less immersive than before. :) But like said above, I’ll consider making the workaround optional.
The high FOV glitches happen almost everywhere to some degree.
No promises, but I’ll consider making the workaround optional for the next update.
Not a vorpX bug, actually a workaround for a CP2077 bug. The game has graphical glitches when raising the camera field of view above a certain point, mostly models/textures streaming in too late or not at all. The capped image zoom ensures that the camera FOV stays below the glitch inducing value.
Lesser of two evils. All you loose are a few degrees of vertical FOV, which is way better than the broken geometry/texture streaming you’d get otherwise.
Thanks for the heads-up. I totally missed that since I use SteamVR extremely rarely myself. Will check whether something has to/can be done on vorpX’s end as soon as I’m back home.
Normally vorpX should rename the desktop theater .exe automatically and by doing so circumvent this message, at least unless Valve changed how the Steam VR theater mode works.
Unfortunately I can’t check myself until later next week whether some Steam update maybe changed anything in that regard, but disabling the VR theater mode either in the Steam options or a game’s properties page always worked as an alternative until now. Are you 100% sure that doing that doesn’t help anymore?
vorpX changes the .ini from within the game while hooked into it, so any of Mod Organizer’s weird file redirections *should* *hopefully* also apply to changes made by vorpX. What probably won’t work right however is later restoring a prior .ini in the vorpX config app.
If in doubt, try playing without Mod Organizer. That way you can be 100% sure that both applying and reverting changes affect the correct files.
@ 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.