Oculus Quest 2 to ROS connection
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 20/100
- Tipo de issue
- Bug
- Clareza
- Precisa de esclarecimento
- Status de atividade
- Estagnada
- Stack de tecnologia
- docker, unity
- Domínio
- distributed-systems, game-dev
Direção de pesquisa
The issue names issue #353, the Pick and Place tutorials through Part 3, Unity on Windows 10, and ROS running in Docker. Start by comparing the connection and VR setup against issue #353 and those tutorials; done means the running Oculus Quest 2 application establishes a connection detected by the ROS server.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Hi everyone,
I am very new to
I'm really sorry to open a new issue even though there is a closed issue that I would like to refer but I can't manage to reopen it.
The problem is the same as for issue #353, I am trying to play the pick and place demo on my Oculus Quest 2. The build goes fine and no errors are prompted but when the app is running ROS does not receive any connection.
I followed the steps explained in issue #353 by Niccolò but as I press Build and Run and put my Oculus Quest 2 on the application is running but nothing happens on the ROS server as no connection is detected. (for how to run the application on the oculus directly from unity I am referring to a you tube video: https://www.youtube.com/watch?v=YwFXQeBmxZ4)
Moreover, I could not see the publish button but I think this is more a design problem since it is my first time developing VR application and I'm not familiar with the process. Anyway, if anyone has a quick solution even to this problem I would be grateful.
I'm running Unity on Windows 10 and ROS on the Docker Engine suggested at Pick and Place tutorial Part 0.
I followed the Tutorial Up to Part 3 Step by Step many times before reopening the issue.
For what regard the VR implementation I followed the guide linked below:
https://learn.unity.com/tutorial/create-a-vr-starter-project-from-scratch#620f8f56edbc2a705d1c3578
which should be the same proposed by Niccolò.
Still, I followed it step by step the same number of times I followed the tutorial of this Repo. Only thing that differs from the unity VR tutorial is that I could not manage to change the Scriptable Render Pipeline Settings as the Pick_and_Place Project does not include the URP as far as I understood.
Last thing is that I also added the Oculus plug-in from the XR Plug-in Management.
OS: Windows 10, for Unity
ROS running on docker as for Part 0 instruction
Packet Manager in Unity: 1) Ros Tpc Connector 2) URDF Importer
Laptop model: Asus Rog GL752VW, that means gtx 960m so no Oculus link possibility in case that matters.
I am writing everything as I am not familiar with none of the plication involved (ROS, Unity, Oculus Quest) and I want to be as complete as possible.
Again, sorry for opening a new issue but me and my project made are running out of time and ideas, if I missed something important for your understanding of the problem or done something wrong let me know let me know.
I am waiting for your help,
thank you in advance
RBR
- Linguagem predominante
- C#
- Estrelas
- 2.6k
- Forks
- 473
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Sem guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de Unity-Technologies/Unity-Robotics-Hub
-
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 35/100
-
ROS2,ActionAberta
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 25/100
-
Is the project deprecated?Aberta
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 20/100
-
Force/Torque sensorAberta
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 15/100
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 25/100
Unity-Technologies/Unity-Robotics-Hub#433 · 1 comentário ·
Todas as issues de Unity-Technologies/Unity-Robotics-Hub
Issues semelhantes
-
DXF with empty names failsAbertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 3 dias
-
bug python
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
ilia-sokolov/OfficeAgent.NET#89 ·
Mantenedores costumam responder em até 13 dias
-
documentation
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
juandresrodca/AdminForge#66 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
umbraco/Umbraco.Automate#612 ·
Mantenedores costumam responder em até 1 dia