-
Search Results
-
Topic: Game can’t handle ultrawide
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.
In reply to: vorpX 25.1.5 Available Now
Happy to report that the latest update made everything look better! At least with my Pimax headsets there has been some problems (aliasing and such) and now it is gone. Also the expert setting that allows user to choose the sampling setting is great, can fix some problems with high sharpening and lower resolutions (patterns on uniformly colored areas, sky etc, choosing linear fixes those, bicubic seems too ‘soft’).
In reply to: vorpX 25.1.5 Available Now
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.
In reply to: Image zoom setting
@inn1950 : If you want to avoid the black area while displaying the entire view, don’t use a 16:9 resolution if your VR headset isn’t 16:9. Usually 4:3 is better (it depends on the VR headsset).
You can choose a very high 4:3 (2880×2160 minimum for full VR) or “1:1” resolution with the Virtual Monitor (Vorpx Desktop Viewer).
OF course the game must allow this resolution but it’s usually not a problem.Topic: problems with some old games
Hi, I get black screen in those games.
Trails in the sky 1
Trails of cold steel 1
Spider-man shattered dimensions
Harry potter half blood prince.
You can hear the audio in the headset and the game works fine in the pc screen.
All the other games I played worked fine.
I have intel core 7 with a nvidia 5070.
I hope someone can help me.In reply to: Image zoom setting
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.
In reply to: PSVR2 + RX 6900XT – VorpX Crashes on any game
Tested again with a timer: timeouts occur exactly 90 seconds after utilizing the program, whether in Desktop mode or in Gaming mode.
There is also a non optional Overlay that the PS/VR2 imposes, namely the psvr2 overlay to be able to sue the motion controllers. This is impossible to turn off, so I suspect any other users with a PS/VR2 will either have the same issue, or have it running without issues, suggesting it can’t be a problem.
I don’t know how many people you have with a VR2, but it’s a bit of info.
In reply to: PSVR2 + RX 6900XT – VorpX Crashes on any game
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 OverlayAll 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.
In reply to: PSVR2 + RX 6900XT – VorpX Crashes on any game
Please first try with only SteamVR, exit Virtual Desktop. Also make sure to select SteamVR in the vorpX config app, not OpenXR. Valve’s OpenXR misses 32-bit support for older games and on top of that is broken in regard to a function that is important in multithreaded rendering pipelines like vorpX’s.
If that does not help, check whether something is running on your PC that also hooks into games. Issues like this almost certainly are caused by another app getting in the way.
The trouble shooting guide in the vorpX help (altenatively pinned to the top of this sub forum) has more details.
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.2I’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.
In reply to: The crosshair is higher than it should be on Quest 3
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!
In reply to: The crosshair is higher than it should be on Quest 3
Everything in order. That’s how basically all VR headsets work, in native VR games too. Some more than others.
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.
Topic: Godot support?
Would this be possible, still a niche engine at the moment if you look at 3d games but I see more games using this. Mainly currently asking because Road To Vostok switched to Godot from Unity.
In reply to: Jurassic Park: Evolution 2
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.
