Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

SpatialController dependency/import issues

Open
#64 5 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, unity

Research direction

Start with the AccessoryTrackingHelper class and inspect the spatialcontroller package dependencies and the code around lines 7 and 14. Check whether the package compiles without Unity.VisualScripting or Unity.PolySpatial, then investigate the hand tracking description requirement in the XR project settings; done means unnecessary dependencies are not forced and the package works without unused hand tracking setup.

Written by the indexing model from the issue text.

Description

bug Plug-in - SpatialController

Couple of complaints about the spatialcontroller package, in the AccessoryTrackingHelper class

line 7
using Unity.VisualScripting;

this shouldn't be here - it's not used, but causes compile errors if you don't have that package. This seems like it's just clearly a bug/mistake

line 14
using Unity.PolySpatial;

We don't use polyspatial at all - polyspatial is added as a dependency to the package just to check if you are in a specific camera mode. It's so much extra bloat just for something we don't care about or need. I believe you can use "Version Defines" to make this code optional for people who have polyspatial in their project, rather than making it a forced dependency

Also, when using the package, it seems to require a hand tracking description - even though we aren't really using hand tracking. To make things slightly more annoying, the hand tracking description box in the xr project settings is greyed out if you don't have unity.xr.hands in your project

Dominant language
C#
Stars
986
Forks
252
Avg merge
1h 36m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apple/unityplugins

All issues in apple/unityplugins

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.