User Tools

Site Tools


democap:hmdquest

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
democap:hmdquest [2026/03/23 02:48] dragonlorddemocap:hmdquest [2026/03/27 16:17] (current) dragonlord
Line 9: Line 9:
 ====== Basic Support ====== ====== Basic Support ======
  
-DEMoCap can be used with Meta Quest HMDs to do limited motion capture. With these HMDs only upper body motion capture are usable with the following features present (depending on your Quest model):+DEMoCap can be used with Meta Quest HMDs to do limited motion capture. The following features can be captured depending on your Quest model:
   * Head tracking   * Head tracking
   * Hand tracking (controller or hands only)   * Hand tracking (controller or hands only)
Line 15: Line 15:
   * Face tracking   * Face tracking
   * Finger tracking   * Finger tracking
 +  * Upper body movement (body tracking enabled)
 +  * Lower body movement (body tracking enabled)
  
 Right now DEMoCap does not yet run on the Quest itself. Instead you have to connect the Quest to your PC where DEMoCap runs. This connection can be either wired or wireless using one of these programs: Right now DEMoCap does not yet run on the Quest itself. Instead you have to connect the Quest to your PC where DEMoCap runs. This connection can be either wired or wireless using one of these programs:
Line 24: Line 26:
 The most stable out of these is WiVRn. There controller and hands only works good. SteamLink has problems with finger tracking breaking the capture on Linux. Occulus Link/AirLink pretty much can't do finger tracking at all. Hence with controller mode various solutions are working while with finger tracking WiVRn seems to be the most reliable one. You have to try for yourself what works for your setup. The most stable out of these is WiVRn. There controller and hands only works good. SteamLink has problems with finger tracking breaking the capture on Linux. Occulus Link/AirLink pretty much can't do finger tracking at all. Hence with controller mode various solutions are working while with finger tracking WiVRn seems to be the most reliable one. You have to try for yourself what works for your setup.
  
 +To use body tracking you have to do the following:
 +- Enable body tracking in the Settings of your Quest
 +- Enable upper and lower body tracking in the WiVRn settings
 +- Enable body tracking in the WiVRn main menu (toggle icon at the top of the screen)
 +
 +Body tracking is done on the Quest using an AI model applied on the cameras built into the headset. The software runs on the headset itself so DEMoCap does not have to do this processing itself. Nevertheless body tracking on the Quest does reduce performance to some degree.
 ====== Full Body Tracking ====== ====== Full Body Tracking ======
  
-The Quest 3 (3S) supports estimated full body tracking. For this the Quest uses the cameras built into the HMD to estimate the full body pose using AI calculations running on the headset. These poses can be retrieved as either a skeleton or as simulated trackers using WiVRn. DEMoCap supports simulated trackers using WiVRn. Unfortunately this has some problems since the way WiVRn simulates the trackers is unfavorable for DEMoCap. This section outlines how to best configure DEMoCap and your characters to get the most out of a Quest FBT setup.+The Quest 3 (3S) supports estimated full body tracking. For this the Quest uses the cameras built into the HMD to estimate the full body pose using AI calculations running on the headset. These poses can be retrieved as skeleton over WiVRn. DEMoCap supports simulating trackers using this full body tracking to make it transparent to your existing setup. This section outlines how to best configure DEMoCap and your characters to get the most out of a Quest FBT setup.
  
 ===== Actor Setup ===== ===== Actor Setup =====
Line 34: Line 42:
 Since the quest only can use reliably the floor distance of the headset it calculates the body proportions solely from it. In general the floor height of a Quest is your own height minus 8-10cm. Hence you can measure your own height and then fill in the values as follows: Since the quest only can use reliably the floor distance of the headset it calculates the body proportions solely from it. In general the floor height of a Quest is your own height minus 8-10cm. Hence you can measure your own height and then fill in the values as follows:
  
-  * Shoulder Level: ''Height'' - 0.24+  * Shoulder Level: ''Height'' - 0.4
   * Shoulder Width: (''Height'' - 0.09) * 0.25   * Shoulder Width: (''Height'' - 0.09) * 0.25
   * Arm Length: (''Height'' - 0.09) * 0.45   * Arm Length: (''Height'' - 0.09) * 0.45
-  * Leg Length: (''Height'' - 0.09) * 0.475+  * Leg Length: (''Height'' - 0.09) * 0.6
   * Foot Distance: Same as ''Shoulder Width''   * Foot Distance: Same as ''Shoulder Width''
  
 For example if you measure your height as 1.8m then you would enter the following values: For example if you measure your height as 1.8m then you would enter the following values:
  
-  * Shoulder Level: 1.56+  * Shoulder Level: 1.4
   * Shoulder Width: 0.4275 (or rounded 0.42)   * Shoulder Width: 0.4275 (or rounded 0.42)
   * Arm Length: 0.7695 (or rounded 0.77)   * Arm Length: 0.7695 (or rounded 0.77)
-  * Leg Length: 0.81225 (or rounded 0.81)+  * Leg Length: 1.026 (or rounded 1)
   * Foot Distance: Same as ''Shoulder Width''   * Foot Distance: Same as ''Shoulder Width''
  
-===== AutoHuman Setup ===== +===== WiVRn =====
- +
-As mentioned above the simulated WiVRn trackers of unfavorable. In particular the elbow tracker is located at the elbow but with the orientation of the lower arm instead the orientation of the upper arm. If you use these simulated trackers directly you will get bad poses, for example the elbow spread depending on your lower arm bending instead of your upper arm position. +
- +
-You can counter this problem the following way: +
- +
-  * Create a duplicate of your character configuration you usually use +
-  * Select the [[democap:motiontransferautohuman|AutoHuman Motion Transfer]] +
-  * In the ''Advanced'' panel tick the ''Elbow guide use position'' checkbox +
-  * Save profile+
  
-The ''Elbow guide use position'' tells DEMoCap to use the position of the elbow trackers to guide the inverse kinematics instead of using the orientationThis solves the problem of the simulated tracker orientation to be wrong but the quality degrades the further away your pose gets from the base IK poseHow well this extreme poses work depends on the character skeleton and the base IK animation used.+The stable and development branch of WiVRn does not yet contain support for Quest FBT. For this you have to use a separate feature branch. Packages for Linux and Quest you can find here: 
 +  * [[https://github.com/WiVRn/WiVRn/actions/runs/23384815703/artifacts/6040835306|WiVRn APK]]. You have to side-load this APK onto your QuestSee WiVRn for information on how to do this
 +  * [[https://github.com/WiVRn/WiVRn/actions/runs/23384815703/artifacts/6040832482|WiVRn Server Flatpak]]. For your Linux system to connect to the Quest.
  
 +For more informations have a look at the [[https://wivrn.github.io/|WiVRn Page]].
democap/hmdquest.1774234117.txt.gz · Last modified: 2026/03/23 02:48 by dragonlord