ValveSoftware / ValveSoftware/Unity
incompatibleFeatureTypes for Quest features
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 64
- Forks
- 3
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
Ideally we'd have a single build for all android devices. We are tantalisingly close so it's slightly disheartening to see this:
Can you explain in more detail exactly what is incompatible? What the effects are (maybe they are tolerable or can be mitigated)?
Is there a way to have runtime guards that solve the incompatibility and thus can coexist in the same build?
Is this maybe best regarded as a bug in the Quest SDK that needs to be reported (making the defensive code at least potentially temporary)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with com.valvesoftware.openxr.utils/Runtime/Features/ValveOpenXRLeptonValidationFeature.cs at line 30 and inspect how incompatible feature types are identified for Quest. Determine the effects, whether runtime guards could permit one build, and whether the behavior points to a Quest SDK bug; document the findings and any reproducible evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- game-dev, mobile-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100