<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Andreas,<br>
      <br>
      This would also connect to the devices motion sensors. It is
      rather difficult in Cardboard mode to navigation with the
      touch-screen.<br>
      <br>
      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.<br>
      <br>
      I am not sure how Turntable differs from LookAt or Examine.  Is
      Turntable restricted to a single axis rotation?<br>
      <br>
      <br>
      Leonard Daly<br>
      <br>
      <br>
      <br>
      On 4/6/2016 2:19 PM, Andreas Plesch wrote:<br>
    </div>
    <blockquote
cite="mid:CAKdk67ubF3sLX=D71OZhKe-VD0MeOR7Di8yiA=jrn2nUJdbH+g@mail.gmail.com"
      type="cite">
      <p dir="ltr">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.<br>
        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.</p>
      <p dir="ltr">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.</p>
      <p dir="ltr">Finally, x3dom has a popular turntable mode which
        could be included in the spec.</p>
      <p dir="ltr">Andreas</p>
      <div class="gmail_quote"><br>
        <blockquote class="quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <br>
          Today's Topics:<br>
          <br>
             1. Mobile Responsive Navigation (Leonard Daly)<br>
             2. Stereographic Displays (Leonard Daly)<br>
             3. WebVR Community Group (Don Brutzman)<br>
          <br>
          <br>
----------------------------------------------------------------------<br>
          <br>
          Message: 1<br>
          Date: Wed, 6 Apr 2016 10:03:22 -0700<br>
          From: Leonard Daly <<a moz-do-not-send="true"
            href="mailto:web3d@realism.com">web3d@realism.com</a>><br>
          To: X3D Graphics public mailing list <<a
            moz-do-not-send="true" href="mailto:x3d-public@web3d.org"><a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a></a>>,<br>
                  "<a moz-do-not-send="true"
            href="mailto:x3dom-users@lists.sourceforge.net">x3dom-users@lists.sourceforge.net</a>"<br>
                  <<a moz-do-not-send="true"
            href="mailto:x3dom-users@lists.sourceforge.net">x3dom-users@lists.sourceforge.net</a>><br>
          Subject: [x3d-public] Mobile Responsive Navigation<br>
          Message-ID: <<a moz-do-not-send="true"
            href="mailto:5705415A.60407@realism.com">5705415A.60407@realism.com</a>><br>
          Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
          <br>
          Mobile devices have built-in motion detectors. These can be
          accessed<br>
          from JavaScript within a browser and used to control the
          viewing of a<br>
          scene. I have documented one way at<br>
          <a moz-do-not-send="true"
            href="http://realism.com/blog/tracking-device-motion"
            rel="noreferrer" target="_blank">http://realism.com/blog/tracking-device-motion</a>.
          This is a mechanism that<br>
          exists external from X3DOM, but is tightly couples to the
          browser<br>
          (access to the motion detectors) and X3DOM (for controlling
          the viewing).<br>
          <br>
          I feel that this capability is important to include directly
          in X3D V4.<br>
          This is a means of navigation, so my initial thought would be
          that this<br>
          would be an addition to the NavigationInfo node. There are two
          types of<br>
          this kind of navigation -- looking at an object (point in
          space) where<br>
          device motion is on a sphere with the object at the center;
          and looking<br>
          around where the device motion is at a fixed point and can
          orient to any<br>
          angle. In both of these cases, there is a fixed
          (non-translated) point<br>
          -- either the object, or the initial camera XYZ position.<br>
          <br>
          The 'type' field already as a "LOOKAT". In fact the spec
          document<br>
          (<a moz-do-not-send="true"
href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/navigation.html#NavigationInfo"
            rel="noreferrer" target="_blank">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/navigation.html#NavigationInfo</a>)<br>
          specifically describes how to navigate about an object in this
          manner<br>
          using '"LOOKAT" "EXAMINE"'. For this case, perhaps all that is
          needed is<br>
          to take (or at least allow) navigation control to come from
          the device.<br>
          Something like a new field "SFBool [in,out] navigationSensor
          FALSE".<br>
          <br>
          Comments?<br>
          <br>
          <br>
          --<br>
          *Leonard Daly*<br>
          X3D Co-Chair<br>
          Cloud Consultant<br>
          President, Daly Realism - /Creating the Future/<br>
          <br>
          -------------- next part --------------<br>
          An HTML attachment was scrubbed...<br>
          URL: <<a moz-do-not-send="true"
href="http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160406/5157af79/attachment-0001.html"
            rel="noreferrer" target="_blank">http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160406/5157af79/attachment-0001.html</a>><br>
          <br>
          ------------------------------<br>
          <br>
          Message: 2<br>
          Date: Wed, 6 Apr 2016 10:03:37 -0700<br>
          From: Leonard Daly <<a moz-do-not-send="true"
            href="mailto:web3d@realism.com">web3d@realism.com</a>><br>
          To: X3D Graphics public mailing list <<a
            moz-do-not-send="true" href="mailto:x3d-public@web3d.org"><a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a></a>>,<br>
                  "<a moz-do-not-send="true"
            href="mailto:x3dom-users@lists.sourceforge.net">x3dom-users@lists.sourceforge.net</a>"<br>
                  <<a moz-do-not-send="true"
            href="mailto:x3dom-users@lists.sourceforge.net">x3dom-users@lists.sourceforge.net</a>><br>
          Subject: [x3d-public] Stereographic Displays<br>
          Message-ID: <<a moz-do-not-send="true"
            href="mailto:57054169.5070702@realism.com">57054169.5070702@realism.com</a>><br>
          Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
          <br>
          This is related but not identical to my previous message
          "Mobile<br>
          Responsive Navigation"<br>
          <br>
          Using shaders it is possible to construct a stereographic
          display so<br>
          that a user can "see" in 3D. This can be assisted with tools
          such as<br>
          Cardboard, Oculus, GearVR, or many other items. I wrote a blog
          post on<br>
          this and how to create the various pieces at<br>
          <a moz-do-not-send="true"
            href="http://realism.com/blog/3d-google-cardboard"
            rel="noreferrer" target="_blank">http://realism.com/blog/3d-google-cardboard</a>.
          The code that does the<br>
          stereographic display is fully X3D as expanded by X3DOM to
          support<br>
          certain features.<br>
          <br>
          I feel that this capability is important to include directly
          in X3D V4.<br>
          This is a means of viewing, so my initial thought would be
          that this<br>
          would be an addition to the Viewpoint node. This method of
          generating<br>
          stereographics does require changes to the scene graph, so it
          might be<br>
          better to have a new node - StereoViewpont.<br>
          <br>
          The fields this nodes appears to require are:<br>
             SFFloat [in,out] interpupillaryDistance 0.03<br>
             <reference to scene or scene-fragment that is to be
          viewed in stereo><br>
          <br>
          There might be other fields (for example depth-of-field, zoom,
          etc.).<br>
          For mobile devices it is also necessary to handle device
          motion, so<br>
          whatever is defined needs to support mobile device tracking.<br>
          <br>
          <br>
          Comments?<br>
          <br>
          --<br>
          *Leonard Daly*<br>
          X3D Co-Chair<br>
          Cloud Consultant<br>
          President, Daly Realism - /Creating the Future/<br>
          -------------- next part --------------<br>
          An HTML attachment was scrubbed...<br>
          URL: <<a moz-do-not-send="true"
href="http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160406/95ed6e42/attachment-0001.html"
            rel="noreferrer" target="_blank">http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160406/95ed6e42/attachment-0001.html</a>><br>
          <br>
          ------------------------------<br>
          <br>
          Message: 3<br>
          Date: Wed, 6 Apr 2016 10:15:34 -0700<br>
          From: Don Brutzman <<a moz-do-not-send="true"
            href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>><br>
          To: X3D Graphics public mailing list <<a
            moz-do-not-send="true" href="mailto:x3d-public@web3d.org"><a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a></a>><br>
          Subject: [x3d-public] WebVR Community Group<br>
          Message-ID: <<a moz-do-not-send="true"
            href="mailto:57054436.50904@nps.edu">57054436.50904@nps.edu</a>><br>
          Content-Type: text/plain; charset="utf-8"; format=flowed<br>
          <br>
          Here is a potential W3C Community Group for X3D participation.<br>
          <br>
          <a moz-do-not-send="true"
            href="https://www.w3.org/community/webvr" rel="noreferrer"
            target="_blank">https://www.w3.org/community/webvr</a><br>
          ==========================================<br>
          > WebVR Community Group<br>
          > Our goal is to help bring high-performance Virtual
          Reality to the open Web.<br>
          ><br>
          > W3C note:<br>
          > 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.<br>
          ==========================================<br>
          <br>
          p.s. another W3C Community Group that was active for a while,
          but appears to have been inactive since 2013:<br>
          <br>
          <a moz-do-not-send="true"
            href="https://www.w3.org/community/declarative3d"
            rel="noreferrer" target="_blank">https://www.w3.org/community/declarative3d</a><br>
          ==========================================<br>
          > Declarative 3D for the Web Architecture<br>
          > 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<br>
           ve 3D g<br>
          raphics as part of HTML documents.<br>
          ==========================================<br>
          <br>
          all the best, Don<br>
          --<br>
          Don Brutzman  Naval Postgraduate School, Code USW/Br       <a
            moz-do-not-send="true" href="mailto:brutzman@nps.edu"><a class="moz-txt-link-abbreviated" href="mailto:brutzman@nps.edu">brutzman@nps.edu</a></a><br>
          Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   <a
            moz-do-not-send="true" href="tel:%2B1.831.656.2149"
            value="+18316562149">+1.831.656.2149</a><br>
          X3D graphics, virtual worlds, navy robotics <a
            moz-do-not-send="true"
            href="http://faculty.nps.edu/brutzman" rel="noreferrer"
            target="_blank"><a class="moz-txt-link-freetext" href="http://faculty.nps.edu/brutzman">http://faculty.nps.edu/brutzman</a></a><br>
          <br>
          <br>
          <br>
          ------------------------------<br>
          <br>
          Subject: Digest Footer<br>
          <br>
          _______________________________________________<br>
          x3d-public mailing list<br>
          <a moz-do-not-send="true" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br>
          <a moz-do-not-send="true"
            href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
            rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
          <br>
          <br>
          ------------------------------<br>
          <br>
          End of x3d-public Digest, Vol 85, Issue 14<br>
          ******************************************<br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
x3d-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
</pre>
    </blockquote>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <font class="tahoma,arial,helvetica san serif" color="#333366">
        <font size="+1"><b>Leonard Daly</b></font><br>
        3D Systems & Cloud Consultant<br>
        X3D Co-Chair on Sabbatical<br>
        LA ACM SIGGRAPH Chair<br>
        President, Daly Realism - <i>Creating the Future</i>
      </font></div>
  </body>
</html>