Search Results for 'keys'

[rbturcott]

Hi,

Using PC with Valve Index, no VR controllers or Xbox type controller. So trying to use keyboard and mouse.
On starting Fallout NV, things seem to start and hook in. Steam VR starts and the game boots to the start menu but is displayed in a window to the left. In the centre is a panel with a couple of hints and to the right is some more help in another panel.
Only Vorpx functions appear to respond to any keystrokes or mouse in the headset.
Mouse disappears outside of any Vorpex function or panel.
There is no way to do anything outside of Vorpx fuctions at this point. Game is displayed on my regular monitors, partially across two monitors. Alt-Tab works, sort of, to get out of VR, but mouse is gone, keyboard sort of works outside of VR. I have to log out or reboot to get mouse functionality back.

Plugged in an Xbox controller to see if that would make a difference, but no luck.

Note, I do not know if this is specific to the game, as this is the only game I’m using it for. It used to work years ago and I’m only just revistiing this game after quite some time.

Any help would be appreciated.

Thanks.

[chtiblue]

Ok I figured some things :)
I don’t know why but this time all the resolutions appeared in game video settings.
To free my view with the headset I had to crankd up headset sensitivity to 4.0 way more than usual.

Only problem I still have is with Vorpx my Xbox controller isn’t properly working in game when it works perfect without Vorpx. With Vorpx interaction keys always switch to keyboard keys so it’s a pita to use inventory, open doors etc…
If I override Xbox controller in Vorpx, it changes keys or doesn’t respond at all

[Ralf]

26/01/13 | vorpX 25.1.5 has been released

Another maintenance update. Addresses a couple of input glitches, comes with a rewritten host-exit that better handles exit crashes with Meta’s OpenXR since a recent Meta Link update, makes alternative hooking usable for more games, fixes a rare DX9 issue, has a bunch of profile fixes/updates and more.

Click here for a list of noteworthy changes

• vorpX: keys wrongly blocked in some DirectInput games (e.g. Fallout 3/NV).
• vorpX: the tracking center hotkey also ensures foreground and input focus.
• vorpX: ALT+TAB and back could occasionally confuse key state tracking.
• vorpX: fixed cursor clipping in some older games (e.g. Metro 2033).
• vorpX: headset audio device switching did not work anymore.
• vorpX: D3D9: better unhooked surfaces handling, e.g. Venetica ALT+TAB crash.
• vorpX: improved host exit, cleaner in various games and with Meta OpenXR.
• vorpControl: folder exclude handles symlinks (e.g. latest EA Desktop).
• vorpControl: minimize runtime windows option supports latest Quest Link.
• vorpControl: alternative hooking working for more games.
• Cyberpunk 2077: improved sync between mod-portion and vorpX.
• Tron 2.0: .ini changes weren’t applied anymore since a while.
• Dishonored 2: scalable HUD added.
• Dragon Age Origins: deal with GOG version 2-core lock.
• Dragon Age II: deal with GOG version 2-core lock.
• Farming Simulator 25: Fixed a Z3D issue related to vehicle mirror count.

[pokkla]

Update #2 (for anyone finding this):
I tried other versions and v24.1.0 also does not disable the ESC and E keys. It works per normal… it works great.

[pokkla]

Update: For what it’s worth, I was able to downgrade vorpX from v25.1.4 to v21.3.5. With that, the “ESC” and “E” keys worked fine. It took a bit of thinking to block the update calls so v21.3.5 wouldn’t get overwritten, but it does work. I’m working on a version swapping program so I can keep v25.1.4 from my other games.

If anyone has ideas on why E and ESC don’t work in v25, let me know.

[pokkla]

I recently got back to playing Fallout New Vegas (last played Feb ’24). However, it appears that vorpX now disables the “E” and the “ESC” keys. No other keys seem to be affected. I can run the game without vorpX and all the keys work fine. I can also run other games with vorpX, like Skyrim SE and Fallout 4, and all the keys work fine. I use MO2, so I tried FONV native (no MO2 and no mods) and I got the same results as running with MO2. That is, the keys work fine without vorpX. But, those two keys are disable with vorpX running. I have done all the noob fixes too, like rebooting the computer, etc.

In FONV, I can remap the action key “E” to something else (like “P”) and the action key works as planned. However, I can’t remap the ESC (menu) key and it is critical to game play. vorpX works fine itself displaying great VR once up and running. It’s just that I can’t use the E or ESC keys.

I have had vorpX for many, many years and used it with many, many games, and this issue is a head scratcher. Is there a different hook/method I should try? Any suggestions would be appreciated.

[Ralf]

As far as the start room is concerned, check the hint badges around the center screen. They tell you which buttons/keys you can press.

[Ralf]

If you happen to be on vorpX 25.1.0, make sure to update to 25.1.2 by running your web installer. 25.1.0 did not work with outdated OpenXR runtime implementations like VD’s OpenXR. Unfortunately auto updates from 25.1.0 to 25.1.2 are broken, so you have to run your web installer manually. If you didn’t keep the installer, check the support FAQ for a new link.

As far as the start room is concerned, check the hint badges around the center screen. They tell you which buttons/keys you can press.

[Ralf]

Interesting, never heard of that. vorpX does use GetAsyncKeyState(), but not in the hooked game. It updates the keyboard state in the vorpControl app and then relays that to the game via interprocess communication. It does hook the function though inside the game for various reasons. I’ll check TR3 in Windows 10. If I find something unusual, I’ll let you know.

BTW: vorpX quite heavily relies on interprocess communication like the one described above between all its parts, which makes mixing components from different versions dangerous and likely to cause havoc. Don’t do that.

Just in case you may also try a uninstall/reboot/reinstall like I suggested to Dellrifter above. Just to be 100% sure everything is really at 25.1.1.

[ENBSeries]

@Ralf
Regarding issues with non functional input. If I keep old version of vorpControl64.dat, then issues do not happen. Maybe there is another combination of files, didn’t test more.
The same problem happens in A Hat in Time. Reinstalling Vorpx via web setup multiple times – no difference. Even Vorpx own ctrl+alt+shift popup message ignores keyboard in A Hat in Time game. The only thing suspicious to me is when first time after long break started Vorpx and it initiated an update, at some stage of installation terminated it manually because was busy with other pc tasks. Still, that don’t explain why problem remains after executing web setup later, after reboot as well. As mentioned earlier, in the SpaceEngine some actions do work in certain moments, like game first popup warning with Esc button to hide it fails, then main menu works for cursor and mouse buttons both, then in-game cursor works but mouse buttons and keyboard are dead. I know some of the last patch(es) of Win11 (I’m on Win10) have changes to GetAsyncKeyState, breaking some apps, maybe workaround was done on Vorpx and it do not works in my case.

[Ralf]

26/01/13 | vorpX 25.1.5 has been released

Another maintenance update. Addresses a couple of input glitches, comes with a rewritten host-exit that better handles exit crashes with Meta’s OpenXR since a recent Meta Link update, makes alternative hooking usable for more games, fixes a rare DX9 issue, has a bunch of profile fixes/updates and more.

Click here for a list of noteworthy changes

• vorpX: keys wrongly blocked in some DirectInput games (e.g. Fallout 3/NV).
• vorpX: the tracking center hotkey also ensures foreground and input focus.
• vorpX: ALT+TAB and back could occasionally confuse key state tracking.
• vorpX: fixed cursor clipping in some older games (e.g. Metro 2033).
• vorpX: headset audio device switching did not work anymore.
• vorpX: D3D9: better unhooked surfaces handling, e.g. Venetica ALT+TAB crash.
• vorpX: improved host exit, cleaner in various games and with Meta OpenXR.
• vorpControl: folder exclude handles symlinks (e.g. latest EA Desktop).
• vorpControl: minimize runtime windows option supports latest Quest Link.
• vorpControl: alternative hooking working for more games.
• Cyberpunk 2077: improved sync between mod-portion and vorpX.
• Tron 2.0: .ini changes weren’t applied anymore since a while.
• Dishonored 2: scalable HUD added.
• Dragon Age Origins: deal with GOG version 2-core lock.
• Dragon Age II: deal with GOG version 2-core lock.
• Farming Simulator 25: Fixed a Z3D issue related to vehicle mirror count.

---

25/12/20 | vorpX 25.1.4 has been released

This maintenance update mainly focuses on an annoyance affecting mouse/keyboard players in some games that upscale the image to the monitor size. Under certain circumstances that can lead to vorpX’s stereo cursor being shown at a wrong position, making it difficult to hit buttons in menus etc. Various reasons for this super annoying glitch are now covered. The remaining will follow later.

Apart from that there have been a few more fixes and a new profile for Farming Simulator 2025 with automatic FOV and a scalable HUD.

Click here for a list of noteworthy changes

• vorpX: Improved stereo cursor rendering in games that upscale their output.
• vorpX: Z3D could break in some games after taking off the headset.
• vorpX: some games could crash with Windows display scaling set to 150/175.
• vorpX: some games could crash on audio device change (25.1.3 regression)
• Farming Simulator 2025: new profile with HUD scaling and DirectVR FOV.
• Farming Simulator 2022: DirectVR FOV update.
• Fallout 4: DirectVR FOV scan was broken after a game update.

---

25/12/16 | vorpX 25.1.3 has been released

Another maintenance update, mainly addressing various issues and annoyances that came up since 25.1.2. Aside from the fixes there is a subtle improvement in regard to how the game/desktop images are sampled before sending them to the headset. Power users can also configure the sampling method now with expert settings enabled.

Click here for a list of noteworthy changes

• vorpX: Battlefield 2 could crash on map load.
• vorpX: some games could crash on CPUs with more than 12 cores.
• vorpX: different image sampling methods for screen/FullVR modes.
• vorpX: image sampling method user selectable (expert setting).
• vorpX: option to improve FPS in games that limit core count (e.g. Witcher 1 GOG).
• vorpX: back to OpenXR 1.0 due to outdated runtimes (eg. Valve, Virtual Desktop).
• vorpX: relaunching games with another graphics API could fail.
• vorpX: DX9: (rare) 64-bit DX9 games ran at roughly half the supposed FPS on Win11.
• vorpX: DX9: some FPS lost since quite a while have been reclaimed (eg. Skyrim).
• vorpX: DX11: Z3D did not work anymore in several games (e.g. COD Black Ops III).
• vorpX: DX12: fixed an (currently unused) Z3D method that didn’t work at all.
• vorpControl: hook helper install auto API detection didn’t work anymore.
• vorpControl: creating desktop shortcuts did not always work anymore.
• vorpService: fallback for virtual display/desktop viewer not working on some PCs.
• vorpService: The virtual display didn’t always get disabled on standby as intended.
• vorpService: Quest Link detection not working anymore after a recent Link update.
• Just Cause 3: depth buffer detection could fail occasionally.
• The Witcher 3: DirectVR: camera position was broken, second position added.
• The Witcher 3: DirectVR: auto EdgePeek for menus, cutscenes etc. didn’t work.
• Elder Scrolls Online: shader parser to detect future UI changes automatically.
• F1 2019: restarting with DX11 didn’t work anymore.
• F1 2020: restarting with DX11 didn’t work anymore.

---

25/09/12 | vorpX 25.1.2 has been released

Another maintenance update with about a dozen noteworthy changes and fixes.

Click here for all changes

• Head tracking mouse emulation did not work anymore in desktop viewer.
• Messages shown in some games on start could become unresponsive.
• Mod component install with the virtual display failed due to an unclickable prompt.
• Some games did not exit cleanly since vorpX 25.1.0.
• Workaround for 32-bit games that use too much RAM on CPUs with many cores.
• Potential workaround for old games that assign small stack sizes (untested).
• In games with .ini and mem-scan FOV, ini-controls weren’t shown before scanning.
• Avoid more annoying virtual monitor related Quest Link self-restarts.
• Communication between the service and 32-bit vorpControl was broken.
• The service could use an entire CPU core after lock/unlock, standby/resume etc.
• Custom sync selection in the vorpX menu selected different options than shown.
• Trouble shoot data now includes all relevant log files.
• Better service handling in the installer.
• Elder Scrolls Online: HUD shaders updated (again).
• Cyberpunk 2077: mod components updated for CP2077 2.31
• As always numerous smaller fixes and optimizations.

---

25/08/30 | vorpX 25.1.1 has been released

This maintenance update brings some OpenXR improvements, carves out more precious GPU memory, enhances Quest controller support with SteamVR and fixes a bug where Z3D became heavily pixelated after switching 3D modes.

Auto-updating from 24.1.0 and 25.1.0 will likely fail (sorry!), you may have to reinstall manually with your web installer. If you didn’t keep it, you can get one here: click

Click here for all changes

• GPU memory usage reduction due to headset sync optimizations, ~150 MB at 4K.
• Auto judder protection when a VR runtime throttles the headset framerate.
• Rendering the start room could produce glitches/DX errors.
• DX11/DX12 Z3D could become heavily pixelated/after switching 3D modes.
• SteamVR: emulated start/back gamepad buttons on Quest controllers now working.
• OpenXR: deal with outdated OpenXR runtimes (e.g. Valve, WMR)
• OpenXR: VR controllers were rendered upside down since an OpenXR lib update.
• OpenXR: resetting the renderer in case of an error could cause a crash.
• OpenXR: head rotation felt wobbly in immersive screen/cinema mode.
• OpenXR: don’t use Valve’s broken OpenXR, use SteamVR if set as OpenXR runtime.
• OpenXR: auto switch to Quest Link or SteamVR if no active OpenXR runtime is set.

---

25/08/28 | vorpX 25.1.0 has been released

This update reunites the regular and the ‘cutting edge’ branches. For those who until now used the regular version it brings three major new features: motion controller gestures, a rewritten desktop viewer and a virtual monitor.

Those who already used the cutting edge build can skip to the full changelog at the bottom of this post to check what has changed since then.

Motion Controller Gestures

You can now map predefined motion controller gestures to key presses and gamepad actions. Aminig down sights, reloading, melee combat, steering wheels and a lot more gestures are available to turn flat games into more immersive VR experiences. While not every game benefits from gestures in the same manner, some (e.g. first person shooter games) can actually feel close to native VR that way. Even seated just a handful of gestures can tremendously improve immersion compared to playing with a gamepad or mouse/keyboard.

Various profiles already have gestures predefined, try e.g. Cyberpunk 2077, Starfield, Titanfall 2 or Aliens Colonial Marines. More will follow. For other games you can easily define gestures yourself. Be amazed how easy that is and how well it can work. Check the video below for a brief introduction.

Desktop Viewer Rewrite

The rewritten desktop viewer now handles high GPU load a lot more stable and also addresses a bunch of annoyances the old desktop viewer had, e.g. the inability to display Windows admin rights prompts.

If vorpX can’t hook a game, try the new desktop viewer. Especially in tandem with the third new feature the vorpX desktop viewer now is the ultimate VR flat game cinema.

Virtual Monitor

The new virtual monitor finally makes running games at higher resolution than your actual monitor allows a breeze. All important resolutions are predefined, and you can easily add more if you want in the config app.

Added benefit for desktop capturing and playing games unhooked with the desktop viewer: the virtual monitor always runs at the refresh rate of your headset, which removes any form of micro stutter that normally is the result of capturing e.g. a 60Hz monitor and displaying it on a 90Hz headset.

The easiest way of using the virtual monitor is launching the vorpX desktop viewer and putting on your headset. Per default vorpX will then switch to its virtual monitor.

Full Changelog

Biggest changes from official (21.3.5) to last cutting edge build (24.1.0)

• Motion Controller gestures that easily let you map VR controller gestures to key/button presses. vorpX gaming as close to native VR as never before.
• A virtual monitor has been added that lets you play games at arbitrarily high resolutions and always has the exact same refresh rate as your headset, which is especially great in cunjunction with the desktop viewer. The smoothest VR desktop experience ever.
• Desktop viewer rewritten to minimize CPU/GPU usage, get rid of a few annoyances, and work great with the new virtual monitor.

Biggest changes since 24.1.0

• Redesigned rendering/post-fx pipeline that significantly reduces the amount of GPU memory used by vorpX at high resolutions.
• Custom memory manager that keeps memory allocated by vorpX separated from game memory as much as possible. Improves general stability everywhere, most notably when using high resolutions with some 32-bit games, e.g. Dragon Age Origins, Venetica.
• Special treatment for 32-bit games able to handle more RAM than the usual 32-bit 2GB limit. vorpX can now detect and directly utilize the extra memory. If you encounter crashes with 32-bit games at high resolutions, check the internet for tools that make them ‘large address aware’. Note that trying that with modern 64-bit games has no effect, those can use all your RAM per default.
• Major (ongoing) spring cleaning continued: lots of internal changes and refactorings that improve general stability and/or help keeping the developer of this Tower of Babel happy.

Noteworthy smaller changes/fixes since 24.1.0

• Optimized texture sharing between game and vorpX threads. Fixes DX12 black screen caused by nVidia driver 580.88+ and in general may/should be a bit smoother under high GPU load.
• Improved cursor tracking. Fixes cursor flicker e.g. in AC:Valhalla/Odyssey.
• Cinema mode uses reduced lightmap sizes in 32-bit games that aren’t large address aware to squeeze out some extra GPU RAM for higher resolutions.
• DX9: Some rarely/never encountered StateBlock related stuff handled. Just in case.
• DX9: Hooking related changes that may improve hooking reliability in some cases.
• DX9: Generic 3D/Headset modes did not work on some AMD GPUs
• DX9: Fixed an issue that could cause games to hang on device creation.
• DX9: Fixed an issue that could cause games to crash on display mode change.
• DX9: Fixed an issue that could cause games to crash on load (e.g. GTA IV).
• DX9: Fixed an issue that could cause games to hang fullscreen (e.g. Splinter Cell 3).
• DX9: The start scene had some weird render glitches in ‘Generic VR headset’ mode.
• DX10: Potential exception on init (e.g. Crysis DX10)
• DX11: Support some rarely used DX11 features (e.g. WoW non-legacy DX11)
• DX11: Improved G3D performance, up to 300%! Don’t get too excited though, that is an outlier. Usually expect anything from 0%-15%.
• DX11: More efficient multithreading. Improves FPS in some games (e.g. Elex 2).
• DX11: Image was garbled in some games, e.g. ArmaA III (24.1.0 regression).
• DX11/12: Optimized shader bookkeeping. Can save >200 MB of RAM (e.g. HZD).
• DX12: More efficient resource bookkeeping. Up to 20% better FPS (e.g. Uncharted 4).
• DX12: Fix for hiccups/uneven FPS in some games (e.g. The Last of Us/Uncharted 4).
• DX12: display mode switching/window resizing failed for some games (e.g. Far Cry 6)
• DX12: various authoring hotkeys did not work.
• Tracking: The jump/crouch detection didn’t work correctly anymore.
• vorpX control: App could crash on startup (24.1.0 regression).
• vorpX control: App could crash after installing hook helpers.
• vorpX control: App could hang after running for a while.

Game Profile Changes/Fixes since 24.1.0

• Cyberpunk 2077: support for latest game version.
• Dark Souls III: scalable HUD didn’t work under some circumstances.
• The Elder Scrolls Online: shader fixes for latest game version.
• The Witcher 3: The profile’s mod part could activate itself without vorpX running.
• World of WarCraft did not work anymore after removal of the old D3D11 renderer.
• Abzu: ini changes were applied on each launch instead of just once.
• Hellblade: ini changes were applied on each launch instead of just once.
• Observer: ini changes were applied on each launch instead of just once.
• Prey (2006): resolution wasn’t set as intended due to a typo.
• Conarium: improved DirectVR memory apply on/off check
• Deus Ex: Human Revolution: various fixes.
• The Surge: motion blur hint added.
• Morrowind: MGE shader chain could become unavailable.
• dgVoodoo2: shader parser for versions 2.7+

[Detective_Yoshi]

VRified Games wrote:

Hiya

Im having a hard time setting it up when I run the script the vorpx controls do not work no button bindings or tracking, same with head rotation

Only vorpx menu shortkeys and positional tracking works

Need help, I really want to showcase this mod on the channel

Yeah! Im always watching your channel and waiting for your tutorial for this too since I was already playing with the old profile. Hope its not as difficult to install as it seeems to be. Great work on your videos!

[RJK_]

I apologize,”Misalignement” may be a wrong term of mine, the HUD becomes “misaligned” only only when using higher 3D settings then normal.
I should have been more precise about what the script does. In TR Legend you have 3 keys that open HUD related views. ESC for HUD, TAB for PDA and J for another menu. Normally in addition to those you need to press a vorpx hotkey to make the hud termporarily visible (mono or Z3D) when playing with higher 3D strength then normal. When pressing -any- of those keys, the script additionally triggers a vorpx hotkey, eg. ALT+X which i found quite helpful.

In short: The script let you trigger a vorpx hotkey together with 3 other keys in order to save that extra keystroke. Of corse its not a 100% solution (game auto hints) but helped me to enjoy the game at higher 3D settings :-)

[RJK_]

I wrote a little key helper for Tombraider Legend where you can view the misaligned HUD properly on higher 3D settings. The script allows you to use several keys together with vorpx in order to swap 3D settings.
Get it here :
https://rjkole.com/gamestuff/vorpx/vorpx_keyhelper/trl_legend.php

[VRified Games]

Hiya

Im having a hard time setting it up when I run the script the vorpx controls do not work no button bindings or tracking, same with head rotation

Only vorpx menu shortkeys and positional tracking works

Need help, I really want to showcase this mod on the channel