Search Results for 'Steam Games'

[Boblekobold]

Concerning Bioshock Infinite, I played it a few years ago on Reverb G2 and I did something else. It probably works with Quest 3.

I don’t say my guide is better, but it was great on G2. It was my first game with VorpX but I think this method is quite simple and reliable.

It’s really easy to get a great result with this game because you don’t even need the virtual Monitor since you can choose any resolution you want, so you should be able to play this game with any VR headset, and even use it to calibrate the best way to configure VorpX to play another game.

There was a DirectVR scan option to autoconfigure the last time I tried (V21) but if you want to configure manually, as I did, I would recommand to :
– adjust the FOV in the .ini files (I used MaxUserFOVOffsetPercent=110 in XUserOptions.ini, but you can probably use a bit more on Quest 3).
– use a very high 4:3 resolution like 3840×2880 (if you can but it shouldn’t be a problem with most PC). You can probably use even higher resolution if you want but this isn’t a very detailed game so 2880p is probably good enough in most cases.

Don’t use the FOV slider in game (at least if you play in full VR), because it’s limited and you probably would have to change the FOV again with the files.

Concerning resolution, you can either :
– use the Virtual Monitor with VorpX v23, V24 or V25 to avoid any problem (launch VorpX desktop Viewer instead of VorpX allow you to really play games with the desired resolution, even in fullscreen mode).
– or you can simply play Windowed, so you can choose any resolution you want, but you’ll have to navigate in the main menu with keyboard instead of mouse.

Don’t forget to adjust Gamma in VorpX, and to use options to enhance image quality (ClarityFX, Sharpness, Texture enhancements in VorpX ingame menu page 2).

I didn’t try to modify the “G3D shadow” parameter on this game (it was my first game with VorpX) but usually it’s better on “auto” (you can try to change it if you experience differences between Z3D and G3D).

I think I had to replace .ini files every time I launched the game (simply reextract an archive you created once).
I may have checked “Don’t Optimize Game settings” but it’s probably not recommanded if you want to auto-configure (it didn’t seem to be a problem if you configure manually but I don’t really know – once again, it was my first game with VorpX a few years ago). This kind of games probably have a lot of automated features, especially if you want to play in 6dof. My method worked well enough to play seated.

But you can probably just load a level and use the DirectVR scan button every time. With my method, changes are permanent and you never have to change anything (except It’s sometimes great to play in immersive screen mode too).

With this method, the game shouldn’t be pixellated at all (at least on G2, because there is no compression), and you shouldn’t have distortions or other problems. It works very well and it’s quite impressive in VR.

You can (and probably should) change font size in the file XUI.ini. Modify value of MaxResolutionUpScale :
https://steamcommunity.com/app/8870/discussions/0/828934723974503663/

I used MaxResolutionUpScale=9.0

Bioshock 1 and especially Bioshock 2 with VorpX are even more beautiful in my opinion :

Bioshock 2 (Fixed crash)

[Ralf]

To a degree your mileage may certainly vary, and as said above, VD may work well in other cases, not so when used with vorpX however unfortunately. Both simply don’t play well together. That’s all.

With vorpX VD introduces wild lag (OpenXR), heavy performance issues in some games, as in FPS almost half of what it should be (OpenXR and SteamVR), upside down controllers since vorpX updated to OpenXR 1.1 (OpenXR) and other minor issues.

I didn’t say VD doesn’t work well in general, I wouldn’t even know that. I can say with certainty though that in case of vorpX Quest Link objectively is the (far) better option. At least half the issues you reported here stem from using VD + vorpX, it takes you only a couple of mouse clicks to fix them right away.

[AlexBlanco]

Hi,

So my main use case for VorpX is to play 3rd person games in stereo 3D using the Cinema display. In this setup by far the best input method for me is my gamepad, with no headset or gesture control at all.

So far, though, it’s really hit or miss as to how easy (or even possible) I find this.
For example, Assassin’s Creed II and Batman: Arkham City both worked really easily whereas I have found GTAV and Batman: Arkham Knight impossible to get up and running, despite tinkering literally for hours.

Is there a comprehensive list of VorpX settings and tips for game-setup for running gamepad-only setups?

In case it helps, my setup is PSVR2 running under SteamVR and I generally use the PS5 Dualsense controller for regular gaming.

Really appreciate any help and input and, judging by the number of posts and things I’ve seen dotted around, I think having all of these tips in one place could be helpful to a lot of people out there.

Thanks,

Alex

[McGuffin]

Thanks Ralf. Tried resetting the game graphics to default – no change. Even deleted the profile and shader folders in users/<user>/Saved Games/kingdomcome to force them to be recreated – no change. Verified game files with steam but still have the issue. There’s a flicker when I switch between 3d off and z-adaptive but both z-buffer modes still look flat with no 3d (3d strength is set to 2.00). Z-Buffer modes are working fine with Fallout 3. Short of reinstalling both game and vorpx not sure what else to try

[333hronos]

Yes, same resolution in both cases (1400×1440), my actual monitor resolution is 4K.

p.s.
I also described some other bugs in v25.1.2 topic, don’t know if you already saw them:

EdgePeek convergence / perspective switch bug (post number 222198)

OpenXR API virtual controllers 3D-model position bug (post number 222199)

OpenXR API Tracking prediction wobbling lag bug (post number 222200)

And another one (which I discovered yesterday)
OpenXR API bug in Hunted: The Demon’s Forge:
The game can’t be injected with OpenXR API, and injects correctly only with SteamVR API.

Also before i managed to make it work, many many times it refuses to inject even with SteamVR, and refuses to create alternative hook (error of extraction somewhat data error). After I changed game version, and after many many tries at last it gives me alternative hook (dll) which works now (I created a backup for that dll in case of any problems with other games in the future), but if I delete hook dll and try to create it, Vorpx refuses to create one again. I don’t know why.

It would be nice, if VorpX can suggest manual DirectX hook dll selection (for example as Reshade installer does).
It would be especially useful in case of games which user know should work correctly, but for some reason doesn’t hooked correctly. (Hunted has RjK G3D profile, it also confirmed on his profile database with his screenshots, so obviously it should work).
I know that it may be wrong (I saw other forum topic when you already discursed that earlier), but in situations when you tried many many times, but game don’t injecting, and hook doesn’t creates automatically it should be a alternate bypass route.

p.p.s.
I also want to thank you for all your hard work, because despite some little bugs, VorpX works just flawless in such games as Outlast with FullVR/DirectVR mode, and in Hunted: The Demon’s Forge with FullVR G3D mode, providing real VR experience.

[JDogDaBoy]

I used to be able to play Black Ops 2 and Black Ops 3 in full VR mode using a meta Quest 2, virtual desktop, and running it as open XR. Now for whatever reason anytime I try to run a game it says open XR creation instance failed. So I’ve tried other methods like steamvr or running the meta Quest link runtime and what that does is brings me into a space like when loading into steamvr. Then it shows a man with a VR headset on and a question mark and the game window is very small on the bottom left. I’ve tried disabling a bunch of different overlays, turning off and on Hags, checking antivirus and everything. I’ve been having this issue for about a month or two now. But I had vorpex for almost a year prior to this issue and was able to play all of my games with no problems. If I could get any insight as to what’s causing this or what I’m doing wrong I would appreciate it!

[dimensionaldude]

I’m on the Pimax Crystal Super trying to use the Desktop Viewer / Virtual Monitor, but am having a couple problems:

-While it works, the resolution is clearly reduced. On a 4k desktop, it looks like it’s downsampled using a nearest neighbor filter down to maybe 1080 (I can see obvious aliasing on straight lines). It’s clearly displaying a poorer quality than something like SteamVR’s desktop view, I’m guessing this is some sort of bug.

-I’m on a 60Hz monitor and I can’t get Desktop Viewer to display the image at 90fps, even with vsync off in games with a high framerate. The in-game framerate will go that high, but the Desktop Viewer isn’t sampling it, it looks identical to capping it at 60 and I can tell it’s not as smooth as 90. Just to test, capping it at 30fps shows an obvious drop, so I think it’s not injecting properly.

Some things I’ve tried / noticed:

-When VorpX hooks into a game directly, it displays it at 90fps fine (same for full resolution), this is only an issue for running a game inside Desktop Viewer.

-When I try to launch Desktop Viewer through the system tray icon, nothing happens, but if I launch vorpDesktop.exe directly from the VorpX directory, then it will load.

-When trying to activate virtual monitor manually from the system tray, nothing seems to change. If it’s already running Desktop Viewer, does that mean it’s already active?

[Seph Swain]

Hi all!

This is how I start my game since version 25 (24):
– wake up PC
– use mouse and monitor to:
– start VorpX (it doesn’t survive the sleep mode)
– start Virtual Desktop manager
– put on headset (with mouse on my lap)
– Desktop Viewer kicks in and turns on Virtual Monitor
– change resolution (from “recommended” to my desired resolution)
– get the Steam window on the virtual monitor
– start game
– store away mouse and pick up gamepad

Is there a chance to shortcut / automate some part of this routine or make it more comfortable?
How do you guys do it?

Can I eg. make the VorpX control survive the sleep or start the virtual monitor in the desired resolution?

Cheers!

[Boblekobold]

Great news !
Did you try with “SteamVR” or “OpenXR” in “Device Selection” ?

Note you can still use WMR + OpenXR with Windows 11 as long as you don’t update too much (23h2 should be fine).
It is very optimized and reliable, never freezes, and works with 32 bit games. I don’t know exactly what Oasis can do and if it’s as optimized as WMR but I guess it’s SteamVR only (according to the description, you can use OpenXR, but probably only the SteamVR’s version, so it may not always work as intended, especially with 32 bit games – In this case you’ll probably have to use “SteamVR” option). I may be wrong since I didn’t try yet (I would prefer to keep using WMR but I’m glad we have another option now). Let’s hope it will keep working as long as we need to.

[Ralf]

If you happen to use SteamVR as your OpenXR runtime, configure vorpX to use SteamVR directly instead.

Valve’s OpenXR implementation is not only outdated (i.e. doesn’t support the latest OpenXR version). It also, spec violation one, has no 32-bit support for older games. And, just as bad, messes up two OpenXR functions, spec violation two, that are used to snychronize frame timing in more complex multithreaded environments, causing severe FPS drops with vorpX compared to working OpenXR implementations or using SteamVR directly.

They ignore reports from several devs in both regards since several years, so they probably won’t fix any of that.

TLDR: Valve’s OpenXR objectively sucks. Do not use.

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

[Nukeboyt]

I am having one heck of a time getting this to run. Fixed the Nvidia driver issue (thanks). Can get it to run on my Quest only via Steam Link with Valve Index selected in Config. When I choose Quest and run game via Quest Link, it errors out saying it cannot detect Quest Headset, Same for if I choose OpenXR and run via Quest Link or Virtual Desktop. Any help suggestions would be appreciated! All other games from Meta Link or Virtual Desktop launch just fine. I must be doing something wrong. Edit: I sent several of the crash reports withing an hour or so prior to this message (≈ 1400 CDT)

[abeardedpirate]

Have a PSVR 2. Installed the free mod to see what this is about.
In settings selected SteamVR since PSVR is using SteamVR app.
Launch game. SteamVR never brings up the game. Can see game if going to desktop mode or theater mode.
While game is open no inputs work. No keyboard inputs, no gamepad inputs, no inputs from my PSVR2 controllers.

I have uninstalled the mod, the game, fresh reboot, installed the game, rebooted, installed the free mod, fresh rebooted again and everything in between. The game will never register inputs. My keyboard does work as I can press Windows Key and get the start menu up to do other things. I can also hit the PS home key to bring up steam interface so I know my buttons work but they are not registering with Cyberpunk itself.

I uninstalled the mod and selected default on every setting inside of cyberpunk 2077 before rebooting and reinstalling the mod just to make sure everything is good. Since there is 0 interface with the free mod the only way I can get the VR selector up (Steam / Meta / Other) is to just reinstall the mod again.

I’ve launched Cyberpunk 2077 letting it open Steam VR and I’ve launched Steam VR and then opened Cyberpunk with no luck.

I went on Steam settings and have enabled steam input override for Cyberpunk 2077. I’ve tried it disabled and enabled same issue both ways.

I’m on an i9900k with a 2080ti with the PSVR2 plugged directly into my 2080ti. I haven’t had issues with other actual VR games/programs but I can’t make this work. Nothing seems to do anything. Delete / left button + right button / and L3 or w/e gamepad is nothing brings up any settings like the mod installer says it does.

Any help would be appreciated cause I feel like I’ve exhausted all the troubleshooting steps I’ve seen on this forum at this point.

[Ralf]

Frankly I can’t even really imagine how a driver update could cause such an issue. vorpX captures the game output before it is sent to the driver and sending the final image to the headset later works through the VR APIs (Meta/SteamVR/OpenXR) like in any other VR app. Not a single point in that pipeline touches the graphics driver directly. Very, very weird.

Either way, since for me 580.88 works fine, so that I can’t replicate your issue, all I can recommend is:

1. Trying all three VR APIs in the config app, a Quest should work with all of them.
2. Using a driver version that is working for you.
3. In case this is related to a gaming laptop, try to disable the integrated GPU to ensure that games run on the same GPU that the headset is connected to, which usually is the dedicated GPU in a gaming laptop.

If you want, you can create a trouble shoot archive with log files and system infos in the config app and send it to support at vorpx com. Probably won’t show anything useful, but can’t hurt to look at it.

[Boblekobold]

Parenthesis : Even without any bug, I don’t think it’s possible to use full potential of a 8k VR headset (especially with SteamVR). It’s probably not useful to most people anyway.

There are a lot of recent games which are a lot more detailed and beautiful in 3840p (5120×3840) than 3200p with VorpX on my G2, even if it’s a 2160p VR headset. It’s probably because the details you can display with a 2160p VR headset in certain games aren’t computed without supersampling (at 3840p, I never tried more).

I may be wrong, but this kind of 8k VR headset are great to get “perfect” PPD if you have a perfect sight, but only with very old (or not demanding at all) games.

In my opinion, most old games, even beautiful ones, are already great in 2880p (in my G2) because there is a limit due to the textures of the games. You can already perfectly see the defaults of the game itself, even if VorpX enhances graphics a lot. I only used 3200 and 3840p with very detailed games like Metro Exodus, Atomic Heart, etc.

Considering 8k VR headset may be more demanding than a Reverb G2 (WMR/OpenXR/2160p), it could require a better graphic card than my RTX4090 to achieve the same result in some cases.

I think a 2880p VR headset like Pimax Crystal Light has already too much resolution in most cases. Some youtubers with RTX4090 seems to prefer G2 over Crystal Light on a same game, even to use UEVR, for example. There must be a reason.

Note : a VR headset with higher FOV may require more resolution to achieve the same result so it has to be taken in consideration here.