You are making things the worst!
Where to start...
I had v79 going for a long time, until my Virtual Desktop Streamer decided to push an update and rendered my Quest 3's VD useless, forcing me to update. Got v85, and quite a few issues with it (bugging UI, elements not loading, and so on).
After a couple months (4-6 ish), decided to check for VD updates, as features were not stable as they should (thanks for messing everything up in the place, ggodin).
Checked for the version, had an update, etc. Noticed, that the Quest 3 system pointed out (something which I honestly dislike extremely) "Update 2.01" with a due-date to it, the typical "if you don't update now, we will update it regardless of your choice in a few weeks!", thanks Meta. Absolute consumer friendly behavior, especially in Europe.
Updated the system, because why postpone it, if it is going to mess you up anyways. and the problems began.
Glitching UI elements on the old UI. Glitching UI in VD. Brightness flickering on screen while in VR games.
Atrocious update. MetaStoreSupport on Reddit suggested re-updating the OS via webseite (https://www.meta.com/en-gb/help/quest/software_update/ ) which simply does not work at all. Downloading seems to work fine, installing will always fail, regardless of browser (edge, chrome, brave, vivaldi), with their extensions (adblocker on/off, js-blocking on/off), doesn't matter which USB port, it will always fail (fix your stuff, Meta!)
Since I was fed up by the sheer incompetence showing UX bugs on v201, I've joined the PTC the first time, and oh boy ... it got even worse! Sidenote: "Unchecking PTC will factory reset the headset and will retrieve stable/public version of OS" is simply a lie! Remove that line from your Meta App! I am still stuck to v203, it does not do any good lying to your customers!
v203 started off harshly bad. UI elements not reacting, not loading, bugging, softlocking UI, rebooting UI without rebooting the headset (UI simply crashes), and that was not everything.
VD was also suffering a lot by this. I was not able to use my dedicated router anymore, as I was using it for over 2 years now!
Router 1 is plugged into my MB's LAN Port, and has WAN access.
Router 2 is plugged into my LAN adapter, without any WAN - local router, just for VR.
Usual behavior, before v203, accessing my PC via VD: Start headset, start Router 2, login into the 6GHz system, start VD, get it going.
v203 (old UI, from 5 days ago, until yesterday...) behavior: Login into my 2.4GHz Router (Router 1), start VD, wait for it to connect to my PC, receive the Token that the app is not pirated *ugh* ... switch over to my Router 2, start VD again, get it going, until I shut down my headset, to re-repeat the entire stupid process.
v203 (new UI): none of these work anymore, dedicated router + VD is useless.
Thanks.
I am still able to connect to my PC using SteamLink and ALVR. Whatever you guys did with your OS, and ggodin with its Virtual Desktop software - change it/revert it, I don't care.
If this is not going to be solved within 2 weeks, I want a refund of this product, as I am not going to deal with this nonsense anymore. I had 3 days of troubleshooting to understand the mess you guys fabricated there, and now out of a sudden, the new UI appears (which is btw the most anti-UI I've ever seen in my entire life, it is so clunky and user unfriendly ... **bleep**), and nothing works anymore. I am tired of this nonsense.
Please treat this as a formal notice. I expect the issue to be resolved within, as noted before, 14 days from receipt of this message. If no satisfactory solution is provided within this timeframe (e.g. refund), I will consider pursuing my rights under EU consumer protection law, including seeking legal remedies.
