Consistent Performance Issues After An "Assumed" Quest 2 "Silent" Update/Patch

Kasuxae-Xaesys commented 1 year ago

Description

To sum it all up, ALVR Has been working perfectly for the past six months, But about two days ago prior to this report's upload date, After what I am assuming was a "ghost patch/update" The client will seemingly drop frames in a consistent frequency (5Hz) after any significant head movement despite scene complexity, ALVR Version, Or Settings. Additionally, No Hardware/Software Changes or setting changes have occurred prior to the issue arising.

I have tried everything from moving session.json to get a fresh setting's file to resetting the quest 2 itself, and resetting the device did fix it until I turned it off and got on it the next day, which is one of the reasons that lead me to believe it was a quest update. At this current moment, I am using ALVR Nightly because I thought the issue would be less prominent. but it functions the same.

I will include almost any information required. IE Logs and such.

General Troubleshooting

[x] I carefully followed the instructions in the README and successfully completed the setup wizard
[x] I read the ALVR Wikis here and here

Environment

Hardware

CPU: Intel Core i7-8700K

GPU: NVIDIA GeForce GTX 1070

RAM: Corsair Vengance (2x 16GB) (2x 8GB) (Total: 48GB)

Motherboard: ASUS PRIME Z370-P

Audio: NVIDIA High Definition Audio - HyperX Cloud Stinger Core Wireless + 7.1

Installation

ALVR Version: 20.0.0 (Release) SteamVR Version: SteamVR 1.25.8 (Latest Release)

Install Type:

[x] Packaged (exe, deb, rpm, etc)
[ ] Portable (zip)
[ ] Source

OS Name and Version OS: Microsoft Windows 10 Home Version: 22H2 OS Build: 19045.3031

More Information

In the case this issue is actually solvable and isn't just a "me" only issue, ill post some more information on the subject here. (If you want this removed, just ask/edit it out)

Before this issue became prevalent, Under light load the graph would taper downwards toward 45ms then jump back to 60ms and avarage around 55ms Under heavy load the graph would be a little rougher but in-game performance is still smooth-ish and taper upwards and average around 80ms-110ms

Here are the performance metrics currently

This Is Light Load Vs Heavy Load With Little To No Head Movement.

Light_And_Heavy

This Is Light Load Vs Heavy Load With me turning 90° every 3 seconds.

Light_And_Heavy_Moving

PS: I am unsure how much this issue has to do with ALVR, But thanks for making such an amazing program! Every other program i have tried doesn't give as good of a performance to visual quality ratio as ALVR does! And yes, I just made this account to post this thread.

Vixea commented 1 year ago

are you using a quest with v54?

Kasuxae-Xaesys commented 1 year ago

How do i check that? Also, May you give me more insight on v54? I am assuming its that quest update.

Vixea commented 1 year ago

https://www.youtube.com/watch?v=RFkjUU4hcXE(a little outdated but it should still help you) v54 has a bug with the wifi beam forming that causes this, the only currently known fix is to factory reset your quest

Kasuxae-Xaesys commented 1 year ago

Yes i am using V54.

Vixea commented 1 year ago

then that's your issue, like I said before the only known fix is a factory reset, yea meta kinda messed up

Kasuxae-Xaesys commented 1 year ago

Ah goodness.... well this sucks, wish i could rollback. I wanna be able to play alvr like i used too. I would rather not have to reset the headset and sit through all those stupid "unskipable intro Videos" just to play for four hours.

Kasuxae-Xaesys commented 1 year ago

lets hope someone who knows a more viable solution comes around.

Kasuxae-Xaesys commented 1 year ago

Possible Solution!

Okay I have found out the solution to this for all you ALVR users out there if you are having the same issue as me! It could be a false alarm however, as i haven't had enough time to fully test this. Enable Quest PTC On the mobile app! Ill provide the walk-through below. I will not close this yet until i am 100% sure it is solved.

https://www.meta.com/help/quest/articles/headsets-and-accessories/using-your-headset/quest-ptc/

/!\Warning/!\Using almost any alpha or beta software can cause problems! Do this at you're own risk/!\Warning/!\

Kasuxae-Xaesys commented 1 year ago

Possible Solution!

Okay I have found out the solution to this for all you ALVR users out there if you are having the same issue as me! It could be a false alarm however, as i haven't had enough time to fully test this. Enable Quest PTC On the mobile app! Ill provide the walk-through below. I will not close this yet until i am 100% sure it is solved.

https://www.meta.com/help/quest/articles/headsets-and-accessories/using-your-headset/quest-ptc/

/!\Warning/!\Using almost any alpha or beta software can cause problems! Do this at you're own risk/!\Warning/!\

Okay, So it seems it has partially fixed the issue... whereas on V54 i couldn't get ALVR to function smoothly at all, On V55, All i would need to do is "forget" the current network and reassign the network to get it to work. I will close this issue as "Partially Resolved", However i really hope this can be fixed or worked around on alvr side, as i never had this issue in the past.

alvr-org / ALVR