-
Search Results
-
In reply to: Titanfall 2 (v2.0.11.0) profile broken?
Titanfall 2 is also now crashing immediately for me too when trying to run it with vorpx. Runs fine without vorpx. Something changed.
In reply to: Games with 3d geometric
There is already a topic with a lot of them :
You can check engines&games here :
https://rjkole.com/gamestuff/engines/index.phpOr looking for the game on the forum.
Or just trying it (the only way to be sure).
From my personnal experience, best profiles are :
Originals Bioshock 1&2&Infinite
Originals Metro (I tried 2033 it has perfect G3D and 6dof) and Redux versions (I tried Last Light Redux and it was perfect but I recommand a top end graphic card with this Redux version, without even knowing if it’s better than standard)
The ascent (and some others Unreal Engine 4 games) works well.
Black Mesa (&Xen), probably Portal and Dark Messiah.
People say Dishonored, Titanfall 2, F.E.A.R, Mirror’s Edge, Fallout 3, etc. works well.
Probably Clive Barker’s Jericho & Undying too.
Originals Stalker works with good G3D but without adavanced lighting (DX9 only).Kingdom Come Deliverance, Metro Exodus and Farcry Primal works well enough (and so probably Cry Engine games like Prey 2017 / Crysis 1-3, and Snowdrop Engine games like Facry 2-5)
Even if concerning Metro Exodus, I prefer Z3D during most of the game (except bunkers&spiders which are great in G3D) in order to have raytracing, at least on Reverb G2 (no compression, so it’s stunning).
Some Z3D profiles are very close to G3D (Atomic Heart, Frontier Of Pandora, Unreal Engine 5 games seems to work great from my experience).
I may be wrong, but I think most DX9 games probably have perfect G3D, and some DX11 games too.
In reply to: Good Full VR Games for Beginners
6dof
Titanfall 2
Metro 2033 redux (Steam)
Metro last light redux (Steam)3dof
Metro exodus (steam non updated version)
In reply to: Whats the best 3D games? (NOT vr, but 3D)
F.E.A.R. and Titanfall 2 were both great back in the day, but I’m not sure how you’re defining “old school shooting games,” exactly.
Topic: vorpX 25.1.5 Available Now
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+
In reply to: Direct Vr Titanfall 2
Of course if you want to use a very high resolution in VR with G3D, you also need a good enough graphic card. I suppose Titanfall 2 isn’t very demanding, but I don’t know.
In reply to: Direct Vr Titanfall 2
I don’t know. I don’t have this game anymore, I didn’t try it with VorpX, and I didn’t use DirectVR a lot, but Ralf probably know (and maybe it’s written somewhere).
Do you have the resolution you want ingame ? It must be a very high 4:3 one.
First of all, adjust zoom level and use ClarityFX and sharpness if needed. You can try to adjust FOV (not only resolution).
If I encounter a problem I can’t solve, I usually disable auto settings (checkbox “Don’t Optimize Game Settings”), and choose the resolution and FOV myself (most of the time I have to do it anyway because I play games without DirectVR, and most of the time it doesn’t take long because it’s almost always the same values). But ralf proved me recently it may break other things to disable auto settings with this kind of advanced profiles. You can always try if nothing works. Set a FOV around 112 and the resolution as you would if you weren’t using VorpX (in game options, cfg/ini files, etc.)
When it works, you’ll probably be able to identify what was the problem, and re-enable auto settings if you need to.
PS :
changing Titanfall 2 FOV manually seems to not be very easy, but it seems to be doable.In reply to: Titanfall 2 Ea game pass and Witcher 1 steam
Both Titanfall 2 and Mirror’s Edge should work from the EA app. You could try to disable the EA ingame menu, although that shouldn’t be necessary.
Resolution isn’t really an issue. Super easily addressable for literally every game out there.
For fully featured DirectVR profiles vorpX has game specific code that lets you set the resolution in the vorpX menu in various steps. If that’s the case vorpX displays an according hint in the top/left corner of the game window and in the headset.
If not, you can always adjust the resolution in the game options yourself, just like you would do when playing on your monitor.
Also make sure to read the ‘Custom Resolutions’ section in the vorpX help. It explains how to add resolutions to your PC that your monoitor can’t display. Alternativly you can use the new virtual monitor in vorpX 24.1.0, which comes with all important resolutions predefined and thus saves you the somewhat tedious process of setting up custom resolutions.
In reply to: Titanfall 2 Ea game pass and Witcher 1 steam
Thabks for your answer, Ralf. I really dont know what happened here.
After Titanfall 2 and Mirror edge, I tried Fallout 3 (wooooow!!! It worked!!!), Deus ex human revolution (bad;psvr 1 like resoulution and distúrbing tiny hands) and Dishobored 1 (good visuals but had to use direct scan sometimes during gameplay because it messes up in game) and all of them hooked first time maybe just changing in hook helpers.
Maybe these games didnt had any issues because were started in Steam, while Mirror and Titan needed Ea play to start? But why then Mass effect original 1 worked with ea play on (and then stopped working) and The Witcher 1 Steam wont start? Well ots a bit frustating but I cant be happier playing these games in VR and very afraid that Rdr2 and Cyberpunk maybe wont hook too if I try. Im very happy with your work and that you still want to improve in future releases.In reply to: Titanfall 2 Ea game pass and Witcher 1 steam
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.
In reply to: Titanfall 2 Ea game pass and Witcher 1 steam
I never tried Titanfall 2 with VorpX but I know it works very well from others.
Maybe try to launch it without VorpX, and set it on DirectX11 or DirectX9 (VorpX doesn’t like DX10 and DX12 because it can’t render G3D, so sometimes official profiles only works with DX9 or DX11).
Did you try the hook helper, and alternate hooking ?
Some unofficial profiles requires to create a direct shortcut instead of launching VorpX (right click on VorpX in taskbar > create shortcut).
Sometimes you just have to wait and it works again (auto-update I presume), or use another version of VorpX (but I never had to and I tried a lot of games).
Hi! These games start the loading screen but wont attach and wont start, just load the title of the game, says its attaching and turn off without showijg ay message or open the vorpx hook helper menu. Titanfall 2 from game pass wich starts with the Ea play app, and Witcher 1 with steam.
With Titanfall I tried the Windows 8 compatibility mode and excluding ea apps in the vorpx menu too, like I saw in some forums here.
Played Psychonauts on Steam and it entered just changing the hook helper, and New Vegas with tweaks, both of them started without ahy problem and I did the seme steps fot those other games.
Trying tô play with Quest 3.
Anyone can help with these issues? New Vegas still works after I tried thoso two. Thabks!In reply to: Best Games
These are my favourite games, all in first person view:
– 7 Days to Die
– Titanfall 2
– Left 4 Dead 2
– Killing Floor 2
– GTA Vice City/San Andreas
– Ultrakill
– Deep Rock Galactic
– Serious Sam 4
– The Sims 4 (takes patience)Of all, my favourite has to be 7 Days to Die.
I’ve never felt so much fear in my entire life.The experience was so frightening, I obsessed on my bases’ integrity during bloodmoon.
I figured this out after a lot of trial and error. I will run through everything I did hopefully it helps others facing this issue.
1. Go into Configure vorpx – Click on Exclude Programs – Exclude EAlink.exe. For extra caution just exclude everything EA related
2. Turn off all firewall and virus scans. I use Macfee mainly, but I also needed to turn of Windows Defender Firewall scan, just turn everything off that you can. Remember to turn them back on when you are done playing TF2
3. Turn off all overlays. NVidia has a built-in overlay, steam has a built-in overlay, xbox has the game bar (for xbox game bar make sure to turn of the camera option), turn off every overlay that you can find
4. Turn off all notifications in windows so you cannot receive any pop-up messages
5. Disconnect any extra screens you have hooked to your pc
6. Lastly, go to the games exe file AKA Titanfall2.exe. Right click on Titanfall2.exe – click “properties” – Click “Compatibility” – Check “run the program in compatibility mode for Windows 8”
Check “Disable Fullscreen optimizations” – Click “Apply”.Thats it. Has been working great for me since I did all these steps. Step 6 was the last thing tried before it started working for me. So, working backwards from 6 to 1 may be a smart move. I turned the game off and back on a handful of times just to insure it was not a fluke. Keep in mind that if you turn TF2 off you will need to fully exit out of your vr mode as well before trying to restart, at least that was the case for me.
