From 9cfa6aaa9e92e4955dc86b005cd0d490c9dade46 Mon Sep 17 00:00:00 2001 From: Vincent Fretin Date: Sun, 17 Dec 2023 15:30:09 +0100 Subject: [PATCH] Update version in doc --- README.md | 4 ++-- docs/getting-started-local.md | 12 ++++++------ examples/shooter-ar.html | 2 +- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index c9808736..af317d3e 100644 --- a/README.md +++ b/README.md @@ -72,10 +72,10 @@ Basic Example My Networked-Aframe Scene - + - + diff --git a/docs/getting-started-local.md b/docs/getting-started-local.md index e9c1d023..23da6989 100644 --- a/docs/getting-started-local.md +++ b/docs/getting-started-local.md @@ -36,7 +36,7 @@ Now let's setup the required dependencies. Create a file called `package.json` a }, "author": "YOUR_NAME", "dependencies": { - "networked-aframe": "^0.11.0" + "networked-aframe": "^0.12.0" } } ``` @@ -110,10 +110,10 @@ Here's the template we'll start with: ```html - + - + @@ -122,8 +122,8 @@ Here's the template we'll start with: ``` Please don't use `https://unpkg.com/networked-aframe/dist/networked-aframe.min.js` for production, this will download the latest major release that may contain breaking changes. -It's ok for a testing environment to specify "@^0.11.0" in the url so it downloads the latest minor version that shouldn't have breaking changes. -For production you want to pin to a specific version like `https://unpkg.com/networked-aframe@0.11.0/dist/networked-aframe.min.js`. +It's ok for a testing environment to specify "@^0.12.0" in the url so it downloads the latest minor version that shouldn't have breaking changes. +For production you want to pin to a specific version like `https://unpkg.com/networked-aframe@0.12.0/dist/networked-aframe.min.js`. If you want to use a more recent build from github master that is not released yet, you can use: @@ -313,7 +313,7 @@ I'm planning on writing a follow-up tutorial to this one that will explain how t ### Syncing Custom Components -Components are synchronized by comparing the state of a component [provided by A-Frame](https://aframe.io/docs/0.7.0/core/entity.html#getattribute-componentname) on a network 'tick'. How quickly this tick happens can be defined in the [NAF Options](https://github.com/networked-aframe/networked-aframe#options), but the default is 15 times per second. On each tick the state is checked against its previous value, and if it changed it's sent over the network to the other users. +Components are synchronized by comparing the state of a component [provided by A-Frame](https://aframe.io/docs/1.5.0/core/entity.html#getattribute-componentname) on a network 'tick'. How quickly this tick happens can be defined in the [NAF Options](https://github.com/networked-aframe/networked-aframe#options), but the default is 15 times per second. On each tick the state is checked against its previous value, and if it changed it's sent over the network to the other users. So how do we choose which components to sync? By default, the `position` and `rotation` components are synced but NAF lets you specify any component that you wish to sync, included child components found in the deep depths of your templates. diff --git a/examples/shooter-ar.html b/examples/shooter-ar.html index 98717069..bfc24b68 100644 --- a/examples/shooter-ar.html +++ b/examples/shooter-ar.html @@ -4,7 +4,7 @@ Shooter AR Example — Networked-Aframe - +