Forum Replies Created
-
Posts
-
Since there hasn’t been an update to vorpX recently, nothing happend on the vorpX end. Something must have happened on your end. Unfortunately it is not possible to tell from here what might have happended on your PC from your issue description.
Here’s what you should check:
To get the obvious stuff out of the way: Make sure that: A. ‘Oculus’ is selected in the vorpX config app as your headset type, B. You have the Oculus/Meta Link app installed and it is working correctly.
If that does not help and you happen to have the Windows system restore feature enabled, go back to a restore point from before the issue started to occur.
In your shoes my first impulse probably would also be blaming vorpX since on the surface that’s what doesn’t work for you, but in a case like this chances are very high that you simply have some unresolved hooking conflict with some tool that also hooks into games.
If not even fully featured DirectVR profiles like this one – G3D, 6DOF tracking, fully automated FOV setup, pre-configured motion controller mapping, heck, in this game vorpX even takes care of moving weapons out of sight unless you shoot – don’t work for you, something weird is going on with your setup.
The best way to trouble shoot potential hooking conflicts is exiting each and every background tool you may have running on your machine, no matter how unlikely you consider them to cause such a conflict. More details regarding potental hooking conflicts can be found in the trouble shooting section of the vorpX help.
I just checked with 23.1.5. Works perfectly fine here as far as I can tell. 24.1.0 is probably broken.
Do a factory reset (config app/trouble shooting) in the config app after going back to 21.3.5. Back in the game make sure to run the DirectVR scanner for 1:1 head tracking and FOV (check the hints vorpX displays in the top/left corner of the game window) and – VERY IMPORTANT – do not tweak anything manually except the game resolution. In highly automated DirectVR profiles like this one chances are very high that you do more harm than good with manual tweaks.
Games often render weapons at a different FOV than the rest of the world to make them look good on the monitor. That, besides moving the weapon out of sight unless you shoot, gets resolved by the auto weapon handling…
If the fully automated setup (usually manual tweaking causes more harm than good in highly automated profiles like this one) doesn’t work with either 23.1.5 or 24.1.0, wait until the next vorpX release. Maybe something changed recently.
I‘m sure it‘ll work in the next vorpX release though, I incidentally just tweaked the weapon handling stuff two or three weeks ago.
If you happen to be on 24.1.0 please go back to the last regular vorpX build or vice versa.
Also for cinema/immersive screen mode you may have to disable automatic weapon handling on the DirectVR page of the menu. This feature currently garbles the image at camera FOVs lower than what vorpX sets in FullVR mode. Will be addressed in the next update.
If you experience issues like that regularly with multiple games that are usually known to work well like e.g. Titanfall 2 and Mirror’s Edge, there almost certainly is something getting in the way that also hooks into games. (Double and triple) check what tools/utilities you may have running in the background. If in doubt, exit it. No matter how unlikely you consider it to potentially cause such an issue.
Also make sure to try installing hook helpers when the ‘Attaching To …’ dialog shows that option after a minute or so. Installing a hook helper to the game folder can often resolve hooking conflicts without having to find the offending app/tool.
Also be aware that some GamePass games may be compiled as UWP (Universal Windows Platform) apps, which run in a sandbox and can’t be hooked. Extremely unlikely though that Titanfall 2 and Mirror’s Edge have been recompiled as UWP apps for GamePass.
The current version of the mod works fine with 2.13 normally. Occasionally game updates break the mod, hence the warning. Currently however the warning really just is a warning and everything works as expected under normal circumstances.
The most likely cause for your problem is some other mod getting in the way or some background program you may have running that also hooks into games, e.g. a GPU/CPU tool, a messenger, a game recording app or whetever else may display overlays in games and thus may cause a conflict.
This cannot be resolved on the forum. Please use the support contact form re the e-mail change. For obvious reasons the license server does not send keys to unknown mail addresses.
There are two different types of cloud profiles: 1. full user profiles for games without an official profile, 2. user settings for official profiles. Only the first type shows up as an extra entry in the local list, the second type loads the user configurable settings for already existing profiles, which would be the case for Elder Scrolls Online. The type of the profile gets displayed in the cloud list.
Haven’t tried in a while, but I think you need the last regular vorpX 21.3.5, not the 24.1.0 beta. the 21.3.5 build has been whitelisted in SC’s anticheat. Also make sure TrackIR is enabled in the game options. Not 100% sure, but if I remember correctly, SC is one of the games where you have to enable TrackIR manually.
Slightly less than 180° would work out mathemetically in theory with games that allow to set the FOV to the maximum possible with the perspective projection games use. BUT: due the extreme distortion that would require insanely high resolutions to reproject the recorded footage to (semi-)spherical 180° video that doesn’t look like being recorded at 320×240 resolution.
Still an interesting idea. Might be worth a shot to create a couple of videos that way as promo material with games where this would actually work in principle without slowing down to a crawl due to the high resolution and FOV.
What’s more feasible in general would be taking a series of pictures and stitching them together to a single 180/360 panorama. A stereoscopic panorama photo mode, so to speak.
Considering the number of users that would actually benefit from this and the fairly limited number of games where it *might* actually work makes even the effort required to take a closer look unfeasible unfortunately.
At least unless you want to pay for it in full at an hourly rate suitable for a highly specialized C++ developer living in a western high tax country. Which you don’t want to, trust me. Even if initial research proved it to be feasible for a limited number of games, a feature like that would take at least a month until properly implemented.
If you want to circumvent anticheat measures in online games, you’re on your own. This forum is not the right place to discuss such topics. Thanks for your understanding.
Only DX7/8 games work as far as I’m aware or maybe DX6-8, DX1-5(or 6) only does the final rasterization via Direct3D, not any actual 3D calculations. Handling such cases would require an entirely new pipeline in vorpX instead of doing 3D like vorpX does 3D normally. Might happen if I‘m bored at some point, but don‘t hold your breath.
To further complicate matters, something has changed recently in dgVoodoo, so vorpX can‘t find projection matrices of recent dgVoodoo versions at all. So even the games that normally work, currently don‘t with recent dgVoodoo builds. Has been taken care of for the next vorpX, but for the time being you have to use older dgVoodoo builds (2.5 or 2.6, can‘t recall exactly).