Forum Replies Created
-
Posts
-
Yesterday’s profile database update ‘only’ contained updates for some shader definitions that got broken by game updates, nothing related to your issue. If you encounter something like that again, keep the three options mentioned above in mind.
Almost certainly this:
Many games cannot handle simultaneous mouse and gamepad input.
If you use your gamepad natively, i.e. vorpX’s ‘Gamepad Override’ setting is set to ‘Off’, but you still use mouse emulation head tracking, you get symptoms like the ones you see in games that can’t properly handle mouse and gamepad input at the same time.
To deal with that you have three options:
- Enable the ‘Gampad Override’ setting, which enables a freely configurable gamepad to mouse/kb mapper.
- Disable the ‘Gampad Override’ setting and then enable ‘Headtracking as Gamepad’. Caveat: Not really recommended in most cases due to high head tracking latency (lag) caused by games filtering gamepad input.
- Disable the ‘Gampad Override’ setting and set ‘Head Tracking Sensitivity’ to 0, which resolves the conflict by disabling head tracking.
You have not been charged as long as the transaction shows as pending in your account. Safe to say after almost a week that the transaction failed for some reason.
I can’t tell you anything more specific than that, sorry. All we get are notifications from our e-commerce service Lemon Squeezy when an order finishes, which in your case did not happen since the transaction failed without you getting actually charged.
If you want me to forward the issue to Lemon Squeezy, please send an e-mail with a screenshot of the transaction in your account to support at vorpx dot com. That only really makes sense though if you actually get charged, i.e. the transaction changes from pending to finished.
After four days I assume the transaction failed for some reason. Common payment options like PayPal or credit card are instant unless something goes wrong. More than four days would be highly unusual even for more exotic payment options that might require manual booking on Lemon Squeezy’s end.
To be on the extra safe side it might still make sense to wait a few more days before trying again. Just in case.
… im not using virtual moniter since many games dont let me pick display 2 …
For that reason with default settings vorpX can disable your actual display when the virtual display is used. The easiest way to trigger that is launching the vorpX desktop viewer and then simply putting on your headset.
Make sure ‘Enable Virtual Monitor’ and ‘Activate when you put on your headset’ are both checked on the Virtual Monitor page of the config app. That would be the default settings.
VERY! important thing to understand first: in many games you will lose vorpX’s mouse emulation head tracking when you disable the gamepad override. The override primarily exists because many games cannot handle simultaneous mouse and gamepad input. By translating gamepad input to mouse input the override enables the use of a gamepad together with mouse emulation head tracking in such games. The alternatives would be no gamepad at all or emulating a gamepad with head tracking, which vorpX can also do. That’s not really recommended though since fairly laggy due to how games handle/filter gamepad input.
That said:
While in Dishonored you can use your gamepad natively after running the memory scan, which lets vorpX manipulate the game’s camera directly without having to emulate mouse input, in the Long Dark probably vorpX converts your gamepad input to mouse/kb input due to the simultaneous mouse/gamepad input issue described above. Per default that means pressing W when you push the stick slightly forward, and in addition to that SHIFT for running when you push it entirely forward. That’s probably why you are running faster than without vorpX. Nothing wrong here, everything working as expected.
You can freely configure the emulation/mapping to your liking in the vorpX menu.
If you don’t need head tracking or want to check whether mouse emulation headtracking still works fine with native gamepad handling, you may have to disable both the gamepad override option and VR controller support in the vorpX menu. VR controllers emulating mouse/kb may also prevent your gamepad from acting natively for the reasons described above.
Please first check whether you actually have been charged in your PayPal/credit card account, i.e. whether there is a charge at all and if so whether it isn’t maybe still marked as pending, which would mean the order wasn’t fullfiled.
If you are 100% sure that you actually have been charged without getting anything from our e-commerce service Lemon Squeezy (quite unlikely), please send an e-mail with a screenshot of the transaction/charge to support at vorpx dot com.
Please check this:
Thanks!
Safe to say that vorpX has grown into something truly unique over the years. Probably hard to fathom the sheer scope and complexity without some basic understanding of 3D/VR programming. That’s the nature of the beast, I guess. Makes it even nicer to get feedback like yours every now and then. :)
Unfortunately there is no single answer to that question since games use different metrics for their FOV calculations. Some use the vertical FOV (which makes most sense), some the horizontal FOV, some use a wrong but fairly common naive vertical to horizontal calculation, some use offsets from some unknown base value or even made up fantasy values. Over the years the number of formulas in profiles where vorpX can calculate the FOV automatically has reached about a dozen…
That said:
For vorpX at default, i.e. with its ImageZoom setting at 1.0, the actual vertical! FOV you want in a game is always 96°, no matter what headset you use. That’s done to keep profiles and potential instructions from profile authors easily interchangeable.
Most modern headsets however can display a bit more if you want. The actual vertical FOV your headset needs with vorpX’s ImageZoom setting maxed out can be found in the vorpX log file in a line like ‘SteamVRDevice: FOV: 103.000000°’ or so. Might also be ‘OculusRiftDevice’ or ‘OpenXRDevice’ depending on your headset type.
That’s only the first step though. From there you need to figure out how the game in question actually handles its FOV calculation, which, as described above, differs heavily from game to game.
You can check the vorpX log file by creating a trouble shoot archive in the config app.
—
BTW: The values from comparison sites on the internet are uselesss for your purpose as they are usually derived by looking through the lenses on some measurement table displayed on the screen. So that’s the FOV the person who looked through the lenses was able to see, which varies depending on various individual factors ranging from face shape to eyesight. It’s not the FOV a game would display on the screen, which usually is higher than these visually guessed values.
There should be no need to tinker with anything FOV related. FOV, including weapon FOV is handled perfectly by DirectVR. Just run the menory scan.
Check my reply in a related thread in the Technical Support sub-forum: click
You may have to raise the ‘Headtracking Sensitivity’ value in the menu. If it still doesn’t work afterwards, on your machine something is wrong that isn’t covered by the fix for the issue. Potentially some weird Windows access rights issue that might e.g. be caused by running Windows with separate admin/day-to-day accounts.
This is a false positive.
vorpX “injects” other programs which some AV programs may classify as malicious behaviour without really being sure about it, and – most annoyingly – without telling their users that they are just taking a guess.
You should report this as a false positive to your AV vendor so they can fix their mistake.
In the meantime please exclude the vorpX program folder from scanning.
Alternatively you might want to consider switching to Windows Defender, which provides excellent protection without being as invasive as some other AV scanners. Windows Defender gets enabled automatically on Windows 10/11 when you uninstall redundant third party AV programs.
I usually make sure Microsoft whitelists new vorpX releases before uploading them, so with Windows Defender you should rarely – if ever – encounter annoying issues like this.