[x3d-public] Mobile Responsive Navigation
Leonard Daly
Leonard.Daly at realism.com
Wed Apr 6 21:09:18 PDT 2016
Andreas,
This would also connect to the devices motion sensors. It is rather
difficult in Cardboard mode to navigation with the touch-screen.
Tank mode (as you noted) does require two input devices. I have seen
some browser with a "slide" mode that is sort-of like that. A dual input
(look & motion) would be ideal. I am not sure how best to define
something like that. Especially for the case when there is only one
controller.
I am not sure how Turntable differs from LookAt or Examine. Is
Turntable restricted to a single axis rotation?
Leonard Daly
On 4/6/2016 2:19 PM, Andreas Plesch wrote:
>
> While "Examine" with and without "lookat" covers the object at center
> case, there is no mode which covers the looking around case. "Walk" or
> "Fly" usually mean looking in the direction of movement.
> So I think it would make sense to add a type 'Lookaround" which means
> that the camera can only change orientation not position. This is the
> typical cardboard VR mode.
>
> There is another mode which is sometimes called mouselook or tank
> mode. In it looking is independent from moving and typically requires
> two input devices: keyboard and mouse, or mouse and orientation sensor.
>
> Finally, x3dom has a popular turntable mode which could be included in
> the spec.
>
> Andreas
>
>
>
> Today's Topics:
>
> 1. Mobile Responsive Navigation (Leonard Daly)
> 2. Stereographic Displays (Leonard Daly)
> 3. WebVR Community Group (Don Brutzman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 6 Apr 2016 10:03:22 -0700
> From: Leonard Daly <web3d at realism.com <mailto:web3d at realism.com>>
> To: X3D Graphics public mailing list <x3d-public at web3d.org
> <mailto:x3d-public at web3d.org>>,
> "x3dom-users at lists.sourceforge.net
> <mailto:x3dom-users at lists.sourceforge.net>"
> <x3dom-users at lists.sourceforge.net
> <mailto:x3dom-users at lists.sourceforge.net>>
> Subject: [x3d-public] Mobile Responsive Navigation
> Message-ID: <5705415A.60407 at realism.com
> <mailto:5705415A.60407 at realism.com>>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Mobile devices have built-in motion detectors. These can be accessed
> from JavaScript within a browser and used to control the viewing of a
> scene. I have documented one way at
> http://realism.com/blog/tracking-device-motion. This is a
> mechanism that
> exists external from X3DOM, but is tightly couples to the browser
> (access to the motion detectors) and X3DOM (for controlling the
> viewing).
>
> I feel that this capability is important to include directly in
> X3D V4.
> This is a means of navigation, so my initial thought would be that
> this
> would be an addition to the NavigationInfo node. There are two
> types of
> this kind of navigation -- looking at an object (point in space) where
> device motion is on a sphere with the object at the center; and
> looking
> around where the device motion is at a fixed point and can orient
> to any
> angle. In both of these cases, there is a fixed (non-translated) point
> -- either the object, or the initial camera XYZ position.
>
> The 'type' field already as a "LOOKAT". In fact the spec document
> (http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/navigation.html#NavigationInfo)
> specifically describes how to navigate about an object in this manner
> using '"LOOKAT" "EXAMINE"'. For this case, perhaps all that is
> needed is
> to take (or at least allow) navigation control to come from the
> device.
> Something like a new field "SFBool [in,out] navigationSensor FALSE".
>
> Comments?
>
>
> --
> *Leonard Daly*
> X3D Co-Chair
> Cloud Consultant
> President, Daly Realism - /Creating the Future/
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160406/5157af79/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 6 Apr 2016 10:03:37 -0700
> From: Leonard Daly <web3d at realism.com <mailto:web3d at realism.com>>
> To: X3D Graphics public mailing list <x3d-public at web3d.org
> <mailto:x3d-public at web3d.org>>,
> "x3dom-users at lists.sourceforge.net
> <mailto:x3dom-users at lists.sourceforge.net>"
> <x3dom-users at lists.sourceforge.net
> <mailto:x3dom-users at lists.sourceforge.net>>
> Subject: [x3d-public] Stereographic Displays
> Message-ID: <57054169.5070702 at realism.com
> <mailto:57054169.5070702 at realism.com>>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> This is related but not identical to my previous message "Mobile
> Responsive Navigation"
>
> Using shaders it is possible to construct a stereographic display so
> that a user can "see" in 3D. This can be assisted with tools such as
> Cardboard, Oculus, GearVR, or many other items. I wrote a blog post on
> this and how to create the various pieces at
> http://realism.com/blog/3d-google-cardboard. The code that does the
> stereographic display is fully X3D as expanded by X3DOM to support
> certain features.
>
> I feel that this capability is important to include directly in
> X3D V4.
> This is a means of viewing, so my initial thought would be that this
> would be an addition to the Viewpoint node. This method of generating
> stereographics does require changes to the scene graph, so it might be
> better to have a new node - StereoViewpont.
>
> The fields this nodes appears to require are:
> SFFloat [in,out] interpupillaryDistance 0.03
> <reference to scene or scene-fragment that is to be viewed in
> stereo>
>
> There might be other fields (for example depth-of-field, zoom, etc.).
> For mobile devices it is also necessary to handle device motion, so
> whatever is defined needs to support mobile device tracking.
>
>
> Comments?
>
> --
> *Leonard Daly*
> X3D Co-Chair
> Cloud Consultant
> President, Daly Realism - /Creating the Future/
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160406/95ed6e42/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 6 Apr 2016 10:15:34 -0700
> From: Don Brutzman <brutzman at nps.edu <mailto:brutzman at nps.edu>>
> To: X3D Graphics public mailing list <x3d-public at web3d.org
> <mailto:x3d-public at web3d.org>>
> Subject: [x3d-public] WebVR Community Group
> Message-ID: <57054436.50904 at nps.edu <mailto:57054436.50904 at nps.edu>>
> Content-Type: text/plain; charset="utf-8"; format=flowed
>
> Here is a potential W3C Community Group for X3D participation.
>
> https://www.w3.org/community/webvr
> ==========================================
> > WebVR Community Group
> > Our goal is to help bring high-performance Virtual Reality to
> the open Web.
> >
> > W3C note:
> > Community Groups are proposed and run by the community. Although
> W3C hosts these conversations, the groups do not necessarily
> represent the views of the W3C Membership or staff.
> ==========================================
>
> p.s. another W3C Community Group that was active for a while, but
> appears to have been inactive since 2013:
>
> https://www.w3.org/community/declarative3d
> ==========================================
> > Declarative 3D for the Web Architecture
> > The mission of the Declarative 3D for the Web Architecture
> Community Group is to determine the requirements, options, and use
> cases for an integration of interactive 3D graphics capabilities
> into the W3C technology stack. This group is aimed to extract core
> features out of the requirements as foundation to propose feasible
> technical solutions. These should cover the majority of 3D use
> cases for the Web - but not necessarily all of them. There are
> upcoming open (e.g., WebGL) and proprietary (e.g., Adobe)
> proposals for imperative graphics APIs in the Web context but we
> are missing an easy way to add interactive high-level declarative
> 3D objects to the HTML-DOM to allow anyone to easily create,
> share, and experience interactive 3D graphics - with possibly wide
> ranging effects similar to those caused by the broad availability
> of video on the Web. The goal of this CG is to evaluate the
> necessary requirements for a successful standardization of a
> declarative approach to interacti
> ve 3D g
> raphics as part of HTML documents.
> ==========================================
>
> all the best, Don
> --
> Don Brutzman Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu <mailto:brutzman at nps.edu>
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA
> +1.831.656.2149 <tel:%2B1.831.656.2149>
> X3D graphics, virtual worlds, navy robotics
> http://faculty.nps.edu/brutzman
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org <mailto:x3d-public at web3d.org>
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
> ------------------------------
>
> End of x3d-public Digest, Vol 85, Issue 14
> ******************************************
>
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
--
*Leonard Daly*
3D Systems & Cloud Consultant
X3D Co-Chair on Sabbatical
LA ACM SIGGRAPH Chair
President, Daly Realism - /Creating the Future/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160406/94b46e45/attachment-0001.html>
More information about the x3d-public
mailing list