Extremely Hard To Get Working

[DrBenStoneSage]

I've been spending 3 weeks trying to get this working robustly with no success. So far:

• I saw the live updates from Unity direct from the SteamVR tracking data when clicking/holding the mouse
• The release exe for the app breaks with a key error and stops working
• I ran the Python program manually and that seems to work with the OSC debug in VRChat
• I have only sporadically seen the tracker moving in VRChat, when I switched to a different world it stopped working
• Removing the gameObject with component borks the project, likely from VRCFury settings e.g. (BlendTree "processing" in state "Remote" in Controller "[FX]" uses parameter "ObjectTracking/Scale" which does not exist.)
• Removing the hackebin from VRCC still the project is borked
• Readding it fixed it
• I have it tracking again in the first world, but toggling the trackers/playspace doesn't turn them off and the position/orientation doesn't match the trackers in steamvr
• Switch worlds I get
  2025-08-29 15:10:14,775 - main - INFO - PlaySpace[16] None => -180
  2025-08-29 15:10:14,776 - main - INFO - PlaySpace[17] None => -180
  2025-08-29 15:10:14,776 - main - INFO - PlaySpace[18] None => -180
  2025-08-29 15:10:14,776 - main - INFO - Traceback (most recent call last):
  File "D:\github\Object-Tracking-App\ObjectTracking.py", line 543, in
  send_position(key, pos, tracker)
  File "D:\github\Object-Tracking-App\ObjectTracking.py", line 161, in send_position
  [tracker_config[7 + offset], tracker_config[19 + offset]],
  ~~~~~~~~~~~~~~^^^^^^^^^^^^^
  KeyError: 19

2025-08-29 15:10:14,777 - main - INFO - PlaySpace[19] None => 12
2025-08-29 15:10:14,777 - main - INFO - PlaySpace[20] None => 12
2025-08-29 15:10:14,777 - main - INFO - PlaySpace[21] None => 12
2025-08-29 15:10:14,778 - main - INFO - PlaySpace[22] None => 180
2025-08-29 15:10:14,778 - main - INFO - PlaySpace[23] None => 180
2025-08-29 15:10:14,778 - main - INFO - PlaySpace[24] None => 180
2025-08-29 15:10:14,779 - main - INFO - PlaySpace[25] None => 5
2025-08-29 15:10:14,779 - main - INFO - PlaySpace[26] None => 5
2025-08-29 15:10:14,779 - main - INFO - PlaySpace[27] None => 5
2025-08-29 15:10:14,780 - main - INFO - PlaySpace[28] None => 180
2025-08-29 15:10:14,780 - main - INFO - PlaySpace[29] None => 180
2025-08-29 15:10:14,780 - main - INFO - PlaySpace[30] None => 180
2025-08-29 15:10:14,781 - main - INFO - {'global': {1: 1}, 'LHR-26757EC5': {1: 10, 2: 9, 3: 10, 4: 6, 5: 6, 6: 6, 7: -12, 8: -12, 9: -12, 10: -180, 11: -180, 12: -180, 13: -5, 14: 0, 15: -5, 16: -180, 17: -180, 18: -180, 19: 12, 20: 12, 21: 12, 22: 180, 23: 180, 24: 180, 25: 5, 26: 5, 27: 5, 28: 180, 29: 180, 30: 180}, 'PlaySpace': {1: 10, 2: 9, 3: 10, 4: 6, 5: 6, 6: 6, 7: -12, 8: -12, 9: -12, 10: -180, 11: -180, 12: -180, 13: -5, 14: 0, 15: -5, 16: -180, 17: -180, 18: -180, 19: 12, 20: 12, 21: 12, 22: 180, 23: 180, 24: 180, 25: 5, 26: 5, 27: 5, 28: 180, 29: 180, 30: 180}}

I think it's almost there; it just needs more robustness and error handling. For example, your troubleshooting:

Ensure only one ObjectTracking.exe is running (Task Manager)

Could be automated or print an error and quit if it detects another running.

Restart VRChat if ObjectTracking was started afterward

This is unreasonable; the server app should be able to handle disconnects/reconnects.

Reset OSC config (AM > Options > OSC > Reset Config)

Turning OSC off and on in VRChat has helped sometimes.

Switch avatar

Reasonable and helps.

Close all VRChat UIs

Reasonable.

Nudge your thumbstick to move a bit forward

Reasonable.

When I did have it working it only worked on the initial world and when I switched it stopped working altogether, which is unreasonable.

[Hackebein]

Thanks for the feedback.

I saw the live updates from Unity direct from the SteamVR tracking data when clicking/holding the mouse

This is a Unity things. You need to set your scene to always update. I have it already on my todo list to set it automatic.

The release exe for the app breaks with a key error and stops working

Switch worlds I get [...]

It shows an error but it shouldnn't break. Please provide details if it stops working.

I have only sporadically seen the tracker moving in VRChat, when I switched to a different world it stopped working

That should not be. Switching Worlds/Avatars shouldn't make it stop working. Please provide details if it stops working.

Removing the gameObject with component borks the project, likely from VRCFury settings e.g. (BlendTree "processing" in state "Remote" in Controller "[FX]" uses parameter "ObjectTracking/Scale" which does not exist.)

I don't know how you managed to generate any animator state without component. If you have steps to reproduce this issue, please share them with me.

Removing the hackebin from VRCC still the project is borked
Readding it fixed it

After removing the package you might have left over components in some gameobjects in your hierarchy. That's something you need to manage yourself.

I have it tracking again in the first world, but toggling the trackers/playspace doesn't turn them off

I will check on that. I haven't looked into that function for a while.

and the position/orientation doesn't match the trackers in steamvr

Can you provide more details please?

Ensure only one ObjectTracking.exe is running (Task Manager)

Could be automated or print an error and quit if it detects another running.

This would require additional permissions and should only happen if the user does something manually. I expect that object tracking will just start with SteamVR, and closes with SteamVR automatic. There should be no user action involved.

Restart VRChat if ObjectTracking was started afterward

This is unreasonable; the server app should be able to handle disconnects/reconnects.

It does already. Anyway there were some user who had issues and somehow only a restart worked.

When I did have it working it only worked on the initial world and when I switched it stopped working altogether, which is unreasonable.

This shouldn't be the case. Please provide details.

[DrBenStoneSage]

Thanks for the reply, I'll give another thorough error report next week when I try it again.