#Not launching in VR

1 messages · Page 1 of 1 (latest)

frozen hollow
#

Here's my current fucked situation. I use a Oculus Rift S. I am running two GPUs. My main, which is more powerful, is an Intel card, as of right now, Intel does not support VR (cringe, i know)

So to remedy this, i run an older, but still VR capable 8GB AMD GPU as a secondary.

So what i usually have to do to get games to work is assign the correct GPU to to all of the game's related processes, as well as all of the Steam VR and Oculus processes.

I got Geronimo, assigned all four of the .exe files within the game files to the correct GPU, yes, even the Visual C++ programs.

I have tried restarting my pc, restarting Steam, restarting Meta Quest Link.
I have tried it with both Steam and Oculus as the default runtime.
I have tried having only my headset plugged in, and unplugging my monitor.

The only thing i can see being the issue is that there is some other process running somewhere else that Geronimo is dependent on, which i need to assign the correct GPU to.

coarse pelican
#

Hmmmm. I would assume that setting the Geronimo-Win64-Shipping.exe to the correct GPU would indeed fix it. Can you explain what happens when you launch the game?

frozen hollow
coarse pelican
#

Okay, that's good to know. I doubt that has to do with the GPU actually. This seems more like a link issue that other people have experienced as well. You noted trying both Oculus as OpenXR runtime as well as SteamVR?

frozen hollow
coarse pelican
#

I would recommend trying that one more time and we'll consider other options if that does not fix it!

frozen hollow
viscid gate
viscid gate
frozen hollow
#

oh shit my bad

viscid gate
#

i will say uuuh you are running a bit of an unconventional setup

frozen hollow
#

oh, it is disabled

viscid gate
#

have you run into issues with other games while trying to use this? the general consensus i’ve seen online is that this setup doesn’t work great

frozen hollow
viscid gate
#

i see

#

are you able to try virtual desktop’s openxr runtime to see if that would fix the problem?

frozen hollow
empty loom
#

@frozen hollow Could you go into the steam launch arguments and type in "-log" ? There should be a console popping up with logs.

frozen hollow
empty loom
#

same error as mine

#

its on the devs from now on

#

there was nothing i could do

#

i went as far as replacing the game files

coarse pelican
#

Guys that's very helpful! I'm looking into this asap

frozen hollow
empty loom
coarse pelican
#

@frozen hollow @empty loom Could you test something for me?
Go into: %appdata%/local/Geronimo/Saved/Config/Windows and open Engine.ini and put:

[/Script/OpenXRHMD.OpenXRHMDSettings]
xr.OpenXRInvertAlpha=True
bIsOpenXR1_0Enabled=True
bIsOpenXR1_1Enabled=False

See if that helps!

empty loom
#

still the same error for me

frozen hollow
#

because of the API mismatch, i'm giving a go at repairing my Meta link, and verifying files on steam vr

coarse pelican
#

It's kind of weird SteamVR is not up to date with the latest openxr api but hopefully I can force the game to run on 1.0

empty loom
#

The weird thing is i tried every major runtime VDXR, SteamVR and Quest Link nothing worked.

#

Even tried replacing the openxr_loader.dll but it just throws a different error so im assuming there is a code mismatch between the versions.

frozen hollow
empty loom
#

wdym by a frankenstein monster? but i have a normal AMD + AMD PC.

frozen hollow
empty loom
#

Could be an AMD issue.

#

I saw someone else managing to get it working but he had a 5090

frozen hollow
#

hmmm, could be

elfin silo
#

i had this same issue, and on 2nd reinstall it just happened to fix itself for me

#

i was losing my mind trying to fix it

elfin silo
#

currently 2060 as my 9070xt is being repaired

frozen hollow
#

Hmm, yeah our issue could relate to AMD then.

empty loom
#

yea...

elfin silo
#

yeah idk, i just had the exact same thing with game loading only on flatscreen, hope it works when my 9070xt comes back

empty loom
#

it might not honestly. this seems like a AMD driver issue now.

fierce crater
#

Same issue here. If I start with Virtuel Desktop and Steam VR it works. With Steam Link and Steam VR black screen. But I have the OculusXR Plugin running in Steam VR. I will test without plugins

#

Using Intel and Nvidia

coarse pelican
coarse pelican
empty loom
frozen hollow
#

@coarse pelican around when can we expect the API backdate?

coarse pelican
coarse pelican
#

Steam Link does not give me any issues launching. Unfortunate, I was hoping it would've so I could replicate it

coarse pelican
# empty loom still the same error for me

Actually after reading the OpenXR source code, I think it's supposed to into Game.ini not Engine.ini, same folder. If the Game.ini doesn't exist you can create it @empty loom @frozen hollow

#

Let's see if that helps

empty loom
coarse pelican
#

Alright, so looks like we're getting somewhere

empty loom
coarse pelican
empty loom
#

yes

coarse pelican
#

Dang

frozen hollow
coarse pelican
#

If it doesn’t exist, you can just make one

frozen hollow
frozen hollow
#

Interesting. I tried swapping Oculus back to default runtime, it didn't work, but it deleted the Game.ini file, and the log is back.

empty loom
#

@coarse pelican Is there any args i can put to have more logs? or do i need a special game version?

empty loom
#

I managed to fix the issue after many hours of debugging with nothing but the issue is most definetly on the user side. Also i am not 100% sure if this works for everyone but it should. (Its the cause of most problems with VR not launching anyway)

What my guess to the issue was are OpenXR API layers XRNeckSafer, XRFoveatedRendering etc.

https://github.com/fredemmott/openxr-api-layers-gui/releases

I recommend downloading this tool for disabling the API layers. And you should disable 99% of things there. Only thing i decided not to disable is the VD Oculus compatibility layer.

Besides that, you need to apply the fix Stilton provided in the other message.

Go to %localappdata%/Geronimo/Saved/Config/Windows , Create the "Game.ini" file. (Case sensitive) and paste in these contents:

xr.OpenXRInvertAlpha=True
bIsOpenXR1_0Enabled=True
bIsOpenXR1_1Enabled=False```

The game should launch in VR now.

Other things that might work if this didn't.

- If your and AMD GPU change your drivers to the VD recommended version.
- Reinstall VD.

If anyone else has this issue please point them to this message.
GitHub

UI for managing OpenXR API layers. Contribute to fredemmott/OpenXR-API-Layers-GUI development by creating an account on GitHub.

#

@frozen hollow If you could confirm this actually works would be lovely.

#

Or anyone really

vernal karma
empty loom
#

It should

#

Honestly idk why i didnt start with this first lol

#

Atleast the API disabling part. The Game.ini is UE5 specific.

coarse pelican
empty loom
#

oh

#

your right

#

my bad

#

fixed

coarse pelican
#

You're the best

empty loom
left bane
regal stag
#

anyone been able to solve this problem with the index?

empty loom
regal stag
#

did everything in the post and didnt work until i restarted shouldve deleted the post my bad

frozen hollow
#

@empty loom yeah no dice for me. I might be missing something, but i don't even have anything to disable in that program.

#

yeah every time i launch now the Game.ini file just gets deleted

empty loom
#

Check other tabs, and what runtime are you using?

#

Also running the game through steam on PC somehow deletes the game.ini. For me it isnt deleting when using the games tab on VD.

frozen hollow
#

other tabs are empty aswell

empty loom
frozen hollow
empty loom
#

holy this is really weird

#

you never used openxr toolkit?

#

or foveated rendering?

frozen hollow
#

nope

empty loom
#

whats your "VR" gpu?

frozen hollow
#

A very abused RX 580

empty loom
#

i saw people actually playing on B580s so maybe you can try? unless your using a different intel gpu.

#

i doubt an RX580 can run a UE5 VR game...

frozen hollow
empty loom
#

Yea, it might work only for VDXR for some weird reason

near gale
#

Seems to work fine for a bit, then screen tears and goes black, looks to be running fine on my monitor, but on my headset no worky. Intel i9 9900K, nvidia 3060 12GB, quest 2. Gonna be honest, I'm tech savy only to a certain point lol. I was able to get to the point where I'm stuck right with AL3. Any advice or help would be appreciated!

empty loom
#

Well thats a different issue then. Idk how much i can help. Im no gamedev by any means and OpenXR is especially complicated same as VR rendering pipelines. I would look first in the #1525050668295913502 channel if your issue is not listed then create a new bug report.

Try launching the game with the -log arg. And send the logs from the console.

#

And OpenXR logs from VD could be useful also if you have that.

twilit path
#

Can someone help me with this same issue? I made a bug report and I'm really excited to play the game, but it isn't possible

#

dawg I don't even know what a VD is 😭 edit: oh, virtual desktop

alpine raft
#

Might sound dumb but i got my game to launch by simply enabling virtual desktop in device manager and launching the game through VD instead of linking through meta

frozen hollow
#

Vd seems to be the fix for the most part

#

For those that can use it anyway, lol

twilit path
twilit path
empty loom
#

Headset also would be nice to know and your PC specs

twilit path
twilit path
#

Running a valve index, steamvr.

PC:
Current windows version
Intel I7-13700kf
32 gb SK Hynix DDR4 (3200MHz)
Sapphire RX 7900XT

empty loom
#

Okay so steamvr for some reason is just not working got it

#

@coarse pelican could you edit the know issues so it says that steamvr still is not working?

#

But i dont think i can take on and help with this issue when i have nothing to debug on. Sorry guys

coarse pelican
empty loom
#

yea this is such a weird issue

#

@twilit path
#1525436505995214860 message
try this fix if you havent already

empty loom
#

does the console from the -log arg say anything?

twilit path
#

I would have to look when i get home

empty loom
#

Okay

twilit path
#

I do have a little more info in my post #1526394146045169816

empty loom
#

I think it's a different issue then. This is a fix for the game not even detecting your headset and there are boxes on the screen that don't move

twilit path
#

Could be. It's a game issue for sure though, everything else works fine.

#

Played other games without issue.

unborn shore
#

Just wanted to hop in and say Im having the same issue. Shows on display but does not detect/play in HMD. I tried these fixes and they have not worked for me. On quest 3 with link cable. 4080 Super ryzen 7 7800x3d

coarse pelican
unborn shore
#

It was not. I just set it as my active and it now is working. Virtual Desktop appeared to be my xr runtime according to the meta link app and i just set it as active.

lost leaf
lost leaf
runic meteor
#

@lost leaf interesting workaround the issue i had was a little different because rather than open XR layers in the steam menu being the issue for some reason i had to disable reshade in open XR API layers from github good job though👍

empty loom
#

Both basically do the same thing, maybe steamvr does it a bit better i have no idea.

coarse pelican
empty loom
#

You mean the version thing? Yes, but the game launches in VR regardless. From what i know Quadviews-Foveated-Rendering is bound to have issues with modern UE5 games. I honestly dont think there is anthing you can do to fix it necessarily but you can reproduce the bug by installing quadview foveated rendering, and or other OpenXR API layers.

#

Maybe you can try fixing it from there

coarse pelican
#

Okay, will do. Thanks!

frozen hollow
# coarse pelican Okay, will do. Thanks!

I would like to mention. Utilizing VDXR, and removing layers oseems to be a fix for those using streaming headsets. But those workarounds don't work for folks like myself who use a wired headset. the game.ini thing takes the version error away, but running steamvr deletes it, and the game still launches into flatscreen.

I don't know what headset you use, but if it's a standalone headset, perhaps trying to get your hands on a wired headset could give you somewhere to start.

honest sapphire
#

Hey I am having the same problem and I am a little confused please will u help me PC spec: I have a nvidia GeForce rtx 5090, AMD Ryzen 9 9950x3D, 1125GB. I use steam vr I have the Pimax Dream air slam and the BigScreen beyond 2 I use both it won’t even launch on the dream air slam it gives me some type of error code thing

#

The game will launch on my screen, but it won’t launch on either of my VR headset my headset

#

i have tired ur method but im just confused honestly

empty loom
#

Im sorry but i am no tech support person. And quite frankly i dont have the time to help people on this complicated matter. You will need to wait until Stilton figures something out.

#

That goes to all people please dont ask me or dm me for help

honest sapphire
#

sorry dude

empty loom