Search Results for 'Dark'

[nm723548]

The working G3D profile has been uploaded to the cloud.

With the Xash3D FWGS Engine Build 3963, you can play and complete Field Intensity, Echoes, C.A.G.E.D., The Trap, The Gate, Delta Particles, They Hunger I–III, Military Duty, Escape From Darkness, Residual Point, Heart of Evil, Black Ops, Uplink, and many other great Half-Life fan add-ons.

The Xash3D FWGS Engine performs very well, even at very high resolutions.

Once, there was a Czech website called Modifikace.cz, which focused on reviewing and rating Half-Life add-ons. One of the highest-rated add-ons on that site was “The Gate.”

It is worth noting that one of the highest-rated fan add-ons for Return to Castle Wolfenstein is called “Timegate.” While similar in both name and execution, both add-ons are highly regarded. However, it seems that the Half-Life version is far less known, as I have never seen it appear on any English lists of top-rated Half-Life fan add-ons.

Steps to make everything work:

Download Xash3D FWGS Engine Build 3963 and extract it into your Half-Life directory, where the original game and its two expansions are installed, as their assets are required for some fan add-ons to function. Overwrite files if necessary.

In the autoexec.cfg file (both in the main folder and in each add-on folder—for example, field_intensity), add:

default_fov 120

Inside the add-on folder (for example, field_intensity), open video.cfg and add or modify:

width “3840”
height “2160”

For this resolution to appear in-game, you must first select it in your display settings after launching VorpX Virtual Desktop. To enable it, create a custom resolution in VorpX Virtual Monitor. Then launch VorpX Virtual Desktop, right-click your desktop, open Display Settings, and select the resolution.

Do not change the resolution while playing, as this will cause the game to crash.

Optionally, you can enable Virtual Super Resolution in AMD Adrenalin or NVIDIA Control Panel. This removes the need to launch VorpX Virtual Desktop beforehand.

If the default_fov command does not work from the config file, you can apply it manually after launching the game by pressing the ~ key. A sensible FOV range is 105–130, depending on whether you prefer greater immersion or a wider field of view. If the image appears zoomed in, slightly increase the FOV.

Running the add-ons:

Always run add-ons using a dedicated shortcut.

Create a shortcut for xash3d.exe and rename it according to the add-on, e.g., FIELD INTENSITY.

Right-click the shortcut, open Properties, and if your add-on folder is named field_intensity, append the following after \xash3d.exe:

–console -32bpp -game field_intensity

The full target line should look like:

\xash3d.exe” -console -32bpp -game field_intensity

Optional:

The original Half-Life was at its best when the gameplay truly reflected its name—when you were barely alive, desperately searching for medkits and ammo.

Unfortunately, Opposing Force and many fan add-ons that use its assets are too easy on medium difficulty. Therefore, it is recommended to play these add-ons on the highest difficulty level for a more challenging and engaging experience.

MODDB:

Half-Life 1 Mod Archive from the 2006 DVD Collection | With Lost Mods

[nm723548]

The working G3D profile has been uploaded to the cloud.

With the Quakespasm-Spiked 24-03-01 port, you will be able to play and complete Arcane Dimensions, Brutalist Jam I–III, Dwell, Alkaline, Limnal Places, Spiritworld, Xmas Jams, Func Map Jam X, Mjölnir, Immortal Lock (an add-on made by a very clever lady from Canada), Malice Refined, and many other great add-ons that transform good old Quake into the king of the VR realm.

Arcane Dimensions, Alkaline, and Brutalist Jam III are probably three of the best ultra–high-quality add-ons that the gaming community has given us for free.

With Arcane Dimensions, Alkaline, and Brutalist Jam III, the creators transformed the base game into an almost metaphysical, gargantuan-in-scope, often surreal experience (particularly in VR). They were also probably among the first to use infinite loops in some maps, similar to those previously seen in sci-fi movies.

Steps for everything to work:

Main problem: After launching the game, there is no image in one eye.

Workaround: After launching the game in VorpX Virtual Desktop, go to Options → Video Options, change Vertical Sync (on or off—it doesn’t matter), and click “Apply Changes.” After applying the changes, everything should work correctly again, and you are ready to play. I tried to fix this via CFG files (e.g., V-Sync), but without success.

Download Quakespasm-Spiked 24-03-01 and extract it into the Quake folder. Overwrite files if needed.

Set the resolution to 3840×2880. For this resolution to appear in-game, you must first select it in your display settings after launching VorpX Virtual Desktop. To enable it, create a custom resolution in VorpX Virtual Monitor. Then launch VorpX Virtual Desktop, right-click your desktop, open Display Settings, and select the resolution. After that, launch the game and choose 3840×2880.

After launching the game in VorpX Virtual Desktop, go to Options → Video Options, change Vertical Sync (on or off), and apply the changes.

Running the add-ons:

Always run the add-on using the shortcut you created.

Create a shortcut for quakespasm-spiked-win64.exe and rename it to match the add-on, e.g., BRUTALIST JAM III.

Right-click the shortcut and open Properties. If you extracted the add-on to a folder named “qbj” (for example), add the following after \quakespasm-spiked-win64.exe: -heapsize 1597152 -game qbj

The full target line should look like:
“\quakespasm-spiked-win64.exe” -heapsize 1597152 -game qbj

If the add-on contains larger maps, consider using a larger heapsize. This helps prevent crashes caused by memory limitations.

Before launching the game or add-on, you may need to set the display scaling to 100% and the resolution to 3840×2880 in VorpX Virtual Desktop. Sometimes the game may start at a lower resolution even if it incorrectly displays 3840×2880 in the video options.

Rule of thumb: Always set scaling to 100% and the desired resolution in desktop settings after launching VorpX Virtual Desktop and before starting the game or add-on.

The in-game resolution should be judged visually—everything should look very sharp. At lower resolutions, the image will appear slightly pixelated or blurry.

Making your own soundtrack:

To create a custom soundtrack for Quake fan maps, install Foobar and Foobar Portable. In one instance of Foobar, you can play the Herbstwind (Patrick Lynen | Meditation & Relaxation) track (for example), while in the other you play your preferred music with Playback → Order set to “Repeat Playlist.”

After setting up your soundtrack, launch the game/add-on/map and enjoy the best possible version of the experience.

The Dungeon Synth Archives channel on YouTube offers a lot of music that fits Arcane Dimensions. You can record music for specific maps using Windows Recorder, play the map with your custom soundtrack, and then delete the recording afterward.

Optional I:

You should consider playing Brutalist Jam III in G3D—it feels like entering the worlds of Zdzislaw Beksinski (a famous Polish surrealist/grotesque painter) in VR.

Over time, some players may consider it one of the best FPS add-ons ever created. Brutalist Jam II also features a remarkable hub that is truly outstanding and unforgettable in VR. Some maps in Brutalist Jam III offer a one-of-a-kind experience, with vast vertical spaces that feel both suffocating and breathtaking at the same time.

It could be said that VR was waiting for Brutalist Jam III—as it is so magnificent, raw, and elegant.

Optional II:

For the best immersion, consider using 3M Peltor (or similar) noise-canceling headphones together with Panasonic in-ear buds, and a backlit keyboard for night play.

Consider using a Samsung HMD Odyssey Plus headset for excellent colors and contrast in Quake. Darkness is often a crucial part of the experience, so deep blacks matter greatly.

The Samsung HMD Odyssey Plus still offers outstanding color and contrast thanks to its AMOLED display.

When buying one, ask the seller whether the USB cable works properly. Signal interruptions can crash AMD drivers. If signal loss is detected (VorpX acts as a virtual monitor), the system may switch to standard graphics drivers, resulting in a black screen.

AMD Adrenalin driver crashes may still occur even with a fully functional cable. In such cases, both the monitor and headset may go black. You may need to restart your computer and reinstall the drivers via Windows Device Manager—sometimes twice, as the first attempt may fail.

Minor scratches or lens blur can be removed using PolyWatch Plastic Polish, though it may damage certain lenses. Use PolyWatch only if you are sure it is safe for your device.

Removing scratches requires applying firm pressure—be careful, but don’t be overly hesitant.

If it’s your first time, watch several YouTube tutorials. PolyWatch works by dissolving and polishing plastic, so avoid overuse as it can deform or reshape lenses.

Some interesting ideas to try:

Entering the City of Pale

Entering the City of Pale is a Quake fan map by Benoit “Bal” Stordeur.

Once a year, there is a truly magical time called Christmas. It is the only time when you can enter the City of Pale—the city gate opens only once a year during Christmas.

Set the Sorcerer’s Dream track by Old Sorcery in Foobar, and launch the game in VorpX Virtual Desktop after midnight during Christmas, when everyone is asleep.

After opening the city gate in VR, you won’t be able to go further. At that point, you should go to bed and fall asleep, reflecting on what you saw and, most importantly, the feeling of the solemn Christmas atmosphere and the place you visited.

In this way, you may pass through the gate and enter the City of Pale in your dreams. During Christmas, once a year, the gate opens in the dream world as well. The younger you are, the higher your chances—entering such places in dreams becomes harder with age, as people begin to question the possibility and they erase such experiences from memory.

To fully understand this idea and appreciate the brilliance of Entering the City of Pale, you must experience it in VR (G3D).

Entering Dante’s Hell

If any vision of hell exists, it is perfectly captured in the Sheer Hellish Miasma Quake map by CZG.

Set tracks 3 and 4 from the Mohnomishe album by Zoviet France in Foobar, enable “Repeat Playlist,” launch the Honey add-on in VorpX Virtual Desktop, and play until you reach the first map.

Experience Dante’s Hell if you are searching for deeper meaning or a change in your life.

[nm723548]

The working profile has been uploaded to the cloud.

After trying the official profile without success, I was able to achieve depth using a different official profile.

The 3D effect breaks every time you take out a weapon or a blackjack. After using them, always hide them using the ~ key (or any other key you assigned earlier for that purpose). This restores the 3D effect. In most other games, this issue would make the game unplayable in 3D, but in Thief it’s irrelevant, as the game focuses on stealth and exploration.

With everything properly configured, the game looks as good as Blood in G3D. The City in the “Endless Rain” and “Winds of Misfortune” fan missions is breathtaking.

Once everything is set up, the 3D effect is strong, creating a real sense of moving through space and observing objects with depth.

Steps to make everything work:

Install TFix 1.27 for Thief I, Thief II, and Thief Gold.

Copy (clone) thief.exe and rename it to thiefvorpx.exe. Repeat the same process for Thief II and the executable inside the Thief Gold folder.

Change the FOV to 140 in cam_ext.cfg. Don’t forget to remove the “;” so the optional FOV setting works. You can adjust the FOV to your preference, but remember you may also need to tweak VorpX Immersive Mode settings and save the changes.

Set the resolution to 3840×2880. For this resolution to appear in-game, you must select it in your screen settings after launching VorpX Virtual Desktop. To enable this, create a custom resolution in VorpX Virtual Monitor. Once created, launch VorpX Virtual Desktop, right-click on your desktop, open Screen Settings, and select the resolution. Then launch the game and choose 3840×2880.

Websites like Thief Missions and Keep of Metal and Gold host over a thousand fan missions. Most are unrated, but the only way to judge them—especially in VR—is to play them. Even a simple mission aesthetics can be great to look at in 3D. With the sense of moving through space, you gain access to countless new places to explore, with VorpX acting as the only secret door to them.

Use AngelLoader to catalog and launch fan missions. Start them through VorpX Virtual Desktop via AngelLoader.

After playing for a while, adjust VorpX Immersive Mode settings to your liking—distance, scale, curvature, and so on.

Use Alt + Space to recenter if you feel too short or if you feel that the picture is misaligned.

Optional:

Set F5 for quicksave and F9 for quickload—you’ll use them frequently.

You can also try cloning the Dark Messiah of Might and Magic VorpX profile, as more options seem to work in Z-Normal mode. However, there may be ghosting issues.

For the best immersion, use Peltor (or similar) noise-canceling headphones together with Panasonic in-ear buds, and a backlit keyboard for night play.

Consider using a Samsung HMD Odyssey Plus headset for excellent colors and contrast in Thief and The Dark Mod. Since darkness is a core part of the experience, display quality matters greatly.

The Samsung HMD Odyssey Plus still offers outstanding color and contrast thanks to its AMOLED screen technology.

When buying one, ask the seller whether the USB cable (which is long and sturdy) works properly. Signal interruptions can crash AMD drivers. If the system detects a signal loss (VorpX acts as a virtual monitor), it may switch to standard graphics drivers, resulting in a black screen.

Note that AMD Adrenalin driver crashes can still occur even with a fully functional cable. In such cases, both the monitor and headset may go black. You may need to restart your computer and manually reinstall the graphics drivers—often twice, as the first attempt may fail—via Windows Device Manager.

Minor scratches or blurring on lenses can be removed using PolyWatch Plastic Polish. However, on some headsets, it may cause additional blurring.

Only use PolyWatch if you are certain it’s safe for your device, as improper use can damage the lenses.

Removing scratches requires applying firm pressure—don’t be afraid of pressing too hard, but proceed carefully.

If you’re doing this for the first time, watch several YouTube tutorials. PolyWatch works by dissolving plastic on a microscopic level, so avoid overuse, as it can deform or reshape the lenses.

Tips for new Thief players:

Always pick up rope arrows—they are reusable.

You can pull yourself up by pressing and holding Space after a jump.

Shooting rope arrows close to edges makes climbing easier.

Some surfaces (like windowsills) are wooden—these can support rope arrows if you aim carefully.

Certain pipes can be climbed.

Some roofs can be climbed by jumping and holding Space, similar to windowsills and walls.
Doors and windows can be deceptive—some that look unusable can actually be opened. Always check them up close.

Knocking out peasants is not always a good idea. They may serve a purpose, such as opening doors, which they cannot do if unconscious.

[Boblekobold]

There is already a topic with a lot of them :

Geometry VR Game List.

You can check engines&games here :
https://rjkole.com/gamestuff/engines/index.php

Or 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.

[Anatolij]

Greetings Ralf. I just encountered a serious performance issue with the latest version of VorpX. Specifically, with DX9 and even DX11. Example: In The Witcher and The Witcher 2, with the latest version, I get 30-60FPS out of 90. But with version 21.3.5, The Witcher 1 runs at a stable 90FPS, while in Witcher 2 70-90FPS. The same with The Darkness II. With the latest version, I get 30-70FPS out of 90, but with version 21.3.5, I get a stable 90FPS. How can this be? Why does the new version have such serious performance issues, especially on a pre-high-end PC? And how can I disable this blatant automatic update that only ruins everything? I want to enjoy the game at a stable 90-120FPS with version 21.3.5, instead of constant lag and low FPS with the latest version.

My system: Windows 11 Home, 25H2 26200.7309
M.B.: ASRock X870 Steel Legend WiFi / CPU: AMD Ryzen 7 9800X3D / RAM: Kingston 2x16GB DDR5-6000MHz / GPU: PowerColor 7900XTX Hellhound White 2800 MHz UV 1.12V/SSD: Kingston 2TB NVMe

[Ralf]

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.

[sark666]

My Xbox controller behaves strange in some games. It works fine in dishonored with vorpx set to gamepad or m/kB, zero issues in that game.

But the next game I tried was the long dark. The gamepad works but I’m running at what seems double the speed the game allows. The game isn’t running too fast like was an issue with older games, it’s just the inputs seemingly triggering this.

I thought as a workaround I’d try m/kB in vorpx but same issue. Not many games have it but in-game you can disable gamepad support in the long dark. I disabled gamepad support and thought I’d use microx to bind gamepad inputs to kbm. This worked fine flatscreen but the issues I had still persisted in vorpx. I tried as gamepad, kbm and even turning controls off in vorpx but that didn’t work.

I then realized even if I have gamepad off in vorpx it still seems the gamepad. What I mean is you can’t seem to truly disable gamepad support.

I then tried hidhide (a utility to hide devices from apps) but to my surprise vorpx still saw the controller.

I gave up and then tried amnesia the bunker. This too had input issues. It would always run even though in-game run is normally a run button and ever input seems to be inputting twice. For ex is press a button to pull out my gun and the play would draw the weapon but immediately put it away.

I’m usually pretty good at working around quirks but I can’t resolve this.

I also tried gamepad override, partial and off, no difference.

If there’s a way to resolve this great, but I would also like a feature to truly disable gamepad support as in vorpx doesn’t see it at all and I would do keyboard mapping. Ideally things would work in-game, but if vorpx had this ability I could have probably worked around it myself.

Another issue with using a gamepad is the menu binds. Binding these to joystick clicks is game breaking for some games as they need it for click run etc. I would think the solution is to use long press for the vorpx menus and a normal click would behave properly in game.

Also I wish we could do custom bindings. For ex, dishonored as I mentioned works great, but each time you die the fov resets. At first I was doing a direct VR scan each time, but then I realized just a quick fov fix by pressing F8.

Great but I don’t want to go in the menus each death to trigger this. Im no where near my keyboard when I play VR. Being reliant on needing to be near my keyboard is a dealbreaker for me. So I’ll probably use some binding utility to bind f8 to an input, but it would be great if we could do that in vorpx

I might as well mention it here instead of starting another thread but Batman Arkham city, another game that works fine with my gamepad, but I like to play in VR. However in VR mode the right stick up down does not change the camera angle only left right rotation works. I thought for this profile it was defaulting to lock the y axis on right controller but I went in the menu and saw it was already off. If I switch the game to cinema mode the right joystick behaves as expected but not in VR mode.

Sorry for the long post, I haven’t tried vorpx in years but trying it again now I’m liking what I see in a few of the games I tried but the gamepad issues are a problem.

I hope there are workarounds for this but just for flexibility sake I do wish there was a way to truly block vorpx from seeing my gamepad, and then I could have worked around it, obviously ideally it would work properly as a gamepad in game.

[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]

This channel is posting some Vorpx games these days like Castlevania, Darksiders, Psychonauts, and among them, Hail to the king, babe, come get some!!!

https://youtu.be/6xkxFEyWPYQ?si=DMdL82pSesYHYnV0

[Boblekobold]

duke54 wrote:

Vorpx gives you stereoscopic 3D, so it’s not like native VR, it’s more like using a 3D TV IMHU, but if you think that would be fun, give it a try!

VorpX is like native VR with a lot of games, but usually more beautiful, clearer&sharper with more display options, and most of the time no motion aiming / handling (it would require a mod). Some games even have great 6dof camera.

I don’t know about this game. There is an unofficial profile in the cloud section.

This game seems to allow an high FOV (something required to get proper full VR). You should usually choose a value around 112°.

So if the profile has headtracking & G3D, it’s probably like native (with the right resolution & FOV). It it has only headtracking and Z3D, it’s like native but with a lesser type of 3D.

Considering this is an unofficial profile, it’s hard to say what it does without testing it.

This game seems to use HPL Engine.

According to this website :
https://rjkole.com/gamestuff/engines/index.php?selengine=HPL%20Engine
there is G3D sometimes with this engine (Amnesia: A Machine for Pigs, Amnesia: The Dark Descent).
If it works, it probably require to play the game in DX11. This game seems recent so I don’t know if shaders will work in G3D without an official profile.
DirectX12 usually only allows Z3D but if there is a profile, it probably works.

[Cless_Aurion]

Thanks again for your time replying. I really appreciate you taking this issue seriously.

Simply sending the res to the headset that you dial in in SteamVR no matter what the actual game res is doesn’t make sense.

Yes, I know. I’m just saying it so I could try and force the resolution manually, instead of having an arbitrarily “double the vertical resolution” setting.
I do that with BigsScreen for example. Even when watching a 1080p movie, or playing some old flat game, I will run native resolution (5500p), even if it is to get the dark environment or the screen borders to have 0 aliasing.

Like said above, you have to look elsewhere to pinpoint your issue. There is no such thing as a “2160p wall” in vorpX.

I am aware, that is the tragic part. Unless its something driver or hardware/HMD specific, I can’t pinpoint anywhere else since there are 0 issues elsewhere, its only VorpX failing me (which to be honest, its the magic software that made me go and spend $2k on a new HMD at all) :S
If I had another high resolution HMD over 3000p around, I would test it there, but I only have my VP1 that is 1600p, which won’t do.

The issues other people with higher than 3000×3000 per eye HMDs (mostly Pimax users) seem to match closely my experience as well, so I suspect everyone with high resolution HMDs has this issue. As more and more high resolution HMDs come in, this issue seems like it will become more and more prevalent.

A game rendered at 1080p doesn’t look better just because you copy it to a 5500p texture before sending it to the headset obviously.

We agree in that of course. As long as the image is wrapped around your head or, the resolution of your HMD has a higher PPD than the screen in front you with the game, it should make barely any difference.

The problem here is… we are DEFINITELY copying a 4860p game image into a 3000p texture before sending it to the headset.
Not only that, but because I am watching that using the floating VorpX display, now we are rendering what is visible in my FOV of a downscaled 4860p game image at 3000p.
So, we are squishing that 4860p image into around 2000p in front of my eyes. That’s why aliasing is so aggravating.

That is also why when I lean in, I can see way more detail that I couldn’t see before
Also, just in case, yes VRAM bumps up as it should as I scale up resolution over 2160p (in fact, BG3 at 4860p is almost maxing out my 24GB of VRAM, which is about double what it consumes at 2160p).

Your “2160p wall” sounds suspiciously as if the game actually runs at your monitor’s res although you think it doesn’t.

Indeed, I thought that too, and it might be the root cause of this issue. If I had a lower(or higher) resolution monitor I would try that theory by plugging only that other monitor in, but I sadly can’t.

The best way I could control for that on the tests I already did was:
1. Start VorpX (virtual display gets enabled)
2. Set Virtual display resolution to 4860p.
3. Start SteamVR and disconnect all my 2160p displays so only VorpX’s Virtual display is enabled.
4. Start the game making sure that the only display windows (and the game) detects is VorpX’s 4860p monitor.
5. Change the resolution of the game to 4860p and restart (or make sure the resolution is already at 4860p or any other higher number than 2160p).

To deal with such potential issues, either run games windowed or (assuming you already have set up a high enough custom resolution), try setting your desktop res to it before launching the game.

I already did that, of course. In fact, all the tests I ran I did try in windowed mode first. Then after it didn’t work, I started to experiment and tried fullscreen and borderless modes without any success (which kind of makes sense).

If a game actually runs at 5500p, vorpX creates a 5500p headset render target. You wouldn’t even be able to let it create something smaller than that even if you wanted when the image vorpX receives is actally a 5500p image.

I’m 100% sure that is not happening in my computer though. The games and the image VorpX is receiving, are higher than 3000p. This is the core of the issue, which you in your own tests proved that VorpX IS able to pull off (that’s why I said it infuriated me!). Because again, the game window inside VorpX HAS 4860p of detail in it.
-VRAM reading matches 4860p
-Performance matches 4860p
-Visually checking the image by leaning in confirms its 4860p.
And yet… the actual HMD is only rendering at that fixed maxed 2781×3072 resolution, so its absolutely ignoring that headset render target if its being sent. :S

Maybe this is a Virtual Display/Windows issue?
I’m going to try to create a virtual display through other means, and use that instead of the VorpX one, I’ll report back once I do so, but I don’t have much faith in it either.

In any case, I’m almost convinced that if we don’t solve this here… as the next wave of HMDs come in and we start getting over 3000p resolution, people will start complaining, since right now its only affecting high tier HMDs.

[Nisch]

I just checked and ConSim isn’t listed under your profiles. I see:

Ark
Bus Sim
Ranch Sim
Sea of Thieves
Slime Rancher
FS22
Long Dark

[Boblekobold]

I guess most DX9 games (except very beautiful ones like Metro 2033 original) should be Ok. Maybe Dishonored 1 (excellent game), probably F.E.A.R 1 (great AI), Dark Messiah (best sword combat and emergent gameplay), Clive Barker’s Jericho (probably very good in VR), etc.

[Domyos]

Hello, and thank you for your messages.

I’m continuing my exploration of VorpX and adding another video, still with the same difficulty.

I’m playing with the title “The Long Dark” and F0V of “The Long Dark” at max 100, still in Quest 3 on a 11900K and RTX-3090 with a Samsung S27D390H 27-inch screen. I’ve upgraded from VorpX Version 21 to 24.1.0.

https://youtu.be/N7wg-oWNhYo?feature=shared

I’m wondering if I need to launch VorpX Viewer first to play only in VR, or is it not necessary?

See you soon.

[seb22]

Karma the dark world :o) unreal engine 5 !!