Search Results for 'sbs'

[onetoo]

Factory Reset did not work for me. I performed a clean install of VorpX after manually deleting leftover folders and registry entries. I also uninstalled Meta Horizon Link and only reinstalled it after installing VorpX and getting it to run with Steam Link.

I added
sDeviceIniName=SteamVR
to C:\ProgramData\Animation Labs\vorpX\vorpX.ini, which made VorpX work with Steam Link. This did not work when I tried it before the clean install.

Switching back to
sDeviceIniName=oculus
allowed Meta Horizon Link to function again.

I also tested OpenXR and Generic3DDisplay in the vorpX.ini file, but both resulted in a side-by-side (SBS) 3D image formatted for VR.

Selecting devices from the Devices menu in the VorpX Config does not modify the vorpX.ini file or affect which runtime is used. The only method that works is manually switching between the two functional runtime entries in vorpX.ini. I also tried running as administrator, with the same results.

When using Meta Horizon Link with vorpX and the vorpX.ini is set to SteamVR, the game launches and works in OpenVR, but errors appear that do not occur when using Steam Link.

Error Box 1: Missing interface
INTERFACE = SteamSteamVRPrivate002
CALLER FN = Steam_NotifyMissingInterface()
APPID = 534380
TIME = 2026/04/18 – 03:04:58

Error Box 2: Missing interface
INTERFACE = SteamSteamVRPrivate001
CALLER FN = Steam_NotifyMissingInterface()
APPID = 534380
TIME = 2026/04/18 – 03:06:59

Anyway, I got Steam Link working with SteamVR, which was my initial and primary goal.

[onetoo]

I spoke too soon. It’s not a workaround. There’s the image is reduced to an oval as if it’s formatted for and it has the gesture instructions in the view. I just got some sleep after seeing the SBS image and didn’t notice. The controller interacts with the game in the background, but doesn’t remove the gesture instructions. Yeah, I hit apply in save dozens of times. I put the .ini back, and the demand for a Quest Link Headset is back when trying to use Generic 3D Display.

[onetoo]

Solution: I deleted “C:\ProgramData\Animation Labs\vorpX\Devices\Display\Oculus.ini” and Meta was removed as an option from the device selection list. Now I can see an SBS image without a VR device attached when Generic 3D Display is selected as the device.

[onetoo]

I tried to use Generic SBS Display for my projector, and I still get the same message asking for a Quest headset. I uninstalled Meta Horizon Link and I still get the message. Factory resetting the profile for any game didn’t help.

[Boblekobold]

I’m testing Generic 3D Display with a 3D glasses-free monitor (I prefer VR, but you can’t wear a VR headset all the time and I was really curious about this new technology)

I didn’t find a way to directly activate the 3D of the monitor (I guess I would need something like a “Simulated Reality” Device Selection option) so I had to use Shaderglass on top of VorpX with 3DGameBridge (Reshade Add-On) in order to display 3D (instead of the SBS output). So far I can’t play fullscreen so if the game doesn’t have a “borderless windowed” mode I have to hide the system bar with another program.

It works great in G3D but so far I get no Z3D with tested games (Bioshock 2, Atomic Heart).

Is it intended ?

(Note : I’m still using V24)

[BerZerker96 ph]

also from my testing , using stero mods like geo 11 and super depth Horizontal interlaced , also called line interlaces offers much more detail and a much better resloution that sbs and tab , higly reccomend you try it , and if possible adding it as an option

[Ralf]

Just a heads-up that i went the extra mile and spent two full days to come up with an auto SBS detection that continuously analyses the image content and decides whether it’s SBS 3D or not.

After quite a bit of fiddling around it’s now super reliable even in difficult edge cases with all 3D movies I checked. Should also work fine with S3D games usually. The only situation where I could potentially imagine it to fall apart is when cranking up 3D too much in a S3D game.

Not quite sure yet whether I’ll turn that on per default in desktop viewer since there is a small remaining risk of false positives. So more testing is required before deciding that. If not, you’ll be able to switch it on in the vorpX menu.

[J0hnnieW4lker]

just fixed it changing the output to sbs, tks

[Cer]

Strange, my post is not there anymore.
Advice was to use such games with VorpX desktop viewer in SBS mode.

[Cer]

using headtracking with Immersive Screen also provides you more range to look around you.

Yes, that is what I do. But picture moves only a bit, I think I have factor 0.5. By moving the head a bit I see more of the game but still don’t see the left and right edge in wide imersive screen mode.

In my opinion, VorpX isn’t meant to simply be a giant 3D monitor. When the game’s design has a good compatibility with VR (3D engine, not too much UI or not at the edge of the screen, high FOV available, first person or third person very close to it), it’s magic ;)

Yes, but is a very good 2nd use which I use more often than the 1st use case.

You probably know it, but you can hook with the Virtual Monitor (at least with the right version of VorpX like V23, V24 and V25) if the game has a profile. VorpX should create a default profile if there is not.

Correct, but there is no official profile and the user made one doesn’t give any 3D effect. No idead why, as DirectX12 game it should work with Z3D, but it looks flat regardless what settings I tweaked. Hence I use VorpX as giant screen in SBS mode, which gives a perfect 3D picture.

A solution may be to :
– configure the game in windowed mode (so it won’t have any reason to use the default res or the physical monitor resolution).

Tried this, didn’t made a difference. Hence I initialy thought it must be a virtual monitor issue.

I used this method on Metro 2033 (Original) to get 3840×2880 resolution with 4:3 ratio.

I am not sure if a resolution higher that the headset resolution will have any benefit. At least you need a system that can handle this or will have to downgrade some grafic options. But here we go off topic.

[Greg]

Since updating to vorpX 25.x (25.1.3 / 25.1.3.1), ESO64.exe no longer works.

Auto-attach crashes ESO before splash
-Late attach (“Trying to attach”) never succeeds
-Hook helper / alternate hooking / window modes do not help
-Same system, same settings works immediately in vorpX 24.1.2

Setup:
-Windows 11
-AMD GPU
-No HMD (3DTV / SBS output)
-Virtual monitor disabled
-Hyper-V / VBS fully disabled (incl. BIOS SVM)

This appears to be a regression related to earlier VR-centric injection in 25.x?

[CrunchyGlass]

If the game is already split into 3D SBS with another tool, you can just run Vorpx desktop viewer in SBS mode (through settings) and pause the watcher.

[Ralf]

That’s the two options you have. Either using the desktop viewer and exclude the .exe or creating your own profile from the SBS base profile. If the latter works without the other app actually creating a conflict, you can simply ignore the warning. Be aware though that using two fairly deep D3D hooks at the same time in a game is basically asking for trouble.

You probably tried the third potential option, so just in case, since you didn’t mention it: you could also try to create a Z3D profile based on the TLOU 1 profile. The Uncharted profile might also be worth a shot for that.

[MarcDwonn]

I upgraded yesterday to the latest version (from v21.xx), and i’m loving the new Desktop Viewer’s performance and syncing. Great work, Ralf! With the impending Steam Frame, i can see myself spending much time again with this software, that’s been my “main driver” for so many years in the past.

Could use a bit of help though: I’m trying to get “The Last Of Us Part 2” running with VorpX, but can’t find a profile, so i followed your advice to make a copy of the generic SBS profile and run the game with that.

I’m using a tool that translates the game into a stereo3D SBS stream which i’m trying to play with VorpX, but VorpX tries to hook into the game and finds the extra DLL of this tool, and nothing works.

Workaround was to *exclude* the game EXE from VorpX watcher. Start VorpX Desktop, then from there start the game. VorpX is still giving me warning messages about a foreign DLL found, but at least it’s working, and the performance is good.

What’s the best way to approach this and minimize the friction and potential errors? It’s very umständlich atm. :)

[Buzbee]

I have tried a few emulators that have support/plugins for sbs/ou which can be used with the vorpx desktop viewer.

Rpcs3 – PS3 (games with 3D support only)
Citra – 3DS games
Dolphin – GameCube

I have also heard of

PCSX-Reloaded – pS1 games
PCSX2 – ps2 games

Are there any others?

Would anyone like to do a quick set-up tutorial for any of the emulators for 2025?

PCSX2 no longer does plugins so it could use an update with current version.