aframevr / aframevr/aframe

laser ray changes color to green (default color)

Open
#4,473 1 comment 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:
The color of the laser ray is white (defined color) for the first time when entering VR mode.
But it changes color to green (default color) for the following cases:

  1. if the headset is unmounted and mounted back again
  2. if the VR mode is exited and entered again
  • A-Frame Version: 1.0.4
  • Platform / Device: Oculus Browser in Oculus Quest
  • Reproducible Code Snippet or URL:
<head>
  <title>My A-Frame Scene</title>
  <script src="https://aframe.io/releases/1.0.4/aframe.min.js"></script>
  <script src="https://unpkg.com/aframe-environment-component@1.1.0/dist/aframe-environment-component.min.js"></script>
</head>
<body>
  <a-scene>
    <a-entity id="rig" position="0 0 0">
      <a-camera id="head" look-controls-enabled wasd-controls-enabled mouse-cursor cursor="rayOrigin: mouse"
      >
      </a-camera>
      <a-entity id="rightHand" laser-controls="hand: right" line="color: white; opacity: 0.75"
        raycaster="far: 10000">
      </a-entity>
    </a-entity>
    <a-entity environment="preset: contact"></a-entity>
  </a-scene>
</body>

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 provided A-Frame reproduction using laser-controls, line, raycaster, and the Oculus Browser on an Oculus Quest. Trace what happens to the line color when the headset is remounted or VR mode is re-entered; done means the configured white color remains instead of reverting to green in both cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.