<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>
      As Mike points out 20ms is significant. As 60fps, the system needs
      to generate a new frame every 16.6ms. Desired is > 90fps (or
      < 11.1ms/frame). Could the DOM event be getting held up until
      after a frame is generated (20ms = 50fps)?<br>
      <br>
      <br>
      Leonard Daly<br>
      <br>
      <br>
      <br>
    </div>
    <blockquote
      cite="mid:2037c542-880d-58ea-01b4-b03cf24f80c4@noegenesis.com"
      type="cite">
      <meta content="text/html; charset=windows-1252"
        http-equiv="Content-Type">
      <p>If we take WebVR into consideration, these types of delays are
        significant.</p>
      <p>Do you anticipate problems?  End to end system delay in VR
        systems must be 20 milliseconds or less to avoid simulator
        sickness.<br>
      </p>
      <br>
      <div class="moz-cite-prefix">On 10/30/16 7:59 AM, Andreas Plesch
        wrote:<br>
      </div>
      <blockquote
cite="mid:CAKdk67uRXscb13gBgs498HMVUUFALTZG8EdENeGTnk8pV0989g@mail.gmail.com"
        type="cite">
        <div dir="ltr">
          <div>
            <div>
              <div>
                <div>Hello,<br>
                  <br>
                </div>
                cobweb_dom v0.7 is now available. It has full support
                for ProtoInstance nodes and basic event tracing
                capability.<br>
                <br>
              </div>
              v0.7 requires the latest development cobweb.js, eg cobweb
              > 2.3 .<br>
              <br>
            </div>
            Event tracing to the console can be enabled by providing a
            'trace' attribute to the X3DCanvas element (with any value).<br>
            <br>
          </div>
          All output x3d events are logged. Here is an example:<br>
          <div>
            <div>
              <div>
                <div>
                  <div><br>
                    <div>
                      <div>1477837418917000: Background  x3d_isBound:
                        true<br>
                        1477837418918000: Background  x3d_bindTime:
                        1477837418.9007943<br>
                        1477837418919000: Viewpoint  x3d_isBound: true<br>
                        1477837418920000: Viewpoint  x3d_bindTime:
                        1477837418.9007943<br>
                        1477837421509000: CylinderSensor aroundX
                        x3d_isOver: true<br>
                        ...<br>
                        <br>
                      </div>
                      <div>(using <a moz-do-not-send="true"
href="https://andreasplesch.github.io/cobweb_dom//tests/interactiveTransformations.xhtml">https://andreasplesch.github.io/cobweb_dom//tests/interactiveTransformations.xhtml</a>
                        )<br>
                      </div>
                      <div><br>
                        The frontal time stamp is the DOM event creation
                        time stamp in microseconds produced by the web
                        browser and available to DOM event listeners.<br>
                      </div>
                      <div>It is interesting to see the difference
                        between the time stamp and say the bindTime of
                        the Background node, 18.918s - 18.901s = 17 ms<br>
                      </div>
                      <div>or for Viewpoint: 18.920 - 18.901 = 19 ms.<br>
                      </div>
                      <div>So it takes a bit for cobweb to call the
                        event callback which creates the DOM event.<br>
                      </div>
                      <div>When a DOM event listener captures the event,
                        it may be a little later again.<br>
                        With a fps of 30, a frame lasts 33ms.<br>
                      </div>
                      <div>It will be interesting to compare what time
                        stamps and values are reported with the x3d-edit
                        trace scripts.<br>
                      </div>
                      <div><br>
                      </div>
                      <div>-Andreas<br>
                      </div>
                      <div><br>
                        <br>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Sat, Oct 29, 2016 at 8:00 PM,
            Andreas Plesch <span dir="ltr"><<a
                moz-do-not-send="true"
                href="mailto:andreasplesch@gmail.com" target="_blank">andreasplesch@gmail.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <p dir="ltr">On Oct 29, 2016 6:20 PM, "Don Brutzman" <<a
                  moz-do-not-send="true" href="mailto:brutzman@nps.edu"
                  target="_blank">brutzman@nps.edu</a>> wrote:<br>
                ><br>
                > On 10/29/2016 2:21 PM, Andreas Plesch wrote:<br>
                >><br>
                >> [...]<br>
                >><br>
                >> Since logging all fields for all nodes becomes
                quickly a bit overwhelming, it would be a nice touch to
                be able select in the GUI which fields are traced (by
                default all).<br>
                ><br>
                ><br>
                > excellent idea.  not easily accomplished with
                current setup, but will keep it in mind as a future
                feature in X3D-Edit.<br>
                ><br>
                > for that matter, couldn't someone someday somewhere
                create such a widget in HTML that listened to all
                ROUTEs, as selected?  8)</p>
              <p dir="ltr">It should be possible find all elements
                referenced by fromNode attributes in ROUTE elements and
                attach event listeners with handlers which just log to
                the console. Let me give it a try.</p>
              <span class="HOEnZb"><font color="#888888">
                  <p dir="ltr">Andreas </p>
                </font></span></blockquote>
          </div>
          <br>
          <br clear="all">
          <br>
          -- <br>
          <div class="gmail_signature" data-smartmail="gmail_signature">Andreas
            Plesch<br>
            39 Barbara Rd.<br>
            Waltham, MA 02453</div>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
x3d-public mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<a moz-do-not-send="true" 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>
      <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>
    <p><br>
    </p>
    <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>
        LA ACM SIGGRAPH Chair<br>
        President, Daly Realism - <i>Creating the Future</i>
      </font></div>
  </body>
</html>