Skip to content

Timeout and connection issue when running demo on Quest 3 #42

@ZoExOr

Description

@ZoExOr

Hello and thank you for the great work on this project!

I encountered a timeout issue when trying to run the demo scene on my Quest 3 headset. The VR scene remains empty and nothing is rendered in the headset, even though the Python backend and Unity scene seem to be running.

Here are the steps I took:

  1. Connected PC and Quest 3 via USB cable (confirmed working)

  2. Both devices are on the same subnet with the same IP prefix

  3. Installed all required Unity plugins as per your documentation

  4. Set IP address and port in: demos/libero/libero_robot_control.py and simpub/core/node_manager.py

  5. Manually configured node info for both ends in
    IRXR-Unity/Assets/IRXRClient/Scripts/IRXRNetManager.cs

  6. Called OnConnectionStart() in the Start() method

  7. I ran the Python demo script (libero_robot_control.py) on PC first, then launched the Unity scene on Quest 3.

However, the scene in the headset remains empty (no Libero env appears), and following error messages are observed:

In Unity:

FiniteStateMachineException: Rep.XSend - cannot send another reply

I would assume it's possibly triggered by a second reply attempt on a single request?

In PC (Simpublisher):

Traceback (most recent call last):
  File "...\simpublisher\simpub\core\node_manager.py", line 219, in async_register_node_info
    self.xr_nodes_info[node_id] = loads(
  ...
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

It seems that an empty or malformed JSON string is being received.

At this point, I'm not sure if manually calling OnConnectionStart() is correct, but without it the connection does not seem to initialize at all.

I also noticed that the Quest3 branch is significantly behind the main branch, and the connection setup logic in main is different. I wonder if this might be causing inconsistencies when running cross-device communication.

It would be a great help if you could provide any guidance on how to properly set up the connection and establish communication between the Quest 3 and PC. Thanks again for this amazing toolkit and all the hard work! Let me know if any additional logs or setup details would help! ;)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions