#Connection Repeatedly cutting in and out after about 20 minutes of playtime.

1 messages · Page 1 of 1 (latest)

maiden tinsel
#

OS: Arch Linux, KDE Plasma
CPU: AMD Ryzen 7 5800X
GPU: Nvidia GeForce RTX 3060
Installation Method: ALVR Launcher from the AUR.
Headset: Quest 3
PC

I finally got wireless working however I seem to have an odd issue. After about 20 or so minutes of gameplay, it starts to rapidly cut in and out for no reason.
Upon changing some settings such as disabling client-side processing, disabling adaptive bitrate and setting a constant one, and changing codecs, it works but the view is glitchy.
Here's the funny thing about it being glitchy as well, the frames are updating beautifully, like looking around is instantly showing the new environment, but something seems to be wrong with the decoding client-side. You can ignore the connection refused, it's just because I took off my headset.
I've also attached screenshots of the statistics.

📎 Logs.txt 📎 session.json image.png image.png image.png
coarse lava
#

Is your headset in developer mode? It looks like your quest in a standard config... are you not on ethernet to the pc and wifi on the quest? Have you tried USB direct to rule out its a wifi issue.

Frames on PC look good on screen but deteriorated on the HMD?

There are a myriad of network drivers being pushed from windows update that are defective currently double check your network driver release date. If its not from this year you have a defective one just manually update it turn driver updates off...

Im not sure if im allowed to do this but i guess we can find out. I built an ALVR system loader that installs quest device in ADB mode and optimizes the settings and lines it up 100% with your ALVR install... so assuming im allowed to do that here if be down to check your bug out to see if its s hardware layer thingy

maiden tinsel
# coarse lava Is your headset in developer mode? It looks like your quest in a standard con...

Quest is in developer mode, the app was installed via ADB.

PC is connected via Ethernet, and router is literally a foot or two from the headset.

In terms of network drivers: Linux, I’m using Linux… not Windows. And I keep it updated.

It could definitely be hardware layer since the HorizonOS is bugging out. It may be viable to just factory reset and then re-enable debug mode.

#

Because if HorizonOS is bugging out, headset drivers and stuff could already be messed up

coarse lava
pine wasp
#

nvidia does not work with the aur version so just dont use that - also including "alvr-nvidia"

#

will work fine if you install alvr via normal way - not using broken aur

#

the reason - its very difficult to compile on arch because everything is so new, so the build is always broken for nvidia

#

if you insist on building alvr yourself for nvidia then either use some container environment or downgrade your gcc - arch is too new and new gcc doesnt support nvcc

#

the stuff on github gets build via container using the "correct" environment, arch does not provide the "correct" environment for nvidia