![]() The screenshots posted below are other people having issues with this recent update so it's just not me. This shows me how little work and support is being put into the windows client and it's honestly disappointing, I know your whole shpeel is trying to push standalone VR but when it gets to the point I can't even use pcvr that is a sign you need to redirect your attention. I then think my install is corrupted and needs a reinstall, your installer took 30 minutes to download less than 100mb of data for the install. Even with all of this in consideration, the app still bugs, I connect my headset via a link cable and I am left with 3 loading dots. I'd like to address the first problem being the infinite loading screen issue I received when updating to v60 and updating my windows client, I was using an older version before with no issues, all drivers are updated, windows is running on the current version, my firewall is set up correctly and so is my antivirus, so I'd just like to squash those bugs real quick. And it's really looking like you don't care about your userbase. It's buggy, it's slow, the UI hasn't changed a bit in 4 years. Over the past couple years iv stuck with oculus, starting with a cv1 and using a quest 2 with link today, the headset itself is solid, the software in the other hand is not. I'm writing this post for a recent issue I have come across but also as a wakeup call to the windows client development team. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |