[Quest] Handling client logout events on quitting the application
Hi there, I have a client-server model setup where the Quest is a client, connected to an external dedicated server via an IP connection. I can force the Quest to handle a logout by interacting with a UI or pressing a button however I'm wondering if there's a way to automatically have the client disconnect from the server when the application is closed using the Quest's external quit menu? (Pressing the Oculus button and choosing 'Quit') The issue I'm experiencing is that the Quest is still connected to the server even after the application has closed. This results in: - The client's pawn still visible and inactive on the server - The client unable to rejoin the session as it's still technically connected. All help is welcome and appreciated. Thanks, Jackson.866Views1like1Comment
Unreal matchmaking only works with some accounts (Must call get_signature first)
I've been setting up multiplayer matchmaking, and it works between two Rifts as long as they are both logged into my account. But it fails with another user and me. The other person gets the error " Error: Oculus: Must call get_signature first (1971051)". We both have access to the app in the dashboard. Any idea what could cause this error? Why would my account be the only one that works? EDIT: turns out it also works with another person here. But not three other people I've tried so far... I don't know of any differences in our setups. So weird! Anyone know what the issue could be?1.4KViews0likes4Comments