Endata Posted March 30, 2019 Share Posted March 30, 2019 After the latest update to 1.2.11 (r9) my library is empty. It's ok if I check on the viveport webpage, but not in the viveport application. I've tried refresh, and re-installing, but no change. Also, if I go to subscription to download a game, it immediately shows error messge "Server is busy at this moment. Download has not started. Please try again." No connectivity issues with anything else. If I try to start a viveport purchased game from Steam library shortcut it errored with some permission issue. The links to those games have dissapeared since the re-install. The upshot is that I cannot play any VR games purchased through viveport or any subscription games. Link to comment Share on other sites More sharing options...
SuperNikoPower Posted April 1, 2019 Share Posted April 1, 2019 Hello, I'm going to send you a PM shortly about this. Keep an eye out. You can always email Viveport's customer care team directly at customerservice@viveport.com Link to comment Share on other sites More sharing options...
Endata Posted April 1, 2019 Author Share Posted April 1, 2019 Thanks SuperNikoPower, but I had realised I could contact support directly and they have been working through the issue after I posted logs. They sent me a solution this morning, and I've just tried it - it worked. The ticket title changed to "because title.data has duplicate app." - so I guess this was the cause, though no indication of how it became that way. They supplied me with a replacement file and instructions which solved the problem. Link to comment Share on other sites More sharing options...
Endata Posted April 2, 2019 Author Share Posted April 2, 2019 I'm told this was caused by an issue that has been fixed in an update today, so shouldn't occur again / to anyone else. Link to comment Share on other sites More sharing options...
HackPerception Posted April 4, 2019 Share Posted April 4, 2019 Popping in to confirm that we did release a patch to the Viveport desktop client that specifically targets what we believe to be the root cause of the bug highlighted in this thread. It should be fully patched as of v1.3.0. If you are reading this and having a similar issue on an updated client, do not hesitate to reach out to us via Viveport -> Settings -> Report Issue or directly via customerservice@viveport.com Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.