<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Works now, thanks a bunch!</p>
<p>I bow to your superior debugging skills.</p>
<p>Do you have a Patreon site?</p>
<p>John<br>
</p>
<div class="moz-cite-prefix">On 7/5/21 8:41 AM, John Carlson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:404c3284-e6ad-b4a5-b1b2-4170314e593c@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Oh! I reported this again. Sorry folks for duplicate.<br>
</p>
<div class="moz-cite-prefix">On 7/5/21 6:08 AM, Holger Seelig
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:EF41142D-8366-4DDD-8674-926E4E3BBC6F@yahoo.de">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<a href="https://localhost:3000/src/main/html/bubbles.html"
class="" moz-do-not-send="true">https://localhost:3000/src/main/html/bubbles.html</a>
<div class=""><br class="">
</div>
<div class="">has a flashing because the event order is not
determined. The TimeSensor sends a fraction_changed (value 0)
and a cycleTime (value currentTime) event at the same time,
but you don’t know in which order. It looks like that the
interpolators get the fraction_changed event earlier than the
new keyValues. That means the first frame is from the old
keyValues. The solution is to send an (new) fraction_changed
event with value 0 in you script after the position and
orientation is set. See attachment with fixed bubbles.x3d.
<div class=""><br class="">
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
</blockquote>
</blockquote>
</body>
</html>