incompatibleFeatureTypes for Quest features

Open
#15 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
csharp, unity

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.

Description

Ideally we'd have a single build for all android devices. We are tantalisingly close so it's slightly disheartening to see this:

https://github.com/ValveSoftware/Unity/blob/b933e9322ff1ebd60914e90f6496314dc7044dfb/com.valvesoftware.openxr.utils/Runtime/Features/ValveOpenXRLeptonValidationFeature.cs#L30

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)

Dominant language
C#
Stars
64
Forks
3
Avg merge
1m
Merged PRs (30d)
3

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 ValveSoftware/Unity

All issues in ValveSoftware/Unity

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.