the first part of this guide is aiming at fixing detection of pico trackers inside vam, or ANY openvr SteamVR games (like blade & sorcery)
another part which will extend this guide will add more information beneficial for troubleshooting pico trackers or any other tracking system not detected in Vam. (second part in progress)
8 points tracking working./ all you have to do is put some files in some folders.
update 3:
1:/ hardware/software requirements:
this guide was made using:
+ pico 4 (standard) firmware 5.11
+ pico tracker app ver. 2.0.1 (2.0.1 is the native/system version wich was downgraded from 2.0.2 for compatibility with DK tracker/ which is not needed if you have 2024 trackers)
+ DK tracker ::aka:: beta motion trackers (not the new 2024 trackers ::aka:: trackers 2.0, but they should work)
+ pico connect 10.2.7
2:/ pico_tracker_profile.json:
the main operation is to restore/reconstruct missing files/folder in pico connect folder,
or construct them manually copy/paste.
go to pico connect folder
"C:\Program Files\PICO Connect\openvr_driver\resources\input\"
open with notepad: "pico_tracker_profile.json"
(the "tracker types" block/struct should look like this don't change anything, what it does say that steamvr is looking for variable path "ressources" which is {pico} in this instance)
in my case the swift folder was missing ("C:\Program Files\PICO Connect\openvr_driver\resources\input\swift")
3:/ the missing "swift" folder:
next, if it's missing, create the 'swift' folder. (C:\Program Files\PICO Connect\openvr_driver\resources\input\swift)
inside the swift folder should look like this, with basic tracking points.
now if you want you can create those files here is an example: of chest profile.json
construct and rename manually the required json files inside swift folder,
or just download the attached json files.
4:/ replace the files with new ones:
i attached everything please observe the path and update accordingly to the location of you instal folders.
How to test:
now for the testing, turn off steamvr and steam, start of clean.
with you pico 4s/ultra heaset on,
pair your trackers & calibrate your trackers,
connect to pico connect server from headset,
launch steamvr from headset,
they should appear in steamvr's list of devices as green/blue boxes,
..
once you are inside steamvr landscape you should see them tracking/moving as white square boxes,
assign for a start just 3 points trackers in steamvr overlay (chest/left foot/right foot leave the rest disabled for now),
restart steamvr after reassignements,
..
back on steamvr landscape
from steamvr overlay desktop view launch vam preferrably from openvr.bat, (lauching from .bat is cleaner)
if this is successfull you should see the tracker white/grey boxes inside vam right away,
UPDATE 2: please redownload all updated files
Inside Vam:
with embody plugin loaded run the wizard,
align the nodes..
from that point on i can't help you out i don't have much experience with embody tweaking..
.. this guide is only aimed at detection.
..
the second part of the guide will be more detailed about how steamvr operate to initiate trackers in steamvr install folders and configuration files...of course to the extent of my knowledge.
rejoice now pico users !! you have unlocked the access to cheap standard tracking inside vam,
of course if you are an experience user you can do much more with hybrid tracking. maybe object tracking capabilities of pico motion tracker can find new uses
to all the friends from owomushi discord channel, thx for assisting me.
another part which will extend this guide will add more information beneficial for troubleshooting pico trackers or any other tracking system not detected in Vam. (second part in progress)
8 points tracking working./ all you have to do is put some files in some folders.
update 3:
github repository guide with files
https://github.com/Elbios/pico-moti...-add-necessary-json-files-to-the-swift-folder
video demostration of the fix:
1:/ hardware/software requirements:
this guide was made using:
+ pico 4 (standard) firmware 5.11
+ pico tracker app ver. 2.0.1 (2.0.1 is the native/system version wich was downgraded from 2.0.2 for compatibility with DK tracker/ which is not needed if you have 2024 trackers)
+ DK tracker ::aka:: beta motion trackers (not the new 2024 trackers ::aka:: trackers 2.0, but they should work)
+ pico connect 10.2.7
2:/ pico_tracker_profile.json:
the main operation is to restore/reconstruct missing files/folder in pico connect folder,
or construct them manually copy/paste.
go to pico connect folder
"C:\Program Files\PICO Connect\openvr_driver\resources\input\"
open with notepad: "pico_tracker_profile.json"
(the "tracker types" block/struct should look like this don't change anything, what it does say that steamvr is looking for variable path "ressources" which is {pico} in this instance)
"tracker_types": {
"TrackerRole_Waist": "{pico}/input/swift/pico_tracker_waist_profile.json",
"TrackerRole_LeftKnee": "{pico}/input/swift/pico_tracker_left_knee_profile.json",
...................................this is an example........... don't copy..................
"TrackerRole_Chest": "{pico}/input/swift/pico_tracker_chest_profile.json",
"TrackerRole_LeftElbow": "{pico}/input/swift/pico_tracker_left_elbow_profile.json",
"TrackerRole_RightElbow": "{pico}/input/swift/pico_tracker_right_elbow_profile.json"
},
in my case the swift folder was missing ("C:\Program Files\PICO Connect\openvr_driver\resources\input\swift")
3:/ the missing "swift" folder:
next, if it's missing, create the 'swift' folder. (C:\Program Files\PICO Connect\openvr_driver\resources\input\swift)
inside the swift folder should look like this, with basic tracking points.
C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\legacy_bindings_vive_tracker_handed.json
C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_chest_profile.json
C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_left_foot_profile.json
C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_left_shoulder_profile.json
C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_right_foot_profile.json
...................... list is incomplete..............................etc.................
now if you want you can create those files here is an example: of chest profile.json
{
"jsonid" : "input_profile",
"controller_type": "vive_tracker_chest",
"input_bindingui_mode" : "single_device",
"input_bindingui_right" :
{
"image": "{htc}/icons/vive_tracker.svg"
},
"input_source" :
{
"/input/power" : {
"type" : "button",
"order" : 1,
"binding_image_point" : [ 90, 80 ]
},
"/pose/raw" : {
"type" : "pose",
"binding_image_point" : [ 100, 90 ]
}
}
}
"jsonid" : "input_profile",
"controller_type": "vive_tracker_chest",
"input_bindingui_mode" : "single_device",
"input_bindingui_right" :
{
"image": "{htc}/icons/vive_tracker.svg"
},
"input_source" :
{
"/input/power" : {
"type" : "button",
"order" : 1,
"binding_image_point" : [ 90, 80 ]
},
"/pose/raw" : {
"type" : "pose",
"binding_image_point" : [ 100, 90 ]
}
}
}
construct and rename manually the required json files inside swift folder,
or just download the attached json files.
4:/ replace the files with new ones:
i attached everything please observe the path and update accordingly to the location of you instal folders.
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\legacy_bindings_vive_tracker_handed.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_camera_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_chest_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_keyboard_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_left_foot_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_left_knee_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_left_shoulder_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_right_foot_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_right_knee_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_right_shoulder_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\pico_tracker_waist_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\swift\vive_tracker_handed_profile.json"
"C:\Program Files\PICO Connect\openvr_driver\resources\input\pico_tracker_profile.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\actions.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_holographic_hmd.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_rift.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive_cosmos.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive_pro.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive_tracker_camera.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive_tracker_chest.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive_tracker_keyboard.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive_tracker_left_foot.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive_tracker_left_shoulder.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive_tracker_right_foot.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive_tracker_right_shoulder.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\binding_vive_tracker_waist.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\bindings_holographic_controller.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\bindings_knuckles.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\bindings_oculus_touch.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\bindings_vive_controller.json"
"G:\xr\VaM\Assets\VaMAssets\SteamVR_Bindings\bindings_vive_cosmos_controller.json"
How to test:
now for the testing, turn off steamvr and steam, start of clean.
with you pico 4s/ultra heaset on,
pair your trackers & calibrate your trackers,
connect to pico connect server from headset,
launch steamvr from headset,
they should appear in steamvr's list of devices as green/blue boxes,
..
once you are inside steamvr landscape you should see them tracking/moving as white square boxes,
assign for a start just 3 points trackers in steamvr overlay (chest/left foot/right foot leave the rest disabled for now),
restart steamvr after reassignements,
..
back on steamvr landscape
from steamvr overlay desktop view launch vam preferrably from openvr.bat, (lauching from .bat is cleaner)
if this is successfull you should see the tracker white/grey boxes inside vam right away,
UPDATE 2: please redownload all updated files
this guide is about detection, please do your tests and report back, thx.
you can return and reassign trackers and test other configurations to look for what is working and what is not working correctly,
to have 8 trackers assign the follwoing in steamvr tracker manager:
feet > feet
camera. & keyboard. > knees
waist > waist
chest > chest
shoulders > elbows
Inside Vam:
with embody plugin loaded run the wizard,
align the nodes..
from that point on i can't help you out i don't have much experience with embody tweaking..
.. this guide is only aimed at detection.
..
the second part of the guide will be more detailed about how steamvr operate to initiate trackers in steamvr install folders and configuration files...of course to the extent of my knowledge.
rejoice now pico users !! you have unlocked the access to cheap standard tracking inside vam,
of course if you are an experience user you can do much more with hybrid tracking. maybe object tracking capabilities of pico motion tracker can find new uses
to all the friends from owomushi discord channel, thx for assisting me.
Attachments
-
Screenshot_com.picovr.picostreamassistant_2024.09.26-17.12.19.867_263.jpeg719.6 KB · Views: 0
-
Screenshot_com.picovr.picostreamassistant_2024.09.26-20.55.21.937_746.jpeg615.2 KB · Views: 0
-
pico_tracker_profile.json2.6 KB · Views: 0
-
legacy_bindings_vive_tracker_handed.json6.3 KB · Views: 0
-
pico_tracker_camera_profile.json2.2 KB · Views: 0
-
pico_tracker_chest_profile.json462 bytes · Views: 0
-
pico_tracker_keyboard_profile.json2.3 KB · Views: 0
-
pico_tracker_left_shoulder_profile.json470 bytes · Views: 0
-
pico_tracker_left_knee_profile.json466 bytes · Views: 0
-
pico_tracker_left_foot_profile.json466 bytes · Views: 0
-
pico_tracker_right_foot_profile.json467 bytes · Views: 0
-
pico_tracker_right_knee_profile.json467 bytes · Views: 0
-
pico_tracker_right_shoulder_profile.json471 bytes · Views: 0
-
pico_tracker_waist_profile.json462 bytes · Views: 0
-
vive_tracker_handed_profile.json1.4 KB · Views: 0
-
actions.json6.3 KB · Views: 0
-
binding_holographic_hmd.json671 bytes · Views: 0
-
binding_rift.json649 bytes · Views: 0
-
binding_vive_cosmos.json663 bytes · Views: 0
-
binding_vive.json649 bytes · Views: 0
-
binding_vive_pro.json657 bytes · Views: 0
-
binding_vive_tracker_camera.json401 bytes · Views: 0
-
binding_vive_tracker_chest.json398 bytes · Views: 0
-
binding_vive_tracker_keyboard.json407 bytes · Views: 0
-
binding_vive_tracker_left_shoulder.json422 bytes · Views: 0
-
binding_vive_tracker_left_foot.json410 bytes · Views: 0
-
binding_vive_tracker_right_foot.json413 bytes · Views: 0
-
binding_vive_tracker_right_shoulder.json425 bytes · Views: 0
-
bindings_knuckles.json12.2 KB · Views: 0
-
bindings_holographic_controller.json10.1 KB · Views: 0
-
binding_vive_tracker_waist.json398 bytes · Views: 0
-
bindings_oculus_touch.json7.4 KB · Views: 0
-
bindings_vive_controller.json11.3 KB · Views: 0
-
bindings_vive_cosmos_controller.json7.4 KB · Views: 0
Last edited: