You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've followed your tutorial to build the APK, and the app launches successfully. Both headsets (xr elite) can connect to the chosen server without any issues.
However, I've encountered an issue with the marker scanning process. (It's quite challenging to scan the marker, and sometimes the marker isn't positioned correctly, but it still somewhat functions.)
The problem arises when the host scans the marker and selects it, clicking "Next." At this point, both players are immediately sent to the game without prompting the second player to scan the marker. Consequently, both players end up in the wrong positions.
Could you please guide me on whether I missed a step or configuration that should prompt the second player to scan the marker? Any tips or suggestions for improving marker detection would be greatly appreciated as well.
Thank you for this repo :)
The text was updated successfully, but these errors were encountered:
Hi,
I've followed your tutorial to build the APK, and the app launches successfully. Both headsets (xr elite) can connect to the chosen server without any issues.
However, I've encountered an issue with the marker scanning process. (It's quite challenging to scan the marker, and sometimes the marker isn't positioned correctly, but it still somewhat functions.)
The problem arises when the host scans the marker and selects it, clicking "Next." At this point, both players are immediately sent to the game without prompting the second player to scan the marker. Consequently, both players end up in the wrong positions.
Could you please guide me on whether I missed a step or configuration that should prompt the second player to scan the marker? Any tips or suggestions for improving marker detection would be greatly appreciated as well.
Thank you for this repo :)
The text was updated successfully, but these errors were encountered: