Releases: AltspaceVR/aframe-altspace-component
Native Skeleton Parents and Synced Instantiation
A new set of components that allows you to parent a-frame entities to avatar skeleton joints:
- https://altspacevr.github.io/aframe-altspace-component/doc/native.n-skeleton-parent.html
- https://altspacevr.github.io/aframe-altspace-component/doc/native.n-cockpit-parent.html
And the ability to instantiate entities that are synced across clients:
- https://altspacevr.github.io/aframe-altspace-component/doc/sync.instantiator.html
- https://altspacevr.github.io/aframe-altspace-component/doc/sync.one-per-user.html
Examples:
v1.3.2 - Minor bug fixes
This patch release fixes a bug with the target
option on the wire
component. Additionally, source maps have been added to ease debugging.
v1.3.1 - n-mesh-collider fixes
The n-mesh-collider now creates colliders for external models (e.g. OBJ or Collada) that are loaded in to your app
v1.3.0 - n-sound-loaded event and rolloff property
- The n-sound component now emits an
n-sound-loaded
event when a sound is loaded and ready to be played - n-sound now has a
rolloff
property that determines the behavior of the volume attenuation - Added full paths to resources documentation
v1.2.1 - Minor bug fixes, improved documentation
- Fixed altspace component timing for calling updateAllBehaviors (Three.js integration)
- Added
target
(singular form) to wire component
v1.2.0 Native Components and Firebase Sync
As of today, AltspaceVR SDK developers can use A-Frame components to manipulate a variety of native AltspaceVR resources, including architectural building blocks, particle effects, physically blocking colliders, positional sounds, and more! Additionally, we've ported over our Firebase synchronization functionality from the Three.js SDK. These represent a huge jump in the power available to our developers, and we are very excited to see what you produce. For a complete description of the new features available, you should check out the updated A-Frame documentation, and the Native Components FAQ.
v1.1.1
Fix fullspace transition bug
v1.1.0 Add fullspace and cursor-collider flags
Merge pull request #13 from AltspaceVR/feature/fullspace Fullspace and cursor colliders in aframe
v1.0.0
Added the enclosuresOnly
flag, disabling altspace API calls if the app is loaded in a 2d display. This flag is true
by default, so this is technically a breaking change, therefore v1.0.0.
Aframe v0.3.0 support, with tracked controls!
Merge pull request #9 from AltspaceVR/feature/aframe-0.3.0 Feature/aframe 0.3.0