c-frame/aframe-extras

Add-ons and helpers for A-Frame VR.

aframe-extras's Issues

Use CannonDebugRenderer for debugging view

Looks more robust than the current wireframe generation.

Categorize VR-friendly controls?

Badges or something? Would be best to be explicit about more FPS-oriented controls.

Controls tracking bugs

• 333 (zqsd)
• 589 (arrow keys)
• 621 (mouse+HMD issues)
• 809 (vertical wasd)
• 998 (deltas)
• 293 (mouse drag stops outside of canvas)
• 814 (look-controls movement axes)

animations w/ collision detection

i'd like for animated objects like platforms to detect collisions and stop, reverse, or something. maybe force-based animations? not sure how this should work. might be a new component or two.

model loading and error indicators

model loading + error indicators (aframevr/aframe#423, aframevr/aframe#424)

physics component demo gif

would be fun to do a gif showing before/after *-body components are added. add to readme or the twitters or something.

Support Cannon compound shapes

Proposed API:

<a-entity collada-model="src: url(chair.dae)" dynamic-body="shape: compound; mass= 10;">
  <!-- Back -->
  <a-body-part shape="box" width="0.1" height="1" depth="1" offset="0.5 0.5 0"></a-body-part>
  <!-- Seat -->
  <a-body-part shape="box" width="1" height="0.1" depth="1" offset="0 0 0"></a-body-part>
  <!-- Legs -->
  <a-body-part shape="cylinder" height="1" radius="0.1" offset="0.5 -0.5 0.5"></a-body-part>
  <a-body-part shape="cylinder" height="1" radius="0.1" offset="0.5 -0.5 -0.5"></a-body-part>
  <a-body-part shape="cylinder" height="1" radius="0.1" offset="-0.5 -0.5 -0.5"></a-body-part>
  <a-body-part shape="cylinder" height="1" radius="0.1" offset="-0.5 -0.5 0.5"></a-body-part>
</a-entity>

Publish separate packages on NPM?

Might be a pain to publish them all, but worth a try.

Convex Hull support

Provides a more robust alternative to Trimesh shapes.

THREE.js QuickHull implementation

Also: http://www.bennolan.com/2014/07/24/physics,-hulls-and-cannon.js.html

Cylinders don't work w/ physics in Safari.

I have no idea. 😒

better docs!

any docs, really.

path

take interpolation points, animate around w/ constant velocity.

bonus: block on collision.

Physics breaks if page loads without focus

Detects one collision up front, and then never again. :/

controls require position / velocity

not friendly

Improve installation instructions

Global script docs are missing, and the NPM docs assume users already know browserify/webpack. Should fix both of those.

Primitive property aliases broken?

From Erica – <a-ocean/>'s color doesn't work in Firefox but density only works in Firefox. Maybe a bug with the registerPrimitive API... or I'm setting material too late somehow?

prevent velocity forcing through obstacles

order of update, or something?

example with particle effects

easy enough, would probably help others to post some examples

fix kinematic-body height on landing/collision

v2.0.0

• Drop fbx-model (too many issues)
• ???

device orientation + position

https://developer.mozilla.org/en-US/docs/Web/API/Detecting_device_orientation#Processing_motion_events

all signs point to this being a non-starter, but it'd be interesting (and not too difficult, by the looks of the API) to test that out.

perspective don't feel good

in the monument example, VR camera perspective feels off

too close to the floor, maybe.

Physics body scaling could not be applied.

Heya, what's the plan with physics body scaling. I'm getting it with an entity that is a box that I'm scaling. It's easy for me to refactor the code to set the width height and depth in this instance, but it'd be nice to support scaling for scenes that are created in the editor. I could write a PR that manually scales elements by calling multiplyScalar on all the vertices? That'll be expensive if the scale is constantly changing, but should be fine for bodies that are scaled on creation but otherwise don't change.

Offset player sphere, decrease size.

If the player sphere can be offset (will this screw with weight distribution?) we can reduce its radius and have more reasonable collisions.

Or maybe the camera frustum just needs adjustment? Not sure what the issue was here. The offset on every tick is silly though, a shape-wise offset would be better.

Publish examples on github.io

It'd be nice to be able to view them and show them as references without having to clone and build them locally first.

create dist builds

w/ separate files for each package, and full package options

component dependancies

In trying out different combinations of the extras, I found that Controls requires Math. Which makes complete sense, but the error 'null defined for v.x' threw me for a bit.

Is there a way of requiring/registering one component from another?

Alternatively, a note or dependency graph (I haven't tried other combinations) could be helpful.

collide event support

current example

el.components['dynamic-body'].body.addEventListener('collide', function (e) {
  // ...
});

Add support for more physics primitives.

Notably, Cannon.js supports cylinders and spheres, so it would be trivial to support these. Heightfields could also be interesting.

sphere physics radius does not adjust to fit

Allow play/pause of physics

At component or system level. Would allow dynamic bodies to be moved, use w/ editor, etc.

Spotify iframe not visible

Collision box on a obj model is much too big

I'm putting the attached model in my scene and the physics model is much bigger than the model. I'm guessing I'm doing something wrong? I've enabled physics debugging.

Add link component

Multiple questions in slack about how to do this / it's dead simple. Bonus points for fade out animation?

Use require() to load subpackage dependencies

not this.extras.*.registerAll()

i have no idea why i didn't do that in the first place

implement gltf-model

See: aframevr/aframe#819

Player keeps moving when using movementEnabled: false

When using an element like:

<a-entity camera kinematic-body />

And I programmatically set

setAttribute('universal-controls', 'movementEnabled: false')

The player keeps rolling at the speed it was travelling before. You have to stop the player completely before disabling movement. It'd be better if the player rolled to a stop even if you have movementEnabled set to false.

Sound effects on collision?

Very yes.

hmd controls broken

Investigate dealing with nested entities & local positions

Body components naively assume position will return absolute world coordinates, which breaks if nested inside another entity with a position.

THREE.js has an API for returning world position. Could enable this by default (if there are no performance implications), or enable an option allowing it on a case-by-case basis. Might by trickier for dynamic-body than static-body.

physics terrain w/ heightmaps

also http://mrdoob.github.io/three.js/examples/webgl_terrain_dynamic.html
and http://danni-three.blogspot.com/2013/09/threejs-heightmaps.html

Add debug / silence errors

• gamepad not found
• physics updates
• physics body loaded

Obj/Collada models fall through with dynamic/static-body

Test at http://anj.fyi/mountains

The manatee falls through the floor, and the mountain mesh isn't walkable.

Link to models:
http://anj.fyi/images/manatee.obj
http://anj.fyi/images/mountains.dae

Add animated water component 🌊

really cute tutorial here, which should work well for a flat-shaded style

Ex:

<a-water/>

... which automatically creates a plane + custom component that applies sin-wave animation to the vertexes on the geometry.

streetview pano component

Shadows

Post here: http://blog.vizor.io/using-lights-and-shadows/

Suggesting directional and hemisphere lights perform (much) better than point or spot lights, when used with shadows. Also:

"Generally, for best performance : quality ratio, it is recommended to use one directional light and either an Ambient Light or a Hemisphere Light to get a nice lighting effect with shadows."

Spotify player covers screen in VR mode on iOS

... @moyicat has weird preferences like wanting to see things while in VR 😑

(monument demo)

grabby physics interaction

Inspiration: http://newtonvr.com –

Our system allows players to pick up, drop, throw, and use held objects. Items don't pass through other items (rigidbodies), or the environment (non-rigidbodies). Rather, held items interact with other rigidbodies naturally - taking mass into account. For example, if you have two boxes of the same mass they can push each other equally, but a balloon, with considerably less mass, can't push a box. For more information on this style of mass-based interaction, see this post by Nick Abel.

Items can be configured to be picked up at any point, or when grabbed, can rotate and position themselves to match a predefined orientation. This lets you pick up a box from its corner as well as pick up a gun and have it orient to the grip.

monuments example broken

was working at v1.0.0, I need to get it updated with all the physics/controls changes.

Twitter webview broken in iOS

min/max zoom issue :|