aframevr / aframevr/aframe

Issue with VR on mobile (cardboard) no collision with geometry on cubemaps

Open
#4,598 0 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

Description:

  • A-Frame Version: 1.0.4 (now tested on master)
  • Platform / Device: (issue only on) Android with Chrome 80+ (since vr services stuff)
  • Reproducible Code Snippet or URL: https://xenodochial-neumann-ca5065.netlify.app/ you can check DOM how it's built, but i can share you whatever else you want, mostly it's from CDN, VR since new chrome doesnt use any custom interface, colission (raycaster) elements are visible in DOM (at the bottom in scence)

Short description: Since Android Chrome 80+ we found and issue that our raycaster doesn't work with LINK(geometry) the circle... anymore. On iPhone + Chrome it works, Android + Firefox works... but now VR on Android Chrome 80+ needs some extra permissions to use and got different view than before like 120hz, with default SETUP cog and arrow back.

I don't really know how to bring back the funcionality, but it's really important for our big clients who uses cardboard option with their endusers.

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

Start with the linked Netlify reproduction and inspect the raycaster collision behavior for LINK geometry in the VR scene on Android Chrome 80+. Compare it with iPhone Chrome and Android Firefox, then verify that collision works in the cardboard view without regressing the working platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
ar-vr-xr, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.