Search Results for 'Steam Games'

[Ralf]

That means that vorpX couldn’t initialize the VR headset, which is a fairly severe issue. Most likely something is messed up on your system.

You *might* be able to deal with that by selecting a different headset type in the vorpX config app.

If e.g. you are using a Quest and currently have selected SteamVR/OpenXR, try native Meta Link instead. Most headsets should work with SteamVR, Meta headsets work best with Meta Horizon Link.

—

Sidenote in case you happen to use OpenXR while SteamVR is set as your system’s OpenXR runtime: Valve knowingly violates the OpenXR spec by not providing a 32 bit version of their OpenXR implementation. So Valve’s OpenXR cannot work with older 32 bit games.

[GreenThumbFoodie]

Just wanted to say thank you Ralf. I’m a first time user with a backlog of so many games. I wanted to find a reliable way to port games to VR that are not using the UEVR model. I had a slight hiccup yesterday so today I followed your tech support suggestions: turn off Steam Overlay (inc FPS counter), wallpaper engine, nvidia app, and others. It hooked and now I’m in the Himalayas enjoying FarCry 4 in VR. I can already tell that the image rendering is way better than other mods for this game (the one that recently was removed).

Specs:
Far Cry 4
16:9
2560×1440

Vorpx set at standard profile. I can’t believe I can even play in the VR controller!!!

Pimax Crystal Light
Steam Frame set at 50% per eye (still plenty)

PC
7800X3D, 5070TI, 64 GB DDRA5 RAM

Well, I’m excited to play my backlog in VR now.

[diamonddust]

Hi, from memory I think I did get it working but I haven’t used it for a while so it may not be working still. As I said originally just renaming the dx12 file didn’t work. You have to make a new file, tell steam to launch using that file, then make a new profile on vorpx using that file.

I copied the F1_2020_dx12.exe and renamed it to F1vorpx.exe (or something like that), then in the game’s properties on steam, I added the address of the new .exe file in quotation marks to the launch option modification line followed by %command%. I think I also changed the “selected launch option” so that it runs in dx12 by default (99% sure – otherwise it was run in dx11 but that doesn’t make sense to me).

So in the launch option modification field you should have something like:

“C:\..[wherever your games are installed]..\steamapps\common\F1 2020\F1vorpx.exe[or whatever you name it]” %command%

Then in the vorpx I made a new profile which I’m pretty sure was based on the F1 2021 profile (again I think – otherwise it might have been based on the F1 2020 profile) and assigned the new F1vorpx.exe program to it.

Let me know how you get on :)

[loonygeekfun]

OMG It works!

Playing in VR with immersive screen on means I can play VR seated and because I can use my quest controllers to emulate a Gamepad, I no longer get cramp from having to grip a game pad. I wonder if this means I can play traditional Gamepad games through the desktop app that vorpx has but use my quest controllers?

I’m so glad that I got Dishonored 2 and this game on the steam sale

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

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

[Ralf]

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.

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

[Boblekobold]

When you download a profile in the Cloud Profiles section, there are instructions next to it (you can also see them by clicking “Edit Profile Properties” even in the Local Profiles section)
Concerning this game, it should tell you how to change the FOV with the console for example.

Anyway, you can usually find this information here for most games :
https://www.pcgamingwiki.com/wiki/Kingdom_Come:_Deliverance_II#Field_of_view_.28FOV.29

Or on Reddit / Steam forums.

—-

Concerning KCD2 :

But as I said, read the comments below this first video because it’s not optimal.
Update by the same person :

Another topic :
https://www.vorpx.com/forums/topic/kingdom-come-deliverance-2-2/
So you should use the Auryza profile (or maybe Starfield) and not the KCD1 profile. You may have to rename the executable in order to make sure VorpX hook with this profile, instead of using first game profile (because apparently they have the same .exe name so VorpX thinks KCD2 is KCD1)

[TheGreatGarbanzo]

Out of curiosity, anyone out there using Vorpx immersive screen mode with an Apple Vision Pro & ALVR?

I typically game on my Quest 3 w/Steam Link / Virtual Desktop… but I’m thinking pancake games would look stunning in stereoscopic 3d on the AVP.

[Ralf]

1. You have to run games at the resolution you want them to run, i.e. change the resolution in the game options accordingly. vorpX does not automatically render games at the resolution you set in SteamVR, The resolution set in the game options is the only thing you have to care about.
2. If after setting the game resolution high enough you still get a pixelated image, the issue is caused by the Pimax software after vorpX hands the image over to SteamVR. This is not an issue on vorpX’s end. There is no, and never has been a ‘low resolution bug’. What I’m getting from this thread here is that the issue might be related to Pimax’s fixed foveated rendering, which should be turned off.
3. If that still doesn’t help, ask Pimax what the heck they are doing.

[Marozaki]

I’m using AirLink or SteamLink for MetaQuest 3, but after about 5 minutes the left and right images start to get out of sync, freeze, and move up
and down.
This happened with both the standalone version and the retail version, and it was the same even when I changed the image quality.
Ray tracing is turned off in the in-game settings, and the FPS is high on the flat version.
The refresh rate is 72MHz for both MetaQuest 3 and SteamVR.
The wireless connection is Wi-fi 6, but I don’t have a wired connection or virtual desktop so I haven’t tried it.
I recently upgraded to an AMD RX9070 and started playing Cyberpunk VR again, but I can only play for 5 minutes at a time.
Previously, I was able to play without any problems with Valve Index and AMD RX6800, but since I switched to MetaQuest 3 which has high resolution, I would like to play at ultra resolution.
When I check the SteamVR performance graph, I occasionally see purple lines indicating display errors and light blue lines indicating network latency, but I don’t experience any lag or freezes in other games.
If anyone has experienced similar symptoms, or knows the cause or how to resolve it, I would really appreciate some advice.

Translated by Google.
From a VorpX fan in Japan.

[Ralf]

Unfortunately there is no single answer to that question since games use different metrics for their FOV calculations. Some use the vertical FOV (which makes most sense), some the horizontal FOV, some use a wrong but fairly common naive vertical to horizontal calculation, some use offsets from some unknown base value or even made up fantasy values. Over the years the number of formulas in profiles where vorpX can calculate the FOV automatically has reached about a dozen…

That said:

For vorpX at default, i.e. with its ImageZoom setting at 1.0, the actual vertical! FOV you want in a game is always 96°, no matter what headset you use. That’s done to keep profiles and potential instructions from profile authors easily interchangeable.

Most modern headsets however can display a bit more if you want. The actual vertical FOV your headset needs with vorpX’s ImageZoom setting maxed out can be found in the vorpX log file in a line like ‘SteamVRDevice: FOV: 103.000000°’ or so. Might also be ‘OculusRiftDevice’ or ‘OpenXRDevice’ depending on your headset type.

That’s only the first step though. From there you need to figure out how the game in question actually handles its FOV calculation, which, as described above, differs heavily from game to game.

You can check the vorpX log file by creating a trouble shoot archive in the config app.

—

BTW: The values from comparison sites on the internet are uselesss for your purpose as they are usually derived by looking through the lenses on some measurement table displayed on the screen. So that’s the FOV the person who looked through the lenses was able to see, which varies depending on various individual factors ranging from face shape to eyesight. It’s not the FOV a game would display on the screen, which usually is higher than these visually guessed values.

[Emre]

It’s crazy.

I read the troubleshooting and am not running any apps that might influence VorpX.

It won’t work with Space Marine 2. I tried, alternative, helper, admin, etc.
I always get the dreaded “VorpX horizontal rainbow lines of death”.

I am using Virtual Desktop and because I run Assetto Corsa I am using OpenComposite (systemwide).

I don’t use SteamVR and I have set VorpX to OpenXR.

Space Marine 2 SOMETIMES works in VR using Vorpx but then when I shake my head too much I get the “VorpX horizontal lines of death” in VR and I have to take the headset off and switch the game off from the main monitor.

Does anyone have an idea?

For world famous AAA games like Space Marine 2 there should really be a “default” way to use VorpX that everyone is told to do. Instead of guessing all the options for hours; alternative hook or not, helper or not, admin or not, etc.

There should be a list somewhere for AAA games on what options to use.
I hate tinkering with a game for hours to try and get it to run.
We are not in 1972.

5080
Quest 3