Hi, welcome! So most of the Quest crashes, as far as we know, is related to memory - basically when you load a certain amount of details (e.g. other players, NPCs, monsters, environment) it takes memory and eventually goes over the limit on Quest and crashes. With the scale of Orbus and the amount of props/people/monsters we load in its a balancing act to ensure good performance as well as trying to keep the play experience as close to PCVR as we can.

We are investigating and hope to have a way to track the memory usage better in the near future so we can continue to improve performance, but if you can let us know any situation where it happens a lot more, or even if you find a way where it reproduces every time, that would be really helpful too so we can debug exactly what’s causing it.

Thanks, and sorry for the issues. We’re working on it.

Edit: On a similar note, some games when played don’t clear the memory properly on the Quest, so some players have had good luck with completely closing down the quest (not just putting into sleep mode but completely shutting down) then re-booting and launching Orbus then to ensure any of the previous apps have cleared the memory they were using.