Forum Replies Created
-
Posts
-
Sounds like some annyoing antivirus program issue.
Try to exclude the vorpX program folder from your AV program, typically that’s C:\Program Files (x86)\Animation Labs\vorpX
BTW: If you happen to use any other AV program than Windows Defender, the best you can do is getting rid of it as fast you can. There is no need for (usually more invasive) third party AV on Windows 10. Windows Defender is more than good enough since several years now. It kicks in automatically when you remove redundant third party AV.
The memory scanner is part of the HL2 since several years, it’s a game though where vorpX can cache the found values, so probably the cache is just out of date. The game is still updated surprisingly often and for each version the DirectVR values are different.
Long story short: After a HL2 update you typically have to re-run the memory scanner. Whenever that’s the case, vorpX will show an according message in the headset as well as in the top left corner of the game window.
Some GamePass games are compiled as Universal Windows Platform apps instead of ‘classic’ Win32 programs. UWP apps run in a secure sandbox and are protected against hooking into them. Haven’t checked whether that’s the case for RE7 on GamePass yet, but this might be the issue here.
Another potential issue is that the GamePass version might use a different .exe name. vorpX expects it to be named re7.exe. Would be great if you could check whether that’s the case, and let me know if the name is different.
Apart from the above there always also is the chance of a conflict with some other program on your PC, of course. In that regard please check the pinned trouble shooting post on top of this sub forum.
Try to reset the vorpX profile to default in the config app. You shouldn’t have to bind any controls on the X-Box gamepad for Ori, it should work perfectly fine with the gamepad in native mode.
That’s half good at least, means vorpX can successfully hook the games and “just” fails to show them in the headset.
There currently is a bug where vorpX may lose the connection to the headset if a game gets minimized (e.g. via ALT+TAB). Try to run the games in question windowed, maybe your issue is related to that bug. Running games windowed usually prevents the bug from occuring. Will be fixed in the vorpX version, of course.
It’s either hooking or the desktop viewer.
Shouldn’t be a big deal to get pretty much any game running in 2D as long as its DX9-12 or OpenGL though. For older DirectX games a DX11 wrapper like dgVoodoo will do the trick. If vorpX doesn’t hook without a profile, simply create a custom profile for the game in question based on a game that uses the same DirectX version and disable 3D in the vorpX menu.
A short introduction to creating custom profiles can be found in the vorpX help. If you really just want to play 2D, that’s extremely easy.
You can reset each profile individually, either on the ‘Local Profiles’ or the ‘Trouble Shooting’ page of the config app.
The resolution you run a game with has a pretty huge impact on the performance. Going from 1920×1080 to 3840×2160 means that four times as many pixels have to be drawn as before.
There should be no performance difference at all though when you change back the resolution to 1920×1080. If that’s really the case, something else has also changed. Can’t really suggest much more than resetting both the vorpX profile (in the config app) and the game’s graphics settings to default.
Also try running the game windowed, just in case it does some internal upscaling to the native native monitor resolution when you set 1920×1080 fullscreen.
With the same game resolution and graphics settings performance is the same regardless of your monitor’s native resolution.
1. Not sure about this one, that shouldn’t happen normally. The only thing I can imagine is that the driver/tool you use to translate your PS4 controller input to Windows native controller input may have something to do with it.
2. You can switch to EdgePeek mode to deal with the matter (mousewheel click or right thumbstick click per default). The issue itself is a side effect of the scalable HUD vorpX provides for the game. Usually it’s possible to cleanly separate game from HUD/menu shaders, but in this case it wasn’t, thus parts of the menu stay unscaled. Switching to EdgePeek while using the menu helps here.
3. Another side effect of a vorpX feature, in this case headtracking. In RDR 2 head tracking is done by emulating a mouse, hence the game constantly switches back and forth between the mouse/kb and the gamepad overlay. The only way to get rid of this glitch would be to disable head tracking in the vorpX menu. Not the entirely only way actually: alternatively you could configure vorpX to emulate a gamepad with head tracking instead of a mouse. That’s fairly laggy though and thus should be avoided unless necessary.
I’m obviously biased, but still hugely puzzled about comparisons with a depth shader that does maybe 10% of what vorpX does, if at all. For one for DX9-11 (and older OpenGL) games vorpX provides “true” Geometry 3D instead of doing post process depth based 3D, which in itself is something entirely different, including the general option to have positonal tracking in every G3D game (provided that doesn’t cause too many glitches).
Even more puzzling is leaving out the whole DirectVR complex. By now there are more than 150 games for which vorpX adjusts everything automatically for a decent FullVR experience largely out of the box. Usually at least covering FOV and resolution, plus setting up the head tracking sensitivity. These games are typically plug & play except for graphics options/performance adjustments. In more than 50 games there is even more than that in the form always perfect 1:1, low latency head tracking via directly accessing a game’s memory locations for camera rotation (and sometimes position).
Not to mention the recently introduced TrackIR handling for games with TrackIR support, scalable HUDs with 3D depth, VR controller support, a gaze based visual hotkey menu and quite a bit more…
In Bioshock Infinite per default the FOV is handled via an .ini edit, not with the memory scanner. Please reset the profile to default in the config app and afterwards make sure to follow the hint shown in the top left corner of the game window regarding setting the FOV slider in the game’s options to max. Without that the .ini edit DirectVR does has no effect.
Halo 4 doesn’t have an official vorpX profile. If there happens to be a user profile with supposed memory scanner functionality it’s unlikely to fully work, if at all. The scanner configuration is fairly game specific. Also scanner profiles don’t always include FOV. You can see what the scanner does and what it doesn’t in a game on the DirectVR page of the vorpX menu.
The G3D FOV Enhancement option can be found under “More 3D Settings” on the main page of the vorpX menu. Be aware though that in most newer games it causes too many visual glitches to be of much use.
BTW: A general way how to handle FullVR for games without automatic FOV adjustment is explained in the “1-2-3 Game Setup” guide in the vorpX help. The method described there isn’t always 100% perfect, but it always works. Additional information regarding FOV can be found in the “Essential Hints” guide in the help.
No such problems here. Please make sure that to run the DirectVR scanner if necessary, there should be a message about that if the cached values are out of date. Also make sure to follow the hint in the top left corner of the game window regarding setting a 4:3 resolution, which is shown if currently no 4:3 res is set.
Sounds as if something is *really* wrong. Hard to tell what, but neither should you have to disable the overlay detection nor does vorpX require admin rights for the game under normal circumstances. That’s only necessary for (mostly older) games that require admin rights themselves. vorpX will complain whenever it can’t hook due to insufficient access rights.
My usual reflex in such odd cases is suspecting some interfering background program. The trouble shooting guide on top of this sub forum has more details on the matter. Most importantly: switch to Windows Defender if you happen to use some (usually more invasive) third party antivirus program. Also check for anything else that might get in the way. Something causing havoc by also hooking into games is the most likely issue here. Last, but not least: if you have mods installed, check whether the issue also occurs without.
What Ogrescar says.
You have to install the Oculus PC software and then connect your Quest with an USB cable to the PC. Once you have everything set up, you can start Oculus Link in your Quest at which point the Quest looks like a PC Headset for vorpX.
Do you have the Oculus PC software installed already? if not, you can getobt here: http://www.oculus.com/setup