<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>>>>>Summary:</div>
<div>>>>> - I think it would be better to start from scratch ie requirements gathering ... and make something just right for x3d multiplayer.</div>
<div>
<div> </div>
<div>Agree. I'd be glad to provide my intermediate results from hobby project SrrTrains v0.01 (using Network Sensor + BS Collaborate)</div>
<div> </div>
<div name="quote" style="margin: 10px 5px 5px 10px; padding: 10px 0px 10px 10px; border-left-color: rgb(195, 217, 229); border-left-width: 2px; border-left-style: solid; -ms-word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin: 0px 0px 10px;"><b>Gesendet:</b> Dienstag, 26. Februar 2019 um 15:28 Uhr<br/>
<b>Von:</b> "GPU Group" <gpugroup@gmail.com><br/>
<b>An:</b> "X3D Graphics public mailing list" <x3d-public@web3d.org><br/>
<b>Betreff:</b> Re: [x3d-public] Multiplayer strategies</div>
<div name="quoted-content">
<div>The DIS distributed interactive simulation component: I found it had some interesting things, and some flaws.
<div>x not x3d centric. Its a giant military standard, and a few nodes adapted to x3d</div>
<div>-- a transform type node</div>
<div>-- some strange radio nodes
<div>* uses UDP 'chirps' for updating positions / pose of transforms (like some multiplayer games)</div>
<div>-- OK if you miss a chirp - the next one will get you back on track</div>
<div>-- interpolators anticipate pose between chirps</div>
<div>-- no central server - anyone who logs in on that port can join and leave at any time</div>
<div>x tries to use UDP chirps for one-time state changes</div>
<div>xx if you miss a state change you are out of sync</div>
<div>-- compensates with regular re-broadcasting of states vis UDP chirps</div>
<div>xx those joining late will have to wait for state broadcasts to sync-up</div>
<div>Summary:</div>
</div>
<div>- I think it would be better to start from scratch ie requirements gathering ... and make something just right for x3d multiplayer.</div>
<div>-Doug Sanden</div>
<div> </div>
</div>
<div class="gmail_quote">
<div class="gmail_attr">On Tue, Feb 26, 2019 at 5:45 AM John Carlson <<a href="mailto:yottzumm@gmail.com" onclick="parent.window.location.href='mailto:yottzumm@gmail.com'; return false;" target="_blank">yottzumm@gmail.com</a>> wrote:</div>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;">
<div>
<div class="gmail-m_-6724862799019591912WordSection1">
<p class="MsoNormal">So far, I think the answer is DIS or AJAX. Check out the Networking Component. I’ve used <a href="http://socket.io" target="_blank">socket.io</a> on non X3D web pages. You may have to buffer requests.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">John</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986" target="_blank">Mail</a> for Windows 10</p>
<p class="MsoNormal"> </p>
<div style="border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(225, 225, 225) currentColor currentColor; padding: 3pt 0in 0in;">
<p class="MsoNormal" style="padding: 0in; border: currentColor; border-image: none;"><b>From: </b><a href="mailto:andreasplesch@gmail.com" onclick="parent.window.location.href='mailto:andreasplesch@gmail.com'; return false;" target="_blank">Andreas Plesch</a><br/>
<b>Sent: </b>Tuesday, February 26, 2019 4:34 AM<br/>
<b>To: </b><a href="mailto:x3d-public@web3d.org" onclick="parent.window.location.href='mailto:x3d-public@web3d.org'; return false;" target="_blank">X3D Graphics public mailing list</a><br/>
<b>Subject: </b>[x3d-public] Multiplayer strategies</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">With VR it may become more common to share a live, dynamic experience using multiple headsets and controllers. At first glance this seems to call for multiple, active viewpoints rendered by a single browser. The layering and layout components seem relevant.</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Another strategy would be having multiple browsers with identical scenes and keeping scenes in sync with an additional process and SAI methods.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">What are the strategies offered by X3D to support sharing a live, dynamic world ?</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">This came up as a x3dom GitHub issue and I thought may be more generally interesting.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
</div>
<p class="MsoNormal">Andreas</p>
<p class="MsoNormal"> </p>
</div>
</div>
_______________________________________________<br/>
x3d-public mailing list<br/>
<a href="mailto:x3d-public@web3d.org" onclick="parent.window.location.href='mailto:x3d-public@web3d.org'; return false;" target="_blank">x3d-public@web3d.org</a><br/>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a></blockquote>
</div>
_______________________________________________ x3d-public mailing list x3d-public@web3d.org <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a></div>
</div>
</div>
</div></div></body></html>