Forum Replies Created
-
Posts
-
Keys stay valid until you change vital hardware or reinstall Windows. You can avoid having to wait for a new key when you just reinstall vorpX by keeping the key e-mail.
You have to make sure that WMR is your default OpenXR runtime. The WMR portal should display an according warning message if that is not the case.
If your ensured WMR is your OpenXR runtime and the issue still occurs, something is wrong. Difficult to tell what, but in that case simply stick to SteamVR as a workaround.
Pretty much what Jey123456 says with one exception: in games with DirectVR memory scanner support vorpX temporarily may require significantly more system RAM during a scanner run. How much depends on how much of a game’s RAM has to be scanned.
Unless you have an awful lot of stuff running in the background that consumes huge amounts of RAM, 16GB will still suffice under all circumstances.
For technical reasons cloud accounts and your forum account are not the same.
You have to create an extra account for the cloud profiles in the vorpX config app.
Windows Defender will work just fine. If you can’t make it work, please create a trouble shoot data archive in the config app (‘Trouble Shooting’ page) and send that to support at vorpx com. Can’t say anything more useful without more specific information.
It‘s always a bit difficult to reply in a meaningful way to ‚I didn‘t change anything, things just stopped working.‘-posts. So please excuse that I only have a more general answer: If you haven’t done so already, please try to reset both the game options and the vorpX profile to default. That should get you back to a state from before the issue started to occur.
In case of issues in regard to using menus, also switching to EdgePeek mode (mousewheel click) sometimes help. If a profile comes with a scalable HUD that may occasionally cause issues with mouse coordinates, specifically whenever the mouse cursor can‘t also be scaled for one or the other reason. This particulur issue can be resolved by using menus in EdgePeek mode.
As far as I’m aware Arma 3 also is moddable, so if you happen to have installed any mods recently, please also try whether the issue occurs without mods.
Unless I misunderstand that either, 2. was answered above, I think. You disable the override by switching the ‚X-Box Gamepad Override’ setting off. Like said above vorpX either overrides gamepads or not. The only thing that affects this behavior is turning the override on/off in the menu.
As far as the origin of your original issue is concerned, I can’t really say much unfortunately. If “suddenly” something changed without you changing this setting, there must have been something unrelated to vorpX that changed. E.g. gamepad input being disabled in the game options.
The only thing I can really recommend is resetting both the game options to default as well as the vorpX profile (respectively deleting and re-downloading it in this case, since it’s not an official one).
I’m sorry. But either I don’t really understand your original question or you don’t understand my replies. Honestly not sure which of the two it is. :)
vorpX doesn’t change any game files or anything when you enable the override. So getting back to how you had thing before enabling it, is easy: you just disable the override.
However, there are only two options as far as mouse based head tracking and gamepads are concerned:
1. A game works fine with both gamepad and mouse input at the same time: if that is the case, you can leave the X-Box Gamepad Overide disabled since mouse based head tracking doesn’t cause a conflict.
2. A game can’t handle simultaneous mouse and gamepad input: in that case mouse based head tracking will cause a conflict and you need the X-Box Gamepad Overide to use a gamepad together with head tracking.
There is no way to get native gamepad input and mouse based head tracking when a game can’t handle simultaneous mouse and gamepad input. The whole point of the gamepad override is dealing with such a conflict.
Natively gamepad input usually handles walk/run in an analog way, i.e. there is no hard switch between walking and running, instead you become gradually faster when moving the stick forward. With the override walk/run (obviously) works like keyboard walk/run with two distinct velocities.
Not necessarily a bad thing in VR btw, at least if you are sensitive to VR sickness. Gradual velocity changes (acceleration) can be fairly sickness inducing when your body isn’t actually accelerating since your brain receives mismatching input from your eyes and your vestibular system.
No idea sorry. If Star Citizen still works with vorpX after their next update, which will supposedly add an anticheat system, and thus might lock out vorpX, I’ll check whether I can somehow replicate your problem.
You aren’t the only one with weekends. ;) Thanks for your patience.
Sounds as if you might be running the game windowed with a resolution larger than your monitor res. In such a case the mouse can’t reach the bottom of the window.
To resolve that you have the following options:
- Run the game fullscreen
- Switch your desktop to a higer res so that the window is fully visible
- Use a gamepad instead of your mouse.
In regard to options 1. and 2. please also check the ‘Custom Resolutions’ section in the vorpX help.
If I understand the post correctly, switching the ‘X-Box Gamepad Override’ option to ‘Off’ is what you have in mind. May require a game restart, depending on how and when the game evaluates connected gamepads.
CAVEAT: Some games don’t support mouse and gamepad input at the same time. In such games the gamepad > mouse/kb mapper is the only way to have both mouse based head tracking and gamepad input. That’s why the mapper exists in the first place.
Can’t help with this here on the forum, but please check your e-mail. I responded to your support mail.
A DirectVR scan (if available) can only affect performance if FOV is handled via the memory scanner. Since matching the game FOV to your headset‘s FOV typically means raising it, performance may actually be lower though. With a higher FOV more has to be rendered.
You still definitely want to use the DirectVR scanner whenever it is available. For one matching game and headset FOVs are a necessity for FullVR mode, and while the memory scanner may either have no effect on your framerate or even decrease it (if it raises the FOV), it also provides low latency 1:1 head tracking by directly overwriting a game‘s camera position in memory. And that is something you definitely want whenever you can. Depending on the game the difference in head tracking quality compared to mouse emulation can be huge.
TLDR: Not using the DirectVR scanner whenever possible is sheer madness. ;)