larister / aframe-workshop

A-Frame and AR.js workshop

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

aframe-workshop

Examples

This workshop will teach you how to create A-Frame scenes to run on your phone and display Augmented Reality content using AR.js an emscripten port of ARToolkit

Prerequisites

Setup

In the following exercises you will follow along with the workshop instructor to create a series of web pages that allow you to view 3D content displayed over printed AR markers using your smartphone.

We will be using https://netlify.com to serve these web pages from a github repository. Netlify supports SSL (https) by default, which is necessary for accessing your phone's camera.

First create a github repository called aframe-workshop and clone it to your laptop. Make sure you select add readme so your repo isn't empty.

Now login to netlify.com and select New site from Git.

Choose GitHub.

Search for aframe-workshop and select it.

Click Deploy site using the default presets.

You will be directed to an overview page. Your site will have been given an auto-generated name e.g. https://dazzling-yalow-d3b2a0.netlify.com

Click this link to view your site. You will see a Page not found message. This is because we haven't pushed anything to our connected GitHub repo yet.

In your cloned repo, create a new file called index.html and type Hello world as the content.

Add index.html to git, commit, and push it.

git add index.html
git commit -m "initial commit"
git push origin master

Wait a few moments then refresh your netlify page. You should see Hello world. You now have everything you need to develop your web pages!

All exercises have examples here: https://github.com/edsilv/aframe-workshop/tree/master/ar

A-Frame documentation

AR.js documentation

Exercises

1. Cube

Create a 1-cube.html page. Use this "boilerplate" code:

<html>
  <head>
    <title>A-Frame Workshop</title>
    <script src="https://aframe.io/releases/0.9.2/aframe.min.js"></script>
    <script src="https://unpkg.com/ar.js@1.7.1/aframe/build/aframe-ar.min.js"></script>
  </head>

  <body style="margin: 0px; overflow: hidden;">
    <a-scene embedded arjs="sourceType: webcam;">
    </a-scene>
  </body>
</html>

Push it to your github repo's master branch. Now browse to your netlify site /cube.html.

You browser may prompt you to have access to your camera, click allow.

Goals

  • Display a 3D cube above the printed Hiro marker
  • Change the default size, position, rotation, and color of the cube
2. GLTF

Save your 1-cube.html as a new 2-gltf.html page, removing your cube from the scene.

Goals

  • Load a gltf model above the Hiro marker, e.g. https://nomad-project.co.uk/objects/collection/headrest/_headrest/headrest.gltf
  • Animate the rotation of the model about the Y (up) axis
  • Use <a-assets> to preload your gltf
  • Use debugUIEnabled: false; to remove debug message overlays
  • Use vr-mode-ui="enabled: false" to remove VR goggles toggle (not needed)
  • Use renderer="logarithmicDepthBuffer: true; colorManagement: true;"to fix z-fighting and enable colour management (otherwise gltfs don't display correctly)
  • Use loading-screen="dotsColor: white; backgroundColor: black" to create a customised loading screen
3. Custom Marker

Save your 2-gltf.html page as a new 3-custom-marker.html page, removing your gltf entity and a-marker-camera from the scene.

Goals

Notes

  • Set AR.js patternRatio: 0.66;: Aesthetically, it's preferable for the black border to match the Aruco grid pattern. patternRatio: 0.66; is needed as the marker ratio isn't 50%. A "Pattern Ratio 0.6" in the marker generator means that the pattern within the marker makes up 60% of the overall marker width (including border). For a 4x4 aruco the pattern ratio is 4/6 (4 grid items plus 2 sides of border). For a 5x5 it's 5/7 (5 grid items plus two sides of border), etc.
  • Use <a-entity camera></a-entity>
  • Models must be placed inside the a-marker tags
  • Better to use simple shapes for markers
  • Markers must not have rotational symmetry
  • Black borders seem to work best
  • Thicker borders are better for stability
  • Markers can be as small as 1.5/2cm but it means that the phone has to be held close
4. Multiple Markers

Save your 3-custom-marker.html page as a new 4-multiple-markers.html page.

Goals

5. Google Poly

Goals

7. Google Poly Search

Goals

  • Query objects in a particular category and display them over markers.
7. Google Poly User (unfinished)

Goals

next: add tilt brush scenes https://github.com/googlevr/poly-sample-web/blob/master/search-sample.html

About

A-Frame and AR.js workshop


Languages

Language:HTML 77.3%Language:JavaScript 22.7%