Forum Replies Created
-
Posts
-
Please check whether you run Steam as admin, with some compatibility mode setting or maybe with a different user account. All of that could lead to issues. Since the Desktop viewer works and has no issues finding the Oculus runtime, this almost certainly is some odd configuration issue in regard to Steam on your machine.
As a more general hint, please also try to disable your virus scanner in case you use anthing else than Windows defender, my first guess would be the one above though.
That sounds like a lot like something on your PC interfering with vorpX. Please follow the steps in the trouble shoot sticky post on top of this sub-forum.
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 every program running in the background that would not be there after a fresh, Microsoft only Windows install.
Apparently I misread you first post, sorry. That sounds like a neat idea, although it probably would be better to have actual 3d models. Not only good for ‘fixing’ low FOV, but a 3d-modeled helmet also improves immersion quite a bit in general. See Bioshock 2. Maybe three pre-defined helmets to choose from for race, sc-fi, fantasy.
As this isn’t exactly essential, I won’t promise anything, but I like the idea.
If you use any other AV software than Windows Defender, please try to uninstall it. Some of these programs don’t really allow their users to disable them.
Please allow some time for an answer. Thanks for your patience.
Update: all set now. If you didn’t receive a mail, please let me know.
Are you using an older vorpX version (latest is 17.2.3)? Since a few releases there is an option to import stereo and mono 360° images in a wide variety of formats.
The importer is in the config app (“Cinema Environments”) and also has a few links to 360° images sources. To use them in the game, enable Cinema Mode and then choose the “Image” Scene, which then let’s you flip through your imported backgrounds.
Being multiplayer only it would make sense that overwatch uses strong protection against hooking into it.
No issue with L4D2 here, it’s one of the usual test cases that are checked on a semi regular basis here. Maybe something is interfering with vorpX on your machine, might make sense to do a little bit of trouble shooting by closing everything that runs in the background.
Programs that may cause issues are: first and foremost aggressive virus scanners (use Windows Defender if you don’t), but also: any kind of GPU/CPU utility, game video recording/streaming software, chat programs and generally everything that can show notifictations in games. In general everything that alsi hooks into games can cause trouble. Also try to disable the Steam overlay. vorpX should take of that if necessary with the latest version, but it can’t hurt.
Doesn’t matter normally.
There may be an exception here and there in case the version sold on other platforms differs from the one on Steam in a way that affects vorpX, but that is quite rare and definitely not the case for GTA V.
The old Return to Castle Wolfenstein for examnple required different Direct VR settings for the Steam and the GOG version, but in the vast majority of cases it doesn’t make a difference.
Sounds like swapped eyes then, some movies have the left/right view reversed. You can change that in the vorpX ingame menu too.
Please make sure to update to the latest vorpX version 17.2.3, which was released yesterday. This could happen fairly often after a recent Windows Defender update, should be OK again now. Alternatively disable real time scanning in your Windows Defender (or other AV software) settings. Shoildn’t be necessary anymore though.
Overwatch isn’t supported, so like with all games that never were checked here, it might or might hook. Not sure about Black Ops, sorry. Will be checked before the next vorpX update, maybe a game patch broke something.
You don’t have to do anything normally for the Touch controllers to work. Per default they are in kb/mouse mode emulating standard WASD/mouselook controls. Please try a factory reset (trouble shooting page of the config app) to reset all settings to their default values, just in case you disabled them accidentally.
The next regular version (in this case 17.3) is of course also in the works, but not quite ready yet. The recent hotfixes for the 17.2 branch were necessary due to the severity of the fixed issues, which had to be addressed ASAP.
vorpX 17.2.3 has been released. This is a hotfix release mainly due to a highly annoying issue that showed up after a recent Windows Defender update. It contains the below fixes:
- Frequent “Access denied” errors when launching games with vorpX after a recent Windows Defender update
- Some profile fixes, most notably 100% correct G3D shadows in Fallout 4