Forum Replies Created
-
Posts
-
@ y0urd0g: I understand that you said you already went through the trouble shooting guide, but please double check for any potential conflicts with other programs on your PC. Hooking issues with multiple games almost certainly are related to some other program also hooking into games and thus creating a conflict.
The most likely candidate is AV software, others are listed in the trouble shooting guide above. The best method to trouble shoot this is to exit everything that is running in the background, even if you don’t suspect it to cause an issue.
Additionally you could try the ‘Alternative Hooking’ checkbox in the config app. Be aware though that alternative hooking is not better per se, it’s just different and some games definitely will require the default method.
If double checking for conflicts does not solve the issue, please create a trouble shoot data archive in the config app after trying to start a few games and send that to support at vorpx com for inspection. Maybe you overlooked something.
Settings changes (FOV, resolution, tweaks): yes. Memory scanner (head tracking): no. The scanner is tuned for the original Halo campaign, you should see a message in that regard when you start a scan.
If you didn’t keep it, you can get one here: https://www.vorpx.com/request-new-download/
BTW: You can find answers to basic questions like this one in the support FAQ without having to wait for a reply.
If you received today’s update to 20.2.0, you already have the official profile. If not check whether maybe your firewall blocks vorpControl.exe from accessing the internet or alternatively reinstall with your web installer.
Short update: just did some additional OpenGL testing with the release build to be extra sure. Everything fine here, so I would definitely need more information regarding the games you had problems with.
I noticed that some OpenGL games could inadvertantly run at twice the headset framerate though. Not critical, but obviously a waste of GPU/CPU power, so I uploaded a new version of the update without this glitch.
The version number is still the same, so no auto-update. If you want this new version, please reinstall with your web installer.
Can you be more specific? Pretty much all OpenGL games with official profiles have been tested during development. How vorpX attaches to OpenGL games hasn’t changed at all, just the G3D implementation has changed.
Whenever you suddenly encounter issues with attaching to games after an update the very first thing to suspect is some AV program running amok. Try to disable it for testing purposes, especially if you use anything else than Windows Defender.
Error 2 means that the profile database is missing. If that happened during the update, something must have gone *seriously* wrong while merging in the new profiles. Should be next to impossible for the update process to cause this.
Anyway, as suggested by the error message a reinstall will fix the issue.
BTW: I removed your other post regarding the same issue. Please just one post per issue. Thanks!
3D-HUDs are a feature you can find in most G3D games. If available in a profile vorpX separates HUD/menu elements and allows you to change the HUD/menu size and stereo 3D-depth in the vorpX menu.
I strongly fall into the latter category, but still couldn’t really warm up to the game ultimately. I played a bit more after several of you guys said two or three hours aren’t enough, and it got definitely better, but in the end I stopped being halfway through or so. Maybe just me getting old. Admittedly it’s becoming increasingly hard these days to get enthusiastic enough about any game to call it a 10/10.
Enjoy your ride though guys, don’t let a grumpy old man distract you. :) At least that way I have more time for vorpX.
Unless something is severely wrong with your setup it has to work. With the main eye option used only one eye gets stereo-shifted, so the other eye shows exactly what the game would show without stereo 3D. No way that could fail.
You may have to recenter head tracking (ALT+SPACE). If it’s not centered, the default position would be off. With (re-)centered tracking the image that is shown for your main eye is exactly the same as the game would show in mono on your monitor.
Interesting, although that’s not the issue as far as the official profile is concerned that will be included in the next vorpX version as that doesn’t have any gamepad override enabled in the first place. From the looks of it I’m 99% certain that the jitter in question is rooted in the graphics pipeline and not related to input.
I’ll take a closer look at Reach later. A similar issue occurs with most recent Call of Duty games, which also behave rather special, so it would be useful to finally get to the bottom of this anyway.