Search Results for 'Fe'

[Cer]

Updated today and tryied Desktop Viewer + Virtual Monitor.
Found that it doesn’t work as expected and returned to play without virtual monitor.

Issue:
Playing with HP Reverb G2. Virtual Monitor suggest default resolution of 2560×1440 (which is for some reson default), but I changed it to 3440×1440 as I want to play with 21:10 so I can turn my head a bit without seeing the edge.

I started Ratched&Clank Rift Apart and got a condesed picture. The screen is 3440 wide, but I had black vertical bars left and right. The visible picture is probably 2560 wide, but contains all 3440 pixels, which looked ugly. In addition the tilt settings of the screen didn’t seem to have an effect.
This issue stayed even after switching of virtual monitor by using “Enable virtual monitor” option of the icon in the tray (why is it called “Enable” when it switches off??). Anyway, games played on my main real monitor, but picture was still bad.

Then I disabled virtual monitor in the VorpX Config, restarted VorpX and could play again with full 3440×1440 resolution and correct screen tilt.

Hope you understood what I am writing here and can fix this issue so I can use virtual monitor.

[Ralf]

Clearly not normal. Without raytracing your GPU should do quite well.

There is a fresh build linked in the original post of this thread. If you still encounter performance issues with the default 3D method, you can now safely switch to Z3D again in the menu, which was broken in some (many) cases before.

[Ralf]

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.

[vrenjoyer1]

Hello,

I’m trying to get vorpx to run games on a HP Reverb G2. At first I tried to play Half-Life 2 using SteamVR but it didn’t work very well. The actual game screen appeared small in the distance, although it rendered there in stereo 3d. Once the game started it glitched out and frame rate dropped so bad I could barely move the mouse. Then I read that SteamVR is not advised for WMR headsets. But how does everything work now in the Oasis era? Will OpenXR, which I found out is the recommended method work still? Do I need to download it from somewhere, or is it included in windows?

I tried to change settings in vorpx to openxr and launch Fallout 3, but the headset doesn’t even turn on. Has anyone tried to get the Reverb G2 to work with vorpx with the Oasis driver?

Thanks for the help!

[Ralf]

First please make sure to exit *ALL* programs running in the background. Especially any third party antivirus applications. Switch to Windows Defender instead. Also everything that may potentially hook into games. That includes any form of GPU/CPU utility or vendor bloatware that might have come with your PC.

If that does not help:

Please create a trouble shhot data archive in the config app and send it to support at vorpx dot com.

[Ralf]

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.

[Ralf]

When you lower the image zoom setting, you get black bars above and below the image. That’s how the zoom works. Alternatively you can instead set an ambience colored background after clicking on ‘More FullVR settings’ in the menu if you prefer that.

The black area below the image is a bit larger than above since VR headsets use an asymmetric view frustum where more pixels are shown below the eye than above to have more precious pixels where it counts. A neat optimization that factors in human vision, which focuses more on things below your eyes than above in the sky. Since the the game was rendered with its usual symmectric frustum, you end up with more space below than above the image when you zoom out.

[Demu]

I have tried with both SteamVR and OpenXR, tried the latter when SteamVR failed.

I have checked and removed other overlays, including those of AMD drivers themselves. GameBar is also functionally cut out of my Windows install with a Debloater.

The options were:

– Rivatuner from MSI Afterburner
– Wallpaper Engine
– AMD Overlay
– Discord Overlay
– Lossless Scaling
– Game Bar
– Browser
– HWINFO (reads sensors for system, I figure safe bet to shut down)
– Windows PowerToys (has overlay componets that are turned off).
– Steam Overlay

All of these have been disabled for the test as you asked. I inspected Task Manager for any processes that may be related, found none.

VorpX is allowed to turn off overlays and runs in admin mode. Alternative hook method has been tried to no effect, so it’s turned off again.

I checked again and the app just crashes on the virtual desktop too, after the same amount of time. I had been using it to launch games so didn’t test the obvious scenario of leaving it running.

The desktop mode is thus also a bust.

The in-app troubleshooter was read back to front before I came to the forums: Googling also didn’t show any similar results to mine.

FAQ above was read.

Tested with just SteamVR and Left 4 Dead 2, crash behaviour is _identical_: Crashes about 2-3 minutes in. Seems to last the exact same amount of time before crashing each time, suggesting a timeout somewhere.

If it’s helpful I can roll back drivers to last year or something similar.

Hope this helps.

[Demu]

OS: Windows 10 latest with ESU
AMD driver: 25.10.3 – 25.12.1
GPU: XFX RX 6900XT (Both OC and non OC tested)
CPU: 9800X3D
RAM: 32GB DDR5-6000
Module: SteamVR – OpenXR
Headset: PS/VR2 with PC adapter – Displayport connection.
VorpX: 25.1.2

I’ve noticed that the app is constantly crashing when using VorpX on any game. Tested Fallout 4, Cyberpunk, Stalker Anomaly, Left 4 Dead 2, Ghost Recon Wildlands, Factorio, 15+ others.

The Virtual desktop starts fine and works fine(usually, sometimes VorPX will attempt to hook vorpDesktop and timeout), until the moment I try to actually play a game. Game will usually start, but inevitably crash after less than 5 minutes. SteamVR reports ‘ IPC Namespace Unavailable ‘ and AMD driver reports that the driver has crashed. Notably, the driver crashes to the Virtual Desktop and in rare cases, crashes out of the VR experience outright.

This happens only with VorpX. SteamVR home works fine, mods for Cyberpunk like RealVR work great, so it’s a very specific VorpX problem with the headset.

Effectively this appears to make the software completely unusable under Windows 10 at this moment.

Hope this helps you ascertain the issue Ralf. I can provide additional info and tests if you need them, to hopefully help you get some more customers for the software.

[Ralf]

Super weird, provided things are actually off-center on your Q3, which is hard to tell from just photos. vorpX doesn’t do anything different on Q3 than it does on Q2, so if there is an actual problem, it almost certainly is something else.

[Ralf]

The game camera center has to be where the headset expects it to be in FullVR mode obviously. Otherwise you get image distortion in motion. vorpX just makes sure that both match, there is no margin for error (or adjustment) here.

Maybe something else is wrong, hard to tell. The way vorpX aligns the game camera to the headset frustum clearly isn’t. Considering that things work for you as you expect on Q2 but not on Q3 makes this even more weird. As you can probably imagine Q3 is the main dev headset here since quite a while and also commonly used by others.

Just in case you haven’t done that already try this:

• Switch to a different VR runtime in the vorpX config app, ideally use native Quest Link to minimize potential external factors.
• Recalibrate your play space.
• Recenter headtracking in vorpX (ALT+SPACE).

[kerekeslaszlo]

I understand that this is beneficial in normal VR games, but in VorpX it’s extremely distracting.
I’ve been trying to solve this issue for 5 days now, but nothing has worked.

What I’ve tried so far:

All settings that are in vorpx

Quest 3 settings “lying down mode”

ALVR + SteamVR + lying down mode

Virtual Desktop

OpenVR-AdvancedSettings + SteamVR

Unfortunately, none of these could lower the screen offset enough to get the crosshair centered.
It seems that in VorpX Full VR mode the screen attachment to the camera is hard-coded, so no external offset can modify it.

I’m running out of ideas at this point.

If you could add a screen height adjustment option in Full VR mode in a future update, that would perfectly solve the problem.

Thank you!

[Boblekobold]

In case it helps sometimes, you can probably manually create/edit a shortcut by editing the target to something like that :
“C:\Program Files (x86)\Animation Labs\vorpX\vorpControl.exe” “C:\Program Files\Epic Games\JWE2\JWE2.exe”
However It could not work if the launcher prevents you to directly launch the executable.

Concerning Game Pass / Xbox app, you can use “add process” instead of “add file“. It worked for me with different games but If this game needs a direct shortcut, it may not help. Sometimes you have to exclude the launcher, but it still doesn’t allow you to use the direct shortcut if this game can’t be directly launched.

The questions are :
– is there a way to directly launch a Steam / Xbox game ?
– why some games require a direct shortcut (It seems to happen with unofficial profiles sometimes) and is there another way to hook them ?

[ClownRazer]

Well. I’ve tried on and off over the last few months. Followed everything I can in your (and others) descriptions and still can’t get it to hook. Only difference left is that I don’t have the epic version, I have both the XBOX and Steam version. The xbox has a different executable Galileo.final.exe and it’s locked down enough that even the VorpX “create desktop shortcut” barfs when I try to choose that EXE, so if you’re reading this and trying the XBOX version, probably quit.

The steam version allows creation of the shortcut and starts the game, but I can’t get it to hook using any attempted combination of: hook helper, alternative hooking, run as admin, etc. Tried with Dellrifters JWE1 profile and the recently added (since this thread started) JWE2 profile by Vincer2000.

If anyone has any success other than Boblekobold please tell me your config and situation. Might just have to go spring for the Epic version to see if that is the difference.

[Boblekobold]

Je compte le faire en VorpX mais je n’ai pas encore essayé. J’avais testé le premier et il fonctionnait bien (avec la v24.1). Par contre il faut sans doute une bonne carte, surtout avec un Quest 3 qui n’est pas le top en terme d’optimisation. Perso j’ai une RTX4090 et j’avais installé un mod de LOD qui boostait les graphismes à fond en affichant tout sur une distance infinie. C’était impressionnant mais ça tuait les performances (sans ça il tournait nickel en 3840p).

Est-ce que tu as de la marge pour te permettre de lancer le jeu en VR ? Que ce soit en VRAM ou même déjà au niveau du framerate ? Sachant qu’en full VR on joue souvent en 2160p à 3840p pour un bon rendu. Essaye de le lancer dans une basse résolution genre 1080p en mode cinéma pour commencer. Evite le DLSS, au moins au début (jamais vu l’intérêt en VR, en tout cas avec un G2, mais j’utilise parfois le FSR en qualité max quand je suis obligé). Les autres options ne causent généralement pas de problèmes du moment que tu as la puissance requise. Assures-toi que tu hook bien. Ensuite, vérifie que tu as bien la 3D. Et enfin règle la résolution (4:3 – 2880×2160 minimum pour le full VR), le FOV (112° environ mais tu peux mettre plus si tu supportes les distorsions), le Zoom en dernier (puis la vitesse de headtracking au besoin), le ClarityFX (pour améliorer l’image), Sharpness (pareil), etc.

Tu as choisis quel profil ? J’imagine qu’il faut utiliser celui du premier jeu, mais que tu dois l’attacher manuellement (sauf s’il y a un profil sur le Cloud). Vérifie dans l’écran d’acceuil que le profil a hooké. Il y a des méthodes de hook alternatives, la possibilité de mettre un hook helper. Parfois ça aide de créer un raccourci direct (clic droit sur VorpX puis tu choisis l’executable du jeu et il apparaitra sur le bureau) plutôt que de lancer VorpX puis le jeu.
La G3D ne va pas fonctionner comme sur le premier parce que la suite est en DX12 mais la Z3D devrait marcher (sauf si la dernière version de VorpX a cassé quelque chose comme suggéré dans un autre topic, mais dans ce cas ce sera sûrement réglé à un moment ou à un autre).

Il y a plusieurs vidéos sur youtube qui indiquent que ça marche bien, avec des conseils (mais il faut lire les commentaires en dessous car tous les conseils ne sont pas optimaux du fait que le youtuber faisait ses premiers pas avec VorpX donc il a fait quelques erreurs).

Généralement je joue en 4:3 personnellement. Tu utilises le moniteur virtuel ? (Vorpx Destkop Viewer)
Commence déjà par hooker normalement avec la résolution de ton écran, sans moniteur virtuel, et lorsque ça marchera tu essayeras de régler la bonne résolution (de préférence une très haute résolution 4:3).

Quand ça ne marche pas, il faut faire simple et y aller progressivement. L’important, c’est de hooker (en tout cas si tu veux la 3D), puis de faire tes réglages (mais pour ces derniers ça vient tout seul car ce sont les mêmes dans tous les jeux, à peu de choses près).

Tu as des tutos en français aussi sur divers sites connus.

———————————-<English>———————————-

Too tired to translate ;)
The first step is to make sure you hook (there are other topics and youtube videos about that).