Fernando Serrano

@netpro2k sorry I forgot about it. Could you rebase it and I'll merge? thanks! :)

Could you share a codepen or a link to your app so I could take a look on how are you using it. Is your controller in the right position...

Based on https://github.com/fernandojsg/aframe-input-mapping-component/issues/12 what do you think about something like: ```json { "trackpaddown": "startTeleport", "axisMove[@state=startTeleport]": "rotateForwardVector", "trackpadup": "endTeleport" } ``` So on `trackpaddown` the ray will appear, then you could...

Other option is to create another `inputMapping` while you're on `aiming/startTeleport`, maybe more verbose, but: ``` teleport: { "trackpaddown": "startTeleport", }, aiming: { axisMove: 'rotatingForward', "trackpadup": "endTeleport" } ```

This is highly related to the latest comments by @johnshaughnessy on https://github.com/fernandojsg/aframe-input-mapping-component/issues/2

Yep, the more I check the syntax with custom attributes and so on, the less I like it. It's a complex problem, I'm not sure how they solve it on...

I like it! Just a question, what is the expected use of `now()` if fixedTime is enabled? maybe is safer to return elapsedTime in that case? as it could be...

So in that case I agree on making `now()` private

@cvan still having some issues after the update to 0.6.1, I'll work on it with @dmarcos this week

@alfa256 can you give it a try to the current deployed version? Also, did you manage to get other three.js examples to work on your mobile?