add physics example

[vincentfretin]

Add a physics example with ammo driver.
refs #193

[vincentfretin]

There is a more complex example by @diarmidmackenzie using a modified version of super-hands compatible with the ammo driver at https://black-and-white-friends.surge.sh/pages/
See also
https://github.com/diarmidmackenzie/aframe-super-hands-component/blob/master/examples/physics/index-ammo.html that is available at https://terrific-minute.surge.sh/examples/physics/index-ammo.html
(link taken from the discussion about the different super-hands forks with ammo compatibility)

[vincentfretin]

Note that with aframe 1.1.0 or 1.2.0 and aframe-physics-system 4.0.1, there are infinite warnings "THREE.Quaternion: .inverse() has been renamed to invert()." when you open the console, see n5ro/aframe-physics-system#183

[vincentfretin]

If you want a wall to block your avatar, you need a nav-mesh
see https://github.com/n5ro/aframe-extras/tree/master/src/pathfinding
and something like this

      <a-entity id="navmesh" gltf-model="navmesh.gltf" visible="false" nav-mesh></a-entity>
      <a-entity id="player" movement-controls="constrainToNavMesh: true"

But this is currently broken with aframe 1.2.0, you may stick with 1.1.0 for now, see c-frame/aframe-extras#349

[vincentfretin]

Also there is a #physics channel on Slack, see this thread https://aframevr.slack.com/archives/C3WGUL4K0/p1617736493000900 with the status of the different physics engine.

[vincentfretin]

Also for this particular example in this PR, we shouldn't be able to move a cube if we don't own it. I'll fix that later.

[n5ro]

I'm still working on a fix to navmesh https://glitch.com/edit/#!/navmesh1
https://glitch.com/edit/#!/navmesh
https://glitch.com/edit/#!/navmesh2

Feel free to read the commented code in each index file for details. I am trying to replace Three.Geometry which has been deleted from threejs with BufferGeometry. I could use some help testing this and writing this code, please remix the links and try to get it working also. In the meantime use Aframe 1.1.0 with A-Frame Extras until we get this fixed.

[vincentfretin]

With the example, the second user doesn't see the cube. Actually it's there but the cube is dropping indefinitely :D

document.querySelector('.cube').getAttribute('position')
Object { x: 0.37061196913538613, y: -22879.074609375, z: -0.39367493127928344, … }

I think the static ground is not initialized before the cube is spawned by networked-aframe. Using connectOnLoad:false and clicking a button to enter the room may fix the issue. I didn't test.

[vincentfretin]

About my comment #270 (comment)
"We shouldn't be able to move a cube if we don't own it".
Actually it may be better to listen to the collide event and call takeOwnership on the cube.

Contributions to this example are welcome. I won't be working on it right now.

[kylebakerio]

About my comment #270 (comment)
"We shouldn't be able to move a cube if we don't own it".
Actually it may be better to listen to the collide event and call takeOwnership on the cube.

yes, this is definitely how I've envisioned it should work

[kylebakerio]

Just a heads up, I was able to get aframe-physics-system working with super hands in A-Frame 1.2.0 here today (using standard CANNON instead of AMMO): n5ro/aframe-physics-system#187 (comment)

Figure that might be helpful in moving this forward. I'm interested in helping with this (and responding and continuing on the networked controllers pull request), just swampped with work right now.

[n5ro]

Thank's Kyle, I'm also swamped with a book I am writing between now and November, but I can send you a video I think that illustrates some of the problems we have identified in Aframe Physics System that I think we can fix if we apply our minds with time and effort to it. I should probably cut the video to the minimum before linking it here on github. I will try to do this soon.

On Sat, Aug 28, 2021 at 3:53 PM Kyle Baker ***@***.***> wrote: Just a heads up, I was able to get aframe-physics-system working with super hands in A-Frame 1.2.0 here today (using standard CANNON instead of AMMO): n5ro/aframe-physics-system#187 (comment) <n5ro/aframe-physics-system#187 (comment)> Figure that might be helpful in moving this forward. I'm interested in helping with this (and responding and continuing on the networked controllers pull request), just swampped with work right now. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#270 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALABUCNDD23X7EEGCIRAFUTT7FSHPANCNFSM42WWSLNA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

--

…

-- Sincerely, Micah Blumberg Journalist, Researcher, Neurohacker Silicon Valley Global News (Science & Technology News), VRMA.io Virtual Reality Magazine (WebXR based news), Aframe WebXR Online Hacknight, The Neural Lace Podcast http://svgn.io http://vrma.io meetup.com/virtualreality/events github.com/micah1 github.com/n5ro San Francisco Virtual Reality (events) Social Media Accounts in order of use 1: facebook.com/worksalt 2. twitter.com @WorkSalt 3. Instagram: micahsun 4. linkedin.com/in/worksalt/ Virtual Reality Oculus: cloudmicah

[kylebakerio]

@n5ro did you mean to respond here in the NAF pull request, or was that comment intended for the aframe-physics-system repo issue thread?

Either way, sounds good. Have you tried that fork, though?

[kylebakerio]

Just wanted to drop this thread here: https://discourse.threejs.org/t/preferred-physics-engine-cannon-js-ammo-js-diy/1565

I really feel like CANNON may have been too quickly dismissed by Diarmid there, as CANNON is generally regarded as having extremely realistic physics. Performance is also an issue in all physics libraries. CANNON does have the best documentation, though, of the physics libraries, from what I've read.

I also have been using that fork of aframe-physics-system mentioned in a prior comment successfully in a client project and that's still going well for me in 1.2.0.

[vincentfretin]

We can change the example I started to use CANNON instead of ammo if we have now a working version with aframe 1.2.0. I'll just be glad we have a more complete networked physics example with any physics engine. ;)

[vincentfretin]

@diarmidmackenzie published a NAF + Physics example here:
https://diarmidmackenzie.github.io/aframe-examples/compositions/networked-physics/