Jump to content

Babylonjs 3.1 release date ?


Recommended Posts

It's planned in less than 2 weeks.

In the meantime, you can already start to play with the latest VR features. I've finished them today. We still need to test/debug them more and write the doc but it should start to work well.

Some samples I've built to validate my use cases :

- GUI interactions: https://www.babylonjs-playground.com/#RVZ28K%237

  • Mansion VR : http://playground.babylonjs.com/#JA1ND3#15
    • You can teleport / rotate in this demo using the very same way as in the Mixed Reality Portal / Cliff House. 
    • When you point on interactive elements, it will change the size of the gaze, its color and the color of the laser pointer to indicate this is an actionable item. Active it using the trigger. 
    • You’ve got 3D spatial sounds
  • Knowing which mesh is currently selected with onNewMeshSelected http://playground.babylonjs.com/#JA1ND3#7
  • By default it returns all meshes, you can add your own filtering logic with meshSelectionPredicate : http://playground.babylonjs.com/#JA1ND3#12
    • In this sample, it will log only the red flags if you’re looking/pointing at it


Link to comment
Share on other sites

Use the main button (grab button on WMR controllers) to activate / desactivate the laser pointer on each controller and use the trigger to launch an action on a mesh or simulate pointerDown / up.

Everything work also using only a gamepad : gaze to select a mesh and button A to trigger an action / pointerDown, look on the floor and push the left stick forward to select teleport and release to be teleported.

I've tried to mimic as much as possible the CliffHouse experience.

Link to comment
Share on other sites

On 12/1/2017 at 2:26 PM, davrous said:

By default it returns all meshes, you can add your own filtering logic with meshSelectionPredicate

*all* is actually a single mesh (it does not look like a multipick on the ray cast) - the documentation will need to be helpful here.  Also, this raycast includes any invisible or unpickable meshes in front of the gaze, of which the first will be picked, so it does not work the same by default as ray casting:

I spent some time confused why my meshes weren't being selected as they were "blocked" by an unpickable!  As it is now, it does not feel to me as intuitive or consistent as it could be in that use case :) I am only voicing here to make sure this is intentional as the backwards compatibility can make that awkward to change afterwards.  Really appreciate all your hard work here - it is a fantastic feature - by far my favourite in 3.1!! Thank-you.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...