Forum Replies Created
-
Posts
-
That are general instructions that you should keep in mind if things aren’t done automatically for a game.
For Resident Evil 7 vorpX adjusts all settings. All you need to do is setting the resolution to 1280×960 like the message says when you start the game.
All you need to do is setting the game’s resolution to 1280×960 like suggested by the message that pops up when you start Resident Evil 7. Everything else is automatically adjusted by vorpX in this case.
Sounds suspiciously like an injection conflict with some other program on your PC.
Hottest candidates are: virus scanners, any sort of CPU/GPU utilities, game video recording/streaming software, chat programs and generally everything that can show notifictations in games.
Best way to trouble shoot this is to disable/uninstall background processes that are not required. Especially the types listed above.
You need to type the first few characters of a game’s name into the search box above the list.
If you still can’t see any cloud profiles listed, make sure that:
1. You are logged in.
2. vorpConfig.exe has access to the internet (might be blocked by firewall, antivirus or similar software).The most recent Unity profile with Geometry 3D support is Firewatch. However, it’s extremely unlikely that 3D will work with any other game using this profile. DX11 Unity profiles are almost certainly game specific.
You don’t need any cloud profile for Resident Evil 7, vorpX already comes with a profile for the game. You just need to start the game.
Older games indeed often look surprisingly good. I think an important factor in this is that the less detailed 3D-graphics of older titles work well with the relatively low resolution of current headset displays. At the moment support for older DirectX versions isn’t a priority, but I won’t rule that out for the future either.
If your monitor doesn’t support a resolution, you can either try to run games windowed or use a downsampling resolution (DSR or “Dynamic Super Resolution” for nVidia). That can be enabled in the graphics driver control panel. Doesn’t work with all games, but for those it does work with, it’s a viable option.
For most games it’s probably better to stick to lower resolutions even on a 4K HMD though, after all decent performance is at least as important as resolution. The 4K display still provides a better image (less screen door effect).
Sorry that I can’t be of more help. This is something specific to your setup, as said above probably an injection conflict. To be extra sure I checked the game again with the last vorpX release build – Steam version as well as an old CD version – after writing my original answer.
The only issue was the Direct VR rotation scan not working with the Steam version, which has been fixed for the next release while I was at it.
In high contrast situations you sometimes see something like that as an display artifact in any VR game, especially when reprojection (“Timewarp”) is used.
In your image the effect looks stronger than I would expect it though. Provided the image wasn’t retouched, the only option that comes to mind is that maybe time warping doesn’t work like it should, which would leed to motion blur/double images similar to what your image shows whenever you rotate your head.
In case you changed any settings on the Direct VR page of the vorpX menu, please check whether “Async. Rendering” is enabled. Having that on (which is the default) not only helps massively with performance, it also ensures that Timewarp is working.
Also make sure that the game is running at 45fps min. Lower frame rates can’t be compensated that well with time warping.
Quake 3 Arena should work without problems normally, it’s one of the usual OpenGL test cases here and thus checked regularly. Unlike Direct 3D hooking OpenGL hooking isn’t even timing sensitive, so there is not much that can go wrong besides an external factor, most likely an injection conflict with some other program on your PC.
BTW: After you got it to hook, please disable FluidSync in the vorpX options. Due to the way vorpX handles OpenGL, FluidSync doesn’t work well with it. That will be be done in a different way in the next vorpX version, for now FluidSync should be disabled manually for OpenGL games.
There is an issue with antialising in Bioshock 1+2 causing a massive framerate drop with vorpX. If you have AA forced through your graphics driver, disable that. Also any ingame AA should be turned off if such an option exists (can’t remember currently).
Normally vorpX auto updates on launch when a new version becomes available. You can also always install the latest version with your web installer in case the auto update fails for some reason.
More profiles will be added in the future. I’m not quite sure yet how many will be in the next version since currently there still is a lot of programming work being done. As soon as that is out of the way, new profiles will become the main focus.
Try to exclude the game folder from your virus scanner. The access denied issue is probably related to the virus scanner blocking the game .exe when vorpX hooks it. Seems to happen more often than before after a recent Windows Defender update.
Trying two or three times usually does the trick, excluding the game .exe (or the whole folder) from scanning is a more permanent option.
The game itself still works fine. I incidentally just checked it an hour ago during the daily check-a-few-games-to-see-whether-you-broke-something-today routine.
Try ALT-C if the cursor is invisible. vorpX usually showns its own cursor since the normal Windows “hardware”-cursor often does not display correctly in stereo. Sometimes however keeping track of whether the cursor should be visible or not may not be 100% reliable. Pressing ALT-C to display the vorpX cursor in many cases helps with that.