-
Search Results
-
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.
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: Any profiles that hook to CRYNEGINE?
Well, I can answer this myself for anyone looking in the future. I was looking up ‘Crynegine’ since they have base profiles for the other engines, but for this there are profiles for:
Crysis (released 2007)
Crysis 2 (released 2011)
Crysis 3 (released 2013)
Prey (released 2017)‘Aporia: Beyond The Valley’ was released in 2017 so I’ll try the Prey profile.
In reply to: Does VorpX support Half-Width SBS?
Yes, that’s the SBS mode vorpX handles.
The way vorpX does it is actually even a bit better than half width SBS normally would be since images are always rendered at full width first and then scaled down to half width when drawing the SBS image, resulting in a 2×1 supersampled image with more preserved detail compared to directly rendering at half width.
So vorpX is actually rendering a full SBS image? Please let us choose to just display that image. Currently, rendering games in 1080p on a 1080p full SBS (3840×1080) monitor results in unreadable text. I need to go to at least 1440p for text to be readable which is very demanding and it sounds unecessary if the image is actually already rendered in full SBS and having to scale it back and forth is what destroys the image quality.
You can use SBS (2:1) + Stretch screen (aspect ratio option) = Normal 3D
Not sure what you mean exactly. My device has a native resolution of 1920×1080 per eye, so the resolution for 3D SBS is 3840×1080. If I set game resolution to this the image gets squished. “Stretch screen (aspect ratio option)” Is this a vorpx setting, I can’t find it. Or is there some other software I can use specifically for the scaling?
Normally I just set the game resolution to 1920×1080 (or 2560×1440 etc) and then vorpx works fine but the image quality is very degraded when I do this, something is messed up with the scaling. Changing nvidia scaling from “GPU” to “Monitor” made it a little bit better but it’s still messed up. I don’t have this issue with geo-11 and full-sbs but in my experience it’s compatible with way fewer games so it only works for a few titles, but the point is I know it’s not supposed to look as degraded as it does and the only reason I can think of is that something is going wrong with the scaling
For example this is how half life 2 looks at 1080p, the text is all messed up. But it’s not just the text or hl2, everything looks way lower res in other games like crysis 3 as well. https://postimg.cc/HrGxjpM7
In reply to: General Game setting to turn off /test with VorpX
Older games use lightmaps to emulate lighting in static geometry, this includes some AO approximation. Realistic games like STALKER, HL2 or The Witcher have darkening in corners, under vehicles etc and look great already. You would be doubling the AO effect in world geometry, which is overkill.
Newer games started to introduce dynamic AO (from Crysis on), and if AO has to be disabled for G3D to work glitch free, they look horribly flat/fake in world geometry because of the missing light maps.
Did anyone of you got the EPIC STORE Crysis Remastered Triology
and tried the Vorpx profiles on Crysis 1,2 and 3 ?Did any of these work okay?
In reply to: List of games with Weapon Hiding
The list is shorter currently than I’d like it to be, will check some more first person games shortly together with adding gestures. Got somewhat shoved to the backseat when I started to experiment with gestures. Same for the related authoring UI.
With the current detection mechanism my guess would be that it should be possible to add the feature to maybe half the G3D first person games. Additional manual authoring based on shaders or buffers is thinkable and would probably be able to catch most of the other half, but would also require more work per game than the current mechanism. So no promises in that respect.
Current games with auto weapon hide:
Aliens: Colonial Marines
Black Mesa Source
Crysis
Fallout 4
Half-Life 2 and episodes
Halo MCC (tested only on the first campaign)
Portal 2
Skyrim SE
Titanfall 2In reply to: Crysis remastered Epic games ?
Has anyone managed to get this to work? The YouTuber above doesn’t explain how he did it. I’ve tried using the profiles from Crysis / Crysis 3, changing the exe to the crysisremastered.exe. It attaches, but VorpX doesn’t seem to start with the game. I’m using HP Reverb G2, either SteamVR or OpenXR, same result…
Just a heads-up that the feature has to be enabled on a game-to-game basis since it rquires some game specific settings. It doesn’t work automagically. Currently it’s enabled for the following games: Half-Life 2 (+episodes), Portal 2, Black Mesa Source, Titanfall 2, Fallout 4, Crysis, Skyrim Special Edition, Aliens: Colonial Marines.
Hi all, new vorpx user here
I purchased vorpx last week after having watched numerous youtube videos and lurking on the forums.
Everything installed and I can pull up the desktop viewer, vorpx starts and also the configuration utility boots up
However, when I start any game with a vorpx profile, for example dishonored (without steam VR running), the intros run in 3d and I can boot into the game, but when I have played just a few seconds (which look absolutely amazing in 3d) the game freezes, and then the link between my oculus and pc drops out (this happens with a physical cable and also through the new air link feature on the quest 2). The same happens with Crysis 3 which I have on my origin account.
If I am playing a native steam VR game (eg the Talos principle) I can play without any dropouts, so I am assuming the link is good.
I have looked through the various help sections but nothing seems to apply. I have completely uninstalled my AVG antivirus, logged out of my VPN and have also uninstalled any hardware utilities such as HW monitor; GPUZ etc. I cannot see any other software that to my mind be interfering but am assuming there is still something running in the background which is causing conflicts.
It is really frustrating as I feel I am so close to getting everything working.
I am now thinking of buying another SSD and having a dual boot windows 10 PC with the new installation being for purely VR/Vorpx games with nothing other than the OS and necessary programs on.
Any help you can think of would be greatly appreciated
Ian
Below is the list list of games that this feature will be enabled for in vorpX 21.2.0 (release tomorrow).
Tweakable options include the feature mode (off/auto hide/size and position only/always hidden), the auto hide timeout, the position of the weapon in 3d space, and weapon FOV and 3D-Strength for tweaking its size. Shouldn’t really be necessary to tweak anything though. Each profile has carefully chosen individual defaults that work just fine.
Games for the first release:
– Half-Life 2 (+episodes)
– Portal 2
– Black Mesa Source
– Titanfall 2
– Fallout 4
– Crysis
– Skyrim Special Edition
– Aliens: Colonial MarinesMore games will follow shortly, I’m fairly confident that adding the feature will be possible for about 4 out of 5 potential candidates, i.e. first person G3D games.
Note that in this first release there is no UI for changing gamepad/key assignments, will also follow shortly. For the time being make sure to use a game’s default bindings, otherwise vorpX might not be able to reliably detect when the weapon is supposed to be shown/hidden under all circumstances.
In reply to: Crysis remastered Epic games ?
https://www.pcgamer.com/crysis-gets-vr-mod-beam-maximum-graphics-directly-into-your-face/
Hard to imagine we had vr in 2013.
Hello,
I seen some topics on my search in regards to independent movement of the head vs gun. Some was saying this can only be done in ARMA III. (topics from like 2019)
Is there a tutorial on how this can be done? I saw mentions of like track IR etc.
And what’s the latest on this? I initially tried to play Far Cry 5, which had both head and gun combined. (I though because of imported profile).
Then I tried Crysis 3, with same results.
Is there any workarounds, did anyone manage to get the head and gun move independently, or better even, bind the gun to the hand controllers (I`m using Reverb G2). I found a demo that came with the WMR app, I think it was Halo or something, that had the guns binded to the controller – that was very impressive.
In reply to: A word of thanks
I have played through Bioshock (the original) and Bioshock Infinite in VR and it was one of the best VR experiences I had. It’s actually up there with Half Life Alyx for me. Being inside these worlds was something really special and I actually enjoy that it’s a seated experience. I’m playing through the Bioshock Infinite DLCs right now and Rapture looks amazing with the newer Engine and in VR. I honestly don’t know why some people give VorpX a bad name since especially with direct vr it’s pretty easy to set up. I will probably buy the new Geforce 3080 just for VorpX since I really want to enjoy all of these great games with maximum visuals and great performance since VorpX really brings my 2070 Super to its knees on higher resolutions in games like Crysis.
In reply to: going to upgrade from gtx 1080 to rtx 3080 !
I have the 2070 Super currently and for 2D it’s more than enough currently but VorpX really brings it down to its knees especially at higher resolutions, so I have really been thinking of selling it and getting the 3080 which looks like a really great GPU for VorpX. Playing Crysis in VorpX at high resolutions with a great framerate then just might be possible. I wonder what Ralf thinks about Nvidias latest cards and if they are worth it and what choice he would make if he wanted to buy one for VorpX?
