Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ar Vr placement issue #5158

Closed
ctdlg opened this issue Nov 21, 2022 · 3 comments
Closed

Ar Vr placement issue #5158

ctdlg opened this issue Nov 21, 2022 · 3 comments

Comments

@ctdlg
Copy link

ctdlg commented Nov 21, 2022

Entering AR or Vr buttons

  • A-Frame Version: 1.3.0
  • Platform / Device: oculus Quest 2, Samsung S7, OppoFind X3 pro, Samsung Tab
  • Reproducible Code Snippet or URL:
    Using aframe.min.js

AR and VR buttons overlap on smartphones and Oculus quest 2 browsers (problem appeared after browser upadates) Only if using embedded code !

I checked all your samples : you also get the same display problem. Your own example HERE does not display correctly on my oculus and my S7 !

Display is OK with Firefox.

We get ar/vr buttons overlap with Chrome or Oculus Quest 2 web browser.

Example 1

Example 2 on my website (use a smartphone...)

@dmarcos
Copy link
Member

dmarcos commented Nov 21, 2022

This is fixed in master now. Can make your own builds npm run dist

@ctdlg
Copy link
Author

ctdlg commented Nov 22, 2022

Thank you very much dmarcos,
It does display correctly now.
I did sponsor you : aframe is really great, I will use it a lot for VR + Oculus quest 2 !

Some more information for beginners ( I did search the meaning of npm run dist and how to !)
1 downloading the 1.3.0 from github
2 reading the README.md, starting line 170 ### npm
3 installed npm on my archlinux system
4 git clone https://github.com/aframevr/aframe.git
5 cd aframe
6 npm run dist
7 using aframe-master.js located in aframe/dist folder

@dmarcos
Copy link
Member

dmarcos commented Nov 22, 2022

@ctdlg Thanks. Much appreciated. Glad is working for you now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants