aframevr / aframevr/aframe

Two webxr projection layers?

Open
#4,880 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
17.6k
Forks
4.4k
PR merge metrics
No merged PRs in 30d

Description

Is it possible in current build of A-Frame to render two projection layers somehow?

I mean, quality of images in webxr layers is mind-blowing, but practically useless while hands/controllers are invisible as they drawn behind quad/cylindrical layer. The second most wanted feature after layers will be second projection layer on top of others (from second scene?).

Contributor guide

Open the contributing guide

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.

Research direction

No files, tests, or entry points are named. Start by reviewing A-Frame's current WebXR projection-layer handling and the WebXR layer constraints described by the issue. Done would mean a defined, supported way to render a second projection layer above the existing layer so hands and controllers remain visible.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
ar-vr-xr
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.