After the upgrade to 13.15 DeoVR exits immediately after launching.
If I click on DeoVR icon a white circle shows during one or two seconds, then it exits to the Pico's homescreen.
Is there anybody whose Pico 4 does not crash with 13.15?
Hi, could you please let me know if you are using Pico 4 with any additional tools? Streaming assistant, or anything else?
I have the same issue.
I do not use an other tools, no streaming assistant.etc.
Pico 4 here, all normal/unremarkable in latest build. No crashes.
Kieshi I tried to launch standalone (native) DeoVR on the headset itself, without any additional tools.
Hi guys, would it be possible for you to get the logs so we can see what is happening?
Also, please could you try to delete app and then install it again and see if it helps with this issue?
- Edited
Kieshi Replying on this thread instead of the release one to keep things focused on a single issue.
Yes I did try deleting the app and reinstalling it from the store. That did not lead to a different behavior.
I then deleted it again and installed a backed up APK from local drive from an earlier version. My local settings were nuked as well, but that is to be expected when deleting an app. The older version does work as expected.
As mentioned in the other thread, I am running an outdated Pico OS: version 5.4.0 from maybe as far back as Feb 2023, perhaps others facing the issue can tell if they are using the latest update or are also on an older version.
Also I have developer mode turned on. Other than that everything should be as a stock pico4.
Kieshi
I still have this issue, my Pico OS is also 5.4.0 like @EUZfZxe7j
Kieshi Thanks, I might update the Pico OS at a later date, but for now I am dependent on this specific version for my own work and apps. Also the new DeoVR doesn't have anything I need in particular, so I am good for now.
Because I'm intrigued by this issue I did take a closer look and specifically at the PICO Unity SDK you guys are using, because those do depend on specific Pico OS versions (as mentioned here). I thought maybe you upgraded in the latest release, but from what I can see you use 2.1.2.2 in the latest as well as the last few releases. 2.1.2 requires Pico OS 5.1.0 or higher.
If I feel like it I might debug a bit further later, I'll let you know if I find anything.