You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(200) |
Jun
(118) |
Jul
(267) |
Aug
(145) |
Sep
(199) |
Oct
(200) |
Nov
(101) |
Dec
(119) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
(21) |
Feb
(268) |
Mar
(154) |
Apr
(176) |
May
(158) |
Jun
(222) |
Jul
(304) |
Aug
(40) |
Sep
(48) |
Oct
(88) |
Nov
(22) |
Dec
|
2012 |
Jan
(12) |
Feb
(51) |
Mar
(63) |
Apr
(87) |
May
(254) |
Jun
(216) |
Jul
(157) |
Aug
(112) |
Sep
(149) |
Oct
(12) |
Nov
(5) |
Dec
(57) |
2013 |
Jan
(36) |
Feb
(28) |
Mar
(126) |
Apr
(111) |
May
(90) |
Jun
(103) |
Jul
(58) |
Aug
(78) |
Sep
(123) |
Oct
(82) |
Nov
(4) |
Dec
(6) |
2014 |
Jan
(9) |
Feb
(68) |
Mar
(243) |
Apr
(237) |
May
(51) |
Jun
(25) |
Jul
(19) |
Aug
(44) |
Sep
(23) |
Oct
(30) |
Nov
(39) |
Dec
(6) |
2015 |
Jan
(80) |
Feb
(49) |
Mar
(14) |
Apr
(38) |
May
(6) |
Jun
(2) |
Jul
(13) |
Aug
(81) |
Sep
(43) |
Oct
(7) |
Nov
(10) |
Dec
(38) |
2016 |
Jan
(32) |
Feb
(35) |
Mar
(82) |
Apr
(28) |
May
(32) |
Jun
(2) |
Jul
(51) |
Aug
(105) |
Sep
(35) |
Oct
(14) |
Nov
(26) |
Dec
(14) |
2017 |
Jan
(107) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(1) |
Jun
(20) |
Jul
(12) |
Aug
(6) |
Sep
(18) |
Oct
(29) |
Nov
(11) |
Dec
(18) |
2018 |
Jan
(53) |
Feb
(20) |
Mar
(22) |
Apr
(15) |
May
(16) |
Jun
(17) |
Jul
(46) |
Aug
(6) |
Sep
(36) |
Oct
|
Nov
(5) |
Dec
(33) |
2019 |
Jan
(71) |
Feb
(25) |
Mar
(37) |
Apr
(46) |
May
(18) |
Jun
(3) |
Jul
(10) |
Aug
(31) |
Sep
(13) |
Oct
(4) |
Nov
(9) |
Dec
(7) |
2020 |
Jan
(32) |
Feb
(16) |
Mar
(12) |
Apr
(43) |
May
(12) |
Jun
(23) |
Jul
(18) |
Aug
(17) |
Sep
(5) |
Oct
|
Nov
(10) |
Dec
(7) |
2021 |
Jan
(15) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
2023 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(11) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
(14) |
2024 |
Jan
(10) |
Feb
(1) |
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Christoph V. <chr...@gm...> - 2024-04-20 17:56:39
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>On the second day, in the afternoon, you can listen to my boss.</div> <div> </div> <div>He talked about "Mission Critical OTT, Using Kamailio as a Lightweight IMS"</div> <div> <div> <div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div style="margin:0 0 10px 0;"><b>Gesendet:</b> Samstag, 20. April 2024 um 11:11 Uhr<br/> <b>Von:</b> "Christoph Valentin" <chr...@gm...><br/> <b>An:</b> chr...@ko...<br/> <b>Cc:</b> "Kevin" <kl...@ya...>, r....@ka..., wol...@t-..., the...@ch..., "Markus Sonntag" <ma...@ma...><br/> <b>Betreff:</b> Kamailio World 2024</div> <div name="quoted-content"><br/> <a href="https://m.youtube.com/playlist?list=PLDaEs5k2Xy-sGcdNOWHfiB6zYKd4q0roM" target="_blank">https://m.youtube.com/playlist?list=PLDaEs5k2Xy-sGcdNOWHfiB6zYKd4q0roM</a><br/> --<br/> Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.</div> </div> </div> </div></div></body></html> |
From: Christoph V. <chr...@gm...> - 2024-04-20 17:33:26
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Dear all,</div> <div> </div> <div>I receive more and more ideas about what we COULD do at "The Society".</div> <div> </div> <div>You all know, we are only two active members, who have besides all that a real full time job in the industry.</div> <div> </div> <div>So, let me cite the bible: Luke 10,2: "<span class="text Luke-10-2" id="en-NIV-25366"><span class="woj">The harvest is plentiful, but the workers are few. Ask the Lord of the harvest, therefore, to send out workers into his harvest field."</span></span></div> <div> </div> <div><span class="text Luke-10-2"><span class="woj">So, "the society" is the "harvest field", sure, but who the hell is "the Lord of the harvest?" IDK.</span></span></div> <div> </div> <div><span class="text Luke-10-2"><span class="woj">Have a nice week,</span></span></div> <div><span class="text Luke-10-2"><span class="woj">Yours Christoph</span></span></div></div></body></html> |
From: Christoph V. <chr...@gm...> - 2024-03-16 14:59:04
|
Dear Doug, Dear all, Not necessary to say, I like the approach of the FreeWRL developers that you introduced last summer with this mail thread. I.e.: the multiuser capabilities of any sensor (touch sensor, time sensor, plane sensor, ......) are realized by Comment PDUs via the DIS protocol. This approach has the advantage the author of the scene does not need to care about multiuser (almost). See the demo video for our "teapot review" scene: https://lc-soc-lc.at/owncloud/index.php/s/BMQeF9fSgir4TaR Cloud Password: HalloWelt We want, I want, invest some of my spare time, in order to analyse the pros and cons against the Network Sensor (e.g. BS Contact) or other technologies. This is our goal for 2024. The whole story will be available on my private blackboard pages, after today in the evening. (u: doug, p: freewrl). https://lc-soc-lc.at/blackboard/member-space/yeti Have a nice week Yours CP/V Gesendet: Samstag, 17. Februar 2024 um 13:24 Uhr Von: "Christoph Valentin via x3d-public" <x3d...@we...> An: "Development for the FreeWRL X3D viewer." <fre...@li...> Cc: "Christoph Valentin" <chr...@gm...>, "Extensible 3D (X3D) Graphics public discussion" <x3d...@we...>, r....@ka..., "Kevin" <kl...@ya...> Betreff: Re: [x3d-public] web3d MMO > Sensor sharing via DIS Dear FreWRL developers, Thank you, I did a re-test with FreeWRL 6.6. The reported bugs are gone. Demo Video: https://lc-soc-lc.at/owncloud/index.php/s/IK0XVW0RGc8ICGT Video Password (cloud): HalloWelt I updated the report on my private blackboard pages: https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm] u:doug p:freewrl P.S.: I will remove those credentials from my private pages, soon. Gesendet: Samstag, 20. Januar 2024 um 21:33 Uhr Von: "GPU Group" <gpu...@gm...> An: "Christoph Valentin" <chr...@gm...> Cc: "Extensible 3D (X3D) Graphics public discussion" <x3d...@we...>, r....@ka..., "Kevin" <kl...@ya...> Betreff: Re: [x3d-public] web3d MMO > Sensor sharing via DIS Christoph - thanks for the VPN enlightenment! -Doug On Sat, Jan 20, 2024 at 11:55 AM Christoph Valentin <chr...@gm...[mailto:chr...@gm...]> wrote: Dear all, Fyi..... We made Doug's example running over our VPN. Our VPN did not forward the DIS PDUs towards multicast address 239.255.1.117[http://239.255.1.117[http://239.255.1.117]]. The reason was easy enough. I had to tell our OpenVPN server to do a bridged VPN instead of a routed VPN. Detailed report: https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm#tc007[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm#tc007][https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm#tc007[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm#tc007]] u: doug p: freewrl Note: I will remove those credentials from my internal blackboard pages, after a few weeks. Have a nice week, CP/V -- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet. Am 29.12.23, 16:49 schrieb Christoph Valentin via x3d-public <x3d...@we...[mailto:x3d...@we...]>: Doug, Just to close this mail thread on x3d-public, I am repeating the information that I already sent to FreeWrl mailing list. Thank you for your help with debugging. You were right, the crash was caused by a missing DEF name in the <Transform> node that the <TouchSensor> is a child of. A complete report can be found on my private pages on our association's blackboard: https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm][https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm]] u: doug p: freewrl Note: After some weeks, I will remove those credentials again from my private pages hny _______________________________________________ x3d-public mailing list x3d...@we...[mailto:x3d...@we...] http://web3d.org/mailman/listinfo/x3d-public_web3d.org[http://web3d.org/mailman/listinfo/x3d-public_web3d.org] _______________________________________________ x3d-public mailing list x3d...@we... http://web3d.org/mailman/listinfo/x3d-public_web3d.org[http://web3d.org/mailman/listinfo/x3d-public_web3d.org] |
From: Christoph V. <chr...@gm...> - 2024-02-17 12:24:49
|
Dear FreWRL developers, Thank you, I did a re-test with FreeWRL 6.6. The reported bugs are gone. Demo Video: https://lc-soc-lc.at/owncloud/index.php/s/IK0XVW0RGc8ICGT Video Password (cloud): HalloWelt I updated the report on my private blackboard pages: https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm u:doug p:freewrl P.S.: I will remove those credentials from my private pages, soon. Gesendet: Samstag, 20. Januar 2024 um 21:33 Uhr Von: "GPU Group" <gpu...@gm...> An: "Christoph Valentin" <chr...@gm...> Cc: "Extensible 3D (X3D) Graphics public discussion" <x3d...@we...>, r....@ka..., "Kevin" <kl...@ya...> Betreff: Re: [x3d-public] web3d MMO > Sensor sharing via DIS Christoph - thanks for the VPN enlightenment! -Doug On Sat, Jan 20, 2024 at 11:55 AM Christoph Valentin <chr...@gm...[mailto:chr...@gm...]> wrote: Dear all, Fyi..... We made Doug's example running over our VPN. Our VPN did not forward the DIS PDUs towards multicast address 239.255.1.117[http://239.255.1.117]. The reason was easy enough. I had to tell our OpenVPN server to do a bridged VPN instead of a routed VPN. Detailed report: https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm#tc007[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm#tc007] u: doug p: freewrl Note: I will remove those credentials from my internal blackboard pages, after a few weeks. Have a nice week, CP/V -- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet. Am 29.12.23, 16:49 schrieb Christoph Valentin via x3d-public <x3d...@we...[mailto:x3d...@we...]>: Doug, Just to close this mail thread on x3d-public, I am repeating the information that I already sent to FreeWrl mailing list. Thank you for your help with debugging. You were right, the crash was caused by a missing DEF name in the <Transform> node that the <TouchSensor> is a child of. A complete report can be found on my private pages on our association's blackboard: https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm] u: doug p: freewrl Note: After some weeks, I will remove those credentials again from my private pages hny _______________________________________________ x3d-public mailing list x3d...@we...[mailto:x3d...@we...] http://web3d.org/mailman/listinfo/x3d-public_web3d.org |
From: Christoph V. <chr...@gm...> - 2024-01-20 17:37:34
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi Doug, Hi all,</div> <div> </div> <div>As promised, here's the final e-mail.</div> <div> </div> <div>Our VPN did not forward the DIS PDUs towards multicast address 239.255.1.117.</div> <div> </div> <div>The reason was easy enough. I had to tell our OpenVPN server to do a bridged VPN instead of a routed VPN.</div> <div> </div> <div>Detailed report: <a href="https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm#tc007">https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm#tc007</a></div> <div> <div>u: doug</div> <div>p: freewrl</div> <div> </div> <div>Note: I will remove those credentials from my internal blackboard pages, after a few weeks.</div> <div> </div> <div>Kr,</div> <div>CP/V</div> <div> <div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div style="margin:0 0 10px 0;"><b>Gesendet:</b> Donnerstag, 28. Dezember 2023 um 22:58 Uhr<br/> <b>Von:</b> "Christoph Valentin via FreeWRL-develop" <fre...@li...><br/> <b>An:</b> fre...@li...<br/> <b>Cc:</b> "Christoph Valentin" <chr...@gm...>, "r....@ka..." <r....@ka...>, "Kevin" <kl...@ya...>, "John Carlson" <yot...@gm...><br/> <b>Betreff:</b> Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004)</div> <div name="quoted-content">Dear Doug, Dear FreeWrl community,<br/> <br/> First and most important: you were right, the crash happened, because FreeWrl expects DEF names (at least in the current experimental implementation) on each sensor node and on each grouping node that a sensor node is attached to (at least I could avoid the one crash, by adding a DEF name to the <Transform> node that the <TouchSensor> is a child of).<br/> <br/> Second: I am adding a few notes inline, marked by [CV2], which might lead to further discussion.<br/> <br/> Third: Currently, as of 2023-12-28 10pm CET, we are having problems with the routing of IP multicast datagrams in our VPN, but we are confident the problems are on our side.<br/> <br/> I will send a last e-mail with a link to a final report, as soon as we will have solved our local problems.<br/> <br/> Have a good NewYear<br/> CP/V <br/> <br/> <br/> <br/> Gesendet: Freitag, 22. Dezember 2023 um 13:06 Uhr<br/> Von: "Christoph Valentin via FreeWRL-develop" <fre...@li...><br/> An: "doug sanden" <hig...@ho...><br/> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." <r....@ka...>, "Kevin" <kl...@ya...>, "Development for the FreeWRL X3D viewer." <fre...@li...>, "John Carlson" <yot...@gm...><br/> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004)<br/> <br/> And the .pcap from TEST-004, where the crash actually happened<br/> <br/> Gesendet: Freitag, 22. Dezember 2023 um 12:26 Uhr<br/> Von: "Christoph Valentin via FreeWRL-develop" <fre...@li...><br/> An: "doug sanden" <hig...@ho...><br/> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." <r....@ka...>, "Kevin" <kl...@ya...>, "Development for the FreeWRL X3D viewer." <fre...@li...>, "John Carlson" <yot...@gm...><br/> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004)<br/> <br/> Hi Doug,<br/> <br/> Thank you for the fast response. Please find my comments inline (marked with [CV]).<br/> <br/> Have a nice day<br/> Christoph<br/> <br/> Gesendet: Donnerstag, 21. Dezember 2023 um 16:45 Uhr<br/> Von: "doug sanden" <hig...@ho...><br/> An: "Development for the FreeWRL X3D viewer." <fre...@li...><br/> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." <r....@ka...>, "Kevin" <kl...@ya...>, "John Carlson" <yot...@gm...><br/> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004)<br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> 1. why so noisy on the console<br/> A. I don’t get the noise, can you send me a few lines and I’ll search for the strings<br/> [CV]: Unfortunately, I do not know, where FreeWRL stores the logs (can you tell me?) So I took a screen shot (-> attached noisy-console.jpg)<br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> 2. why first avatar doesn’t show up in 2nd scene until it it moves?<br/> A. CONFIRMED. I don’t know, but likely nothing in freewrl is triggering a send<br/> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a><br/> L.2611<br/> if (!changed) {<br/> return pdus;<br/> }<br/> - in general an app doesn’t know how many others are logged in, and when they log in/out<br/> - in theory there could be a timespan whereby if you don’t move, it sends updates anyway, on a Heartbeat<br/> - or it tracks events from others and when it sees a new user, sends a pose update<br/> -- and that could be programmed in freewrl<br/> [CV]: I'd suggest to send EntityState PDU for the user's/avatar's position regularly (e.g. every second), if the user does not move. This seems to be the simplest solution. However, we would have to check with the IEEE DIS standard, what they say about this. I would volunteer to do a re-test after this implementation.<br/> [CV2]: at today's test session, we noticed that the avatar of the other user is not removed, when the other instance quits the FreeWrl player. That's another error, but probably the same root cause.<br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> 3. why timesensor is sent<br/> A. good question. I think the freewrl programmer just did all sensor nodes because they all pass through the same choke point in freewrl.<br/> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c</a>[<a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c</a>][<a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c</a>[<a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c</a>]]<br/> L. 6872 sendSensorEvents()<br/> There could be classes of sensors. Perhaps just the touch sinks should be sent. Or perhaps TimeSensor is special and needs to be synchronized in a special way. Or perhaps there needs to be a special Synch node that timesensors route through.<br/> An easy fix would be to filter out timesensor events so they aren't sent and see how that works.<br/> [CV]: I think, the idea of having classes of sensors is a good idea. Some sensors will generate events or state updates that are only of local interest, others would output their events/state updates on each and every scene instance. I would volunteer to do a proposal via x3d-public mailing list, OK?<br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> 4. why first scene bombs and avatar doesn’t move in 2nd scene<br/> A. good question, I haven’t reproduced that error with elevator3.x3d. Elevator2.x3d bombs sometimes for me when I mouse-over a sensor. That could be the bug. It's bombing because freewrl programmer assumed the nodes would have DEF names<br/> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a>[<a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a>][<a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a>[<a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a>]]<br/> L.2565<br/> const char* def = getNodeName(fromnode);<br/> int fromNode = hash37(def);<br/> and it bombs when doing a hash37 on a NULL string.<br/> [CV]: my first idea was it could be caused by malformed DIS Comment PDUs -> I attached the .pcap from TEST-003 (-> test-003-20231221-elevator3-single-user.pcap) -> Frame No. 247, 259, 281, 284 are malformed<br/> [CV2]: CONFIRMED, the crash was caused by the missing DEF name in the <Transform> node that the <TouchSensor> is a child of. Malformed comment PDUs could still be found in the .pcap, even if the DEF name had been added <br/> <br/> -Doug<br/> <br/> <br/> ________________________________________<br/> From: Christoph Valentin via FreeWRL-develop <fre...@li...><br/> Sent: December 21, 2023 4:15 AM<br/> To: Development for the FreeWRL X3D viewer.<br/> Cc: Christoph Valentin; r....@ka...; Kevin; John Carlson<br/> Subject: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004)<br/> <br/> Dear developers of FreeWrl,<br/> <br/> you find the information about today's test session at <a href="https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm" target="_blank">https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm</a>[<a href="https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm" target="_blank">https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm</a>][<a href="https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm" target="_blank">https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm</a>[<a href="https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm" target="_blank">https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm</a>]]<br/> User: doug<br/> Passwd: freewrl<br/> <br/> <br/> <br/> Follows a copy of the most important text:<br/> <br/> At a test session in the morning of Dec 21st, 2023, I tried to nail down the most important behavioral shortcomings of the elevator3.x3d scene, when using it on FreeWrl 6.4 on my private Windows laptop<br/> <br/> <br/> <br/> TEST-003: Single Instance Test, basic wireshark trace<br/> <br/> Demo Video: <a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>][<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>]][<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>][<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>]]]<br/> Cloud Password for the video: HalloWelt<br/> <br/> - Why does the FreeWrl 6.4 output that nasty logs that fill the whole display?<br/> <br/> - When assuming the DIS Comment PDUs are caused by both sensors of the scene, i.e. by the TouchSensor and by the TimeSensor, then the question arises: why do we need traffic for the TimeSensor, when we have already the touch event of the TouchSensor propagated thru the network? Isn't that redundant information?<br/> <br/> <br/> <br/> TEST-004: Two Instances Test (one machine), behavioral assessment<br/> <br/> Demo Video: <a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>][<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>]][<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>][<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>]]]<br/> Cloud Password for the video: HalloWelt<br/> <br/> - Why does the avatar of the first instance appear at the second instance, only after the user on the first instance moves a bit?<br/> - Why does the elevator in the first instance NOT start to move, after I have touched the button in the second instance?<br/> - Why does the first instance crash, soon after I touch the button in the second?<br/> <br/> Have a nice day<br/> <br/> Yours<br/> CP/V<br/> <br/> <br/> _______________________________________________<br/> FreeWRL-develop mailing list<br/> Fre...@li...<br/> <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>[<a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>][<a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>[<a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>]]_______________________________________________ FreeWRL-develop mailing list Fre...@li... <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>[<a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>]_______________________________________________ FreeWRL-develop mailing list Fre...@li... <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>[<a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>]<br/> <br/> <br/> _______________________________________________<br/> FreeWRL-develop mailing list<br/> Fre...@li...<br/> <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a></div> </div> </div> </div></div></body></html> |
From: John C. <yot...@gm...> - 2024-01-10 06:32:49
|
Perhaps an approach to generative AI for 3D would be through Turtle/RDF/OWL/SPARQL. Work on translation to X3D might be needed. I checked to see if RDF worked in ChatGPT. One can construct somewhat creative RDF, or query for books, e.g. Mark Twain’s books. I look forward to trying GPU skinning. John On Tue, Jan 9, 2024 at 2:41 PM doug sanden <hig...@ho...> wrote: > That is interesting history. 25+ years. So that's how it happened. Wow. > -Doug > > I dabbled for a few years in wrl / x3d using cortona and flux (for a > historical virtual tour of old townsite). I had talked to Parisi once on > phone and suggested he make flux opensource, he said maybe he should, and > would think about it. He did then retracted, but I got a snapshot before > retraction. Then I found freewrl on sourceforge, which didn't run on > windows, but had an active community. So I worked on porting it. That was > back in 2009 or so. > > Freewrl's age is showing a bit, with html integration being a theme these > days (hypothesis: freewrl could do hybrid using webview), and protos still > not handled generally (also a limitation of specs). > I haven't heard anyone working with generative AI for x3d - any ideas how > that would work with x3d/web3d? > > Maybe needs one more industrial/gov/mil project to spur some clean up / > refactoring -- let us know if you see something. > > > > > ________________________________________ > From: JohnS <iva...@gm...> > Sent: January 9, 2024 11:50 AM > To: Development for the FreeWRL X3D viewer. > Subject: Re: [FreeWRL-develop] GPU skinning > > And, it started because I was doing some VR work for a project that might > have been for the military research side, using a program called "Liquid > Reality", that ran on Linux. Microsoft purchased that company, and (of > course) the product disappeared. So I had to find (quickly) a replacement; > Tuomas Lukka had started FreeWRL, in Perl, and to get performance, lots > re-written in C; as you are 100% aware, the internals are "weird" because > of that Perl origin. > > Before I moved back to Canada mid-1996, I attended a W3C conference in > Paris in May, and (looking for a place to sit and type) I sat near the back > of a presentation on VRML and listened to the presentation rather than > sorting notes. I do remember thinking "this is strange..." but little did I > know that, within a year or two, I'd be using it, and working with Tony > Parisi on the VRML/X3D standards; Tony is mentioned in the talk linked > below from that conference. (FYI, for a bit of ancient history) > > https://www.w3.org/Conferences/WWW5/fich_html/invited/MarkPesce-speech.html > > Long time ago now, but the world does work in interesting ways! I > sometimes follow the X3D email chains, you are doing interesting work. > > John. > > > On Tue, Jan 9, 2024 at 11:39 AM doug sanden <hig...@ho... > <mailto:hig...@ho...>> wrote: > Thanks John. Who knew freeWRL would last this long when it was started?! > -Doug > > > _______________________________________________ > FreeWRL-develop mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freewrl-develop > |
From: doug s. <hig...@ho...> - 2024-01-09 20:40:56
|
That is interesting history. 25+ years. So that's how it happened. Wow. -Doug I dabbled for a few years in wrl / x3d using cortona and flux (for a historical virtual tour of old townsite). I had talked to Parisi once on phone and suggested he make flux opensource, he said maybe he should, and would think about it. He did then retracted, but I got a snapshot before retraction. Then I found freewrl on sourceforge, which didn't run on windows, but had an active community. So I worked on porting it. That was back in 2009 or so. Freewrl's age is showing a bit, with html integration being a theme these days (hypothesis: freewrl could do hybrid using webview), and protos still not handled generally (also a limitation of specs). I haven't heard anyone working with generative AI for x3d - any ideas how that would work with x3d/web3d? Maybe needs one more industrial/gov/mil project to spur some clean up / refactoring -- let us know if you see something. ________________________________________ From: JohnS <iva...@gm...> Sent: January 9, 2024 11:50 AM To: Development for the FreeWRL X3D viewer. Subject: Re: [FreeWRL-develop] GPU skinning And, it started because I was doing some VR work for a project that might have been for the military research side, using a program called "Liquid Reality", that ran on Linux. Microsoft purchased that company, and (of course) the product disappeared. So I had to find (quickly) a replacement; Tuomas Lukka had started FreeWRL, in Perl, and to get performance, lots re-written in C; as you are 100% aware, the internals are "weird" because of that Perl origin. Before I moved back to Canada mid-1996, I attended a W3C conference in Paris in May, and (looking for a place to sit and type) I sat near the back of a presentation on VRML and listened to the presentation rather than sorting notes. I do remember thinking "this is strange..." but little did I know that, within a year or two, I'd be using it, and working with Tony Parisi on the VRML/X3D standards; Tony is mentioned in the talk linked below from that conference. (FYI, for a bit of ancient history) https://www.w3.org/Conferences/WWW5/fich_html/invited/MarkPesce-speech.html Long time ago now, but the world does work in interesting ways! I sometimes follow the X3D email chains, you are doing interesting work. John. On Tue, Jan 9, 2024 at 11:39 AM doug sanden <hig...@ho...<mailto:hig...@ho...>> wrote: Thanks John. Who knew freeWRL would last this long when it was started?! -Doug |
From: JohnS <iva...@gm...> - 2024-01-09 18:50:42
|
And, it started because I was doing some VR work for a project that might have been for the military research side, using a program called "Liquid Reality", that ran on Linux. Microsoft purchased that company, and (of course) the product disappeared. So I had to find (quickly) a replacement; Tuomas Lukka had started FreeWRL, in Perl, and to get performance, lots re-written in C; as you are 100% aware, the internals are "weird" because of that Perl origin. Before I moved back to Canada mid-1996, I attended a W3C conference in Paris in May, and (looking for a place to sit and type) I sat near the back of a presentation on VRML and listened to the presentation rather than sorting notes. I do remember thinking "this is strange..." but little did I know that, within a year or two, I'd be using it, and working with Tony Parisi on the VRML/X3D standards; Tony is mentioned in the talk linked below from that conference. (FYI, for a bit of ancient history) https://www.w3.org/Conferences/WWW5/fich_html/invited/MarkPesce-speech.html Long time ago now, but the world does work in interesting ways! I sometimes follow the X3D email chains, you are doing interesting work. John. On Tue, Jan 9, 2024 at 11:39 AM doug sanden <hig...@ho...> wrote: > Thanks John. Who knew freeWRL would last this long when it was started?! > -Doug > > |
From: doug s. <hig...@ho...> - 2024-01-09 16:39:41
|
Thanks John. Who knew freeWRL would last this long when it was started?! -Doug ________________________________________ From: JohnS <iva...@gm...> Sent: January 9, 2024 9:05 AM To: Development for the FreeWRL X3D viewer. Subject: Re: [FreeWRL-develop] GPU skinning Well done Doug! Love to see the continued improvement in the source - John. On Tue, Jan 9, 2024 at 10:46 AM doug sanden <hig...@ho...<mailto:hig...@ho...>> wrote: Added an option for GPU humanoid skinning and its on by default, and a commandline parameter --skin F to turn it off (thunk to CPU skinning) Speedup on big humanoids with 224,000 skin vertices: from 2 FPS with CPU skinning to 20 - 40 FPS with GPU skinning. -Doug _______________________________________________ FreeWRL-develop mailing list Fre...@li...<mailto:Fre...@li...> https://lists.sourceforge.net/lists/listinfo/freewrl-develop |
From: JohnS <iva...@gm...> - 2024-01-09 16:06:00
|
Well done Doug! Love to see the continued improvement in the source - John. On Tue, Jan 9, 2024 at 10:46 AM doug sanden <hig...@ho...> wrote: > Added an option for GPU humanoid skinning and its on by default, and a > commandline parameter --skin F to turn it off (thunk to CPU skinning) > Speedup on big humanoids with 224,000 skin vertices: from 2 FPS with CPU > skinning to 20 - 40 FPS with GPU skinning. > -Doug > > > _______________________________________________ > FreeWRL-develop mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freewrl-develop > |
From: doug s. <hig...@ho...> - 2024-01-09 15:46:26
|
Added an option for GPU humanoid skinning and its on by default, and a commandline parameter --skin F to turn it off (thunk to CPU skinning) Speedup on big humanoids with 224,000 skin vertices: from 2 FPS with CPU skinning to 20 - 40 FPS with GPU skinning. -Doug |
From: John C. <yot...@gm...> - 2024-01-08 17:39:38
|
This was due to shading language optimization by the compiler. An unused variable, rfac was removed, causing the removal of bias, power, scale, etc. On Sun, Jan 7, 2024 at 10:53 AM John Carlson <yot...@gm...> wrote: > This message is referenced from previous post to group. It has been > extended. > > ---------- Forwarded message --------- > From: John Carlson <yot...@gm...> > Date: Sun, Jan 7, 2024 at 3:01 AM > Subject: Scene ok. Why all the errors though? > To: GPU Group <gpu...@gm...> > > > See attached zip, personal/fwball.x3d > > There are similar warning issues with CGE. The scene is okay there too. I > can send a zip for comparison, if needed. I have gotten X_ITE to work > without an issue. > > The scene appears okay, perhaps a bit of flicker or shader delay (probably > due to compilation of shader?), but there's huge number of log messages. > Perhaps there is some type conflict or the variables sent to the vertex > shader are affecting the fragment shader? Perhaps I need to change the > variable types with updates to shading language? > > $ /c/Program\ Files\ \(x86\)/freeWRL/freeWRL.6.4/freeWRL.exe > personal/fwball.x3d > > MidiInWinMM::initialize: no MIDI input devices currently available. > > libfreewrl version 6.4.0 > -h for commandline use > openGL version 4.6.0 NVIDIA 537.42 > GLSL shader max version 4.60 NVIDIA 460 > maximum texture size system/gpu: 16384 runtime/freewrl: 8192 > processor architecture x64 > maxiumum image texture units 32 > depth bits 24 > Shader variable :chromaticDispertion: is declared as an attribute; we can > not do much with thisin shader 13, we have 3 uniforms, looking for name > :chromaticDispertion: ....Uniform 0 is name :cube: len 4 size 1 type > 35680a=cube b=chromaticDispertion brackets =(null) > ....Uniform 1 is name :fw_ModelViewMatrix: len 18 size 1 type > 35676a=fw_ModelViewMatrix b=chromaticDispertion brackets =(null) > ....Uniform 2 is name :fw_ProjectionMatrix: len 19 size 1 type > 35676a=fw_ProjectionMatrix b=chromaticDispertion brackets =(null) > Shader type check: X3D type and shader type not compatible for variable > :fw_ProjectionMatrix:shaderCheck mode 1 (inputOnly) type 20 (SFVec3f) name 0 > len 19 size 1 type 35676 ch fw_ProjectionMatrix > GL_FLOAT_MAT4 > in shader 13, we have 3 uniforms, looking for name :cube: ....Uniform 0 > is name :cube: len 4 size 1 type 35680a=cube b=cube brackets =(null) > names match, breakingShader type check: X3D type and shader type not > compatible for variable :cube:shaderCheck mode 1 (inputOnly) type 10 > (SFNode) name 0 > len 4 size 1 type 35680 ch cube > GL_SAMPLER_CUBE > Shader variable :bias: is either not declared or not used in the shader > programin shader 13, we have 3 uniforms, looking for name :bias: > ....Uniform 0 is name :cube: len 4 size 1 type 35680a=cube b=bias brackets > =(null) > ....Uniform 1 is name :fw_ModelViewMatrix: len 18 size 1 type > 35676a=fw_ModelViewMatrix b=bias brackets =(null) > ....Uniform 2 is name :fw_ProjectionMatrix: len 19 size 1 type > 35676a=fw_ProjectionMatrix b=bias brackets =(null) > Shader type check: X3D type and shader type not compatible for variable > :fw_ProjectionMatrix:shaderCheck mode 1 (inputOnly) type 0 (SFFloat) name 0 > len 19 size 1 type 35676 ch fw_ProjectionMatrix > GL_FLOAT_MAT4 > Shader variable :scale: is either not declared or not used in the shader > programin shader 13, we have 3 uniforms, looking for name :scale: > ....Uniform 0 is name :cube: len 4 size 1 type 35680a=cube b=scale brackets > =(null) > ....Uniform 1 is name :fw_ModelViewMatrix: len 18 size 1 type > 35676a=fw_ModelViewMatrix b=scale brackets =(null) > ....Uniform 2 is name :fw_ProjectionMatrix: len 19 size 1 type > 35676a=fw_ProjectionMatrix b=scale brackets =(null) > Shader type check: X3D type and shader type not compatible for variable > :fw_ProjectionMatrix:shaderCheck mode 1 (inputOnly) type 0 (SFFloat) name 0 > len 19 size 1 type 35676 ch fw_ProjectionMatrix > GL_FLOAT_MAT4 > Shader variable :power: is either not declared or not used in the shader > programin shader 13, we have 3 uniforms, looking for name :power: > ....Uniform 0 is name :cube: len 4 size 1 type 35680a=cube b=power brackets > =(null) > ....Uniform 1 is name :fw_ModelViewMatrix: len 18 size 1 type > 35676a=fw_ModelViewMatrix b=power brackets =(null) > ....Uniform 2 is name :fw_ProjectionMatrix: len 19 size 1 type > 35676a=fw_ProjectionMatrix b=power brackets =(null) > Shader type check: X3D type and shader type not compatible for variable > :fw_ProjectionMatrix:shaderCheck mode 1 (inputOnly) type 0 (SFFloat) name 0 > len 19 size 1 type 35676 ch fw_ProjectionMatrix > GL_FLOAT_MAT4 > GL_INVALID_VALUE here: child_shape after reallyDrawOnce > (C:\Users\dougs\Documents\dev\source2\freewrl\freex3d\src\lib\scenegraph\Component_Shape.c:1662) > calling kill_javascript() > done kill_javascript > Ending texture load thread gracefully > finalizeRenderSceneUpdateScene > |
From: John C. <yot...@gm...> - 2024-01-08 17:37:21
|
SOLUTION: Use FreeWRL with -J DUK arguments /c/Program\ Files\ \(x86\)/freeWRL/freeWRL.6.4/freeWRL.exe -J DUK flowers2.x3d Or set default JS engine in FreeWRL launcher to duktape2000 Comments on updating individual coordinates array variables with JS spidermonkey welcome! PROBLEM follows: I don't know how to solve this problem in a cross-browser way yet. I know why X3DOM doesn't work (routes to/from Script nodes don't work, last I heard). I am attaching a new version, which works, except for coordinates updates w/ respect to parameter Script fields or Script local variables in FreeWRL. Creating local variables in the Script tag instead of using fields didn't work. At this point, I am suggesting looking into FreeWRL source code for solutions. I no longer need MFVec3f constructor compatibility, since I am using strictly Script fields now, and not temporary variables. https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/personal/flowers2.x3d Previous versions worked in FreeWRL, but this is the only solution that has both flowers visualized and some amount of animation. Full animation, like Sunrize, is desired. If you want to download sunrize, I suggest: $ npm install -g sunrize Then $ sunrize `pwd`/flowers2.x3d Alternatively, $ npx sunrize `pwd`/flowers2.x3d npx/npm is part of node.js, available here: https://nodejs.org/en/download/ `pwd`/ expands to the current folder in bash. You may have to specify the full path to flowers2.x3d Full source is attached. Feel free to cross-post. Thanks! John |
From: John C. <yot...@gm...> - 2024-01-07 16:31:21
|
I recall trying to move the fields from ComposedShader to ShaderPart, but nothing changed. I can see that this issue might come from the fragment shader which does not use or declare the variables, but the vertex shader does declare and use the variables. I haven’t tried that patch yet. I will spend a bit more time debugging. Thanks for your time, this helps me think. |
From: John C. <yot...@gm...> - 2023-12-29 22:51:50
|
I think one has to send the Entity State PDU whether the user moves or not. On Fri, Dec 29, 2023 at 2:20 PM Christoph Valentin < chr...@gm...> wrote: > Hi John, > > I doubt this would help, because we are using UDP, which is an unreliable > transport protocol. > > I am in favor of repeating the DIS Entity State PDU e.g. every second, if > the user does not move. > > If no Entity State PDU is received for three seconds, then the entity > manager should remove the avatar. > > Makes sense? > > Kind regards and hny > Christoph > > -- > Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail > gesendet. > Am 29.12.23, 05:16 schrieb John Carlson <yot...@gm...>: > >> There might be a connect/disconnect PDU in DIS. >> >> On Thu, Dec 28, 2023 at 3:58 PM Christoph Valentin < >> chr...@gm...> wrote: >> >>> Dear Doug, Dear FreeWrl community, >>> >>> First and most important: you were right, the crash happened, because >>> FreeWrl expects DEF names (at least in the current experimental >>> implementation) on each sensor node and on each grouping node that a sensor >>> node is attached to (at least I could avoid the one crash, by adding a DEF >>> name to the <Transform> node that the <TouchSensor> is a child of). >>> >>> Second: I am adding a few notes inline, marked by [CV2], which might >>> lead to further discussion. >>> >>> Third: Currently, as of 2023-12-28 10pm CET, we are having problems with >>> the routing of IP multicast datagrams in our VPN, but we are confident the >>> problems are on our side. >>> >>> I will send a last e-mail with a link to a final report, as soon as we >>> will have solved our local problems. >>> >>> Have a good NewYear >>> CP/V >>> >>> >>> >>> Gesendet: Freitag, 22. Dezember 2023 um 13:06 Uhr >>> Von: "Christoph Valentin via FreeWRL-develop" < >>> fre...@li...> >>> An: "doug sanden" <hig...@ho...> >>> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." >>> <r....@ka...>, "Kevin" <kl...@ya...>, "Development for the >>> FreeWRL X3D viewer." <fre...@li...>, "John >>> Carlson" <yot...@gm...> >>> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, >>> TEST-004) >>> >>> And the .pcap from TEST-004, where the crash actually happened >>> >>> Gesendet: Freitag, 22. Dezember 2023 um 12:26 Uhr >>> Von: "Christoph Valentin via FreeWRL-develop" < >>> fre...@li...> >>> An: "doug sanden" <hig...@ho...> >>> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." >>> <r....@ka...>, "Kevin" <kl...@ya...>, "Development for the >>> FreeWRL X3D viewer." <fre...@li...>, "John >>> Carlson" <yot...@gm...> >>> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, >>> TEST-004) >>> >>> Hi Doug, >>> >>> Thank you for the fast response. Please find my comments inline (marked >>> with [CV]). >>> >>> Have a nice day >>> Christoph >>> >>> Gesendet: Donnerstag, 21. Dezember 2023 um 16:45 Uhr >>> Von: "doug sanden" <hig...@ho...> >>> An: "Development for the FreeWRL X3D viewer." < >>> fre...@li...> >>> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." >>> <r....@ka...>, "Kevin" <kl...@ya...>, "John Carlson" < >>> yot...@gm...> >>> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, >>> TEST-004) >>> >>> >>> >>> >>> >>> >>> >>> 1. why so noisy on the console >>> A. I don’t get the noise, can you send me a few lines and I’ll search >>> for the strings >>> [CV]: Unfortunately, I do not know, where FreeWRL stores the logs (can >>> you tell me?) So I took a screen shot (-> attached noisy-console.jpg) >>> >>> >>> >>> >>> >>> >>> >>> 2. why first avatar doesn’t show up in 2nd scene until it it moves? >>> A. CONFIRMED. I don’t know, but likely nothing in freewrl is triggering >>> a send >>> >>> https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c >>> L.2611 >>> if (!changed) { >>> return pdus; >>> } >>> - in general an app doesn’t know how many others are logged in, and when >>> they log in/out >>> - in theory there could be a timespan whereby if you don’t move, it >>> sends updates anyway, on a Heartbeat >>> - or it tracks events from others and when it sees a new user, sends a >>> pose update >>> -- and that could be programmed in freewrl >>> [CV]: I'd suggest to send EntityState PDU for the user's/avatar's >>> position regularly (e.g. every second), if the user does not move. This >>> seems to be the simplest solution. However, we would have to check with the >>> IEEE DIS standard, what they say about this. I would volunteer to do a >>> re-test after this implementation. >>> [CV2]: at today's test session, we noticed that the avatar of the other >>> user is not removed, when the other instance quits the FreeWrl player. >>> That's another error, but probably the same root cause. >>> >>> >>> >>> >>> >>> >>> >>> 3. why timesensor is sent >>> A. good question. I think the freewrl programmer just did all sensor >>> nodes because they all pass through the same choke point in freewrl. >>> >>> https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c][https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c]] >>> L. 6872 sendSensorEvents() >>> There could be classes of sensors. Perhaps just the touch sinks should >>> be sent. Or perhaps TimeSensor is special and needs to be synchronized in a >>> special way. Or perhaps there needs to be a special Synch node that >>> timesensors route through. >>> An easy fix would be to filter out timesensor events so they aren't sent >>> and see how that works. >>> [CV]: I think, the idea of having classes of sensors is a good idea. >>> Some sensors will generate events or state updates that are only of local >>> interest, others would output their events/state updates on each and every >>> scene instance. I would volunteer to do a proposal via x3d-public mailing >>> list, OK? >>> >>> >>> >>> >>> >>> >>> >>> 4. why first scene bombs and avatar doesn’t move in 2nd scene >>> A. good question, I haven’t reproduced that error with elevator3.x3d. >>> Elevator2.x3d bombs sometimes for me when I mouse-over a sensor. That could >>> be the bug. It's bombing because freewrl programmer assumed the nodes would >>> have DEF names >>> >>> https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c][https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c]] >>> L.2565 >>> const char* def = getNodeName(fromnode); >>> int fromNode = hash37(def); >>> and it bombs when doing a hash37 on a NULL string. >>> [CV]: my first idea was it could be caused by malformed DIS Comment PDUs >>> -> I attached the .pcap from TEST-003 (-> >>> test-003-20231221-elevator3-single-user.pcap) -> Frame No. 247, 259, 281, >>> 284 are malformed >>> [CV2]: CONFIRMED, the crash was caused by the missing DEF name in the >>> <Transform> node that the <TouchSensor> is a child of. Malformed comment >>> PDUs could still be found in the .pcap, even if the DEF name had been >>> added >>> >>> -Doug >>> >>> >>> ________________________________________ >>> From: Christoph Valentin via FreeWRL-develop < >>> fre...@li...> >>> Sent: December 21, 2023 4:15 AM >>> To: Development for the FreeWRL X3D viewer. >>> Cc: Christoph Valentin; r....@ka...; Kevin; John Carlson >>> Subject: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) >>> >>> Dear developers of FreeWrl, >>> >>> you find the information about today's test session at >>> https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm][https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm]] >>> User: doug >>> Passwd: freewrl >>> >>> >>> >>> Follows a copy of the most important text: >>> >>> At a test session in the morning of Dec 21st, 2023, I tried to nail down >>> the most important behavioral shortcomings of the elevator3.x3d scene, when >>> using it on FreeWrl 6.4 on my private Windows laptop >>> >>> >>> >>> TEST-003: Single Instance Test, basic wireshark trace >>> >>> Demo Video: >>> https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY]][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY]]] >>> Cloud Password for the video: HalloWelt >>> >>> - Why does the FreeWrl 6.4 output that nasty logs that fill the whole >>> display? >>> >>> - When assuming the DIS Comment PDUs are caused by both sensors of the >>> scene, i.e. by the TouchSensor and by the TimeSensor, then the question >>> arises: why do we need traffic for the TimeSensor, when we have already the >>> touch event of the TouchSensor propagated thru the network? Isn't that >>> redundant information? >>> >>> >>> >>> TEST-004: Two Instances Test (one machine), behavioral assessment >>> >>> Demo Video: >>> https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p]][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p]]] >>> Cloud Password for the video: HalloWelt >>> >>> - Why does the avatar of the first instance appear at the second >>> instance, only after the user on the first instance moves a bit? >>> - Why does the elevator in the first instance NOT start to move, after I >>> have touched the button in the second instance? >>> - Why does the first instance crash, soon after I touch the button in >>> the second? >>> >>> Have a nice day >>> >>> Yours >>> CP/V >>> >>> >>> _______________________________________________ >>> FreeWRL-develop mailing list >>> Fre...@li... >>> >>> https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop][https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop]]_______________________________________________ >>> FreeWRL-develop mailing list Fre...@li... >>> https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop]_______________________________________________ >>> FreeWRL-develop mailing list Fre...@li... >>> https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop] >>> >> |
From: Christoph V. <chr...@gm...> - 2023-12-29 20:20:32
|
<html> <head> <meta name="viewport" content="width=device-width"> <meta http-equiv="Content-Type" content="text/vnd.ui.insecure+html;charset=utf-8"> </head> <body style="overflow-wrap:break-word; word-break: break-word;"><div class="mail_android_message" style="line-height: 1; padding: 0.5em">Hi John,<br/><br/>I doubt this would help, because we are using UDP, which is an unreliable transport protocol.<br/><br/>I am in favor of repeating the DIS Entity State PDU e.g. every second, if the user does not move.<br/><br/>If no Entity State PDU is received for three seconds, then the entity manager should remove the avatar.<br/><br/>Makes sense?<br/><br/>Kind regards and hny<br/>Christoph<br/><br/>--<br/>Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.</div><div class="mail_android_quote" style="line-height: 1; padding: 0.3em"><html><body>Am 29.12.23, 05:16 schrieb John Carlson <yot...@gm...>:</body></html><blockquote class="gmail_quote" style="margin: 0.8ex 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div dir="auto"> There might be a connect/disconnect PDU in DIS. </div> <div> <br> <div class="gmail_quote"> <div class="gmail_attr" dir="ltr"> On Thu, Dec 28, 2023 at 3:58 PM Christoph Valentin <<a href="mailto:chr...@gm...">chr...@gm...</a>> wrote: <br> </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"> Dear Doug, Dear FreeWrl community, <br> <br> First and most important: you were right, the crash happened, because FreeWrl expects DEF names (at least in the current experimental implementation) on each sensor node and on each grouping node that a sensor node is attached to (at least I could avoid the one crash, by adding a DEF name to the <Transform> node that the <TouchSensor> is a child of). <br> <br> Second: I am adding a few notes inline, marked by [CV2], which might lead to further discussion. <br> <br> Third: Currently, as of 2023-12-28 10pm CET, we are having problems with the routing of IP multicast datagrams in our VPN, but we are confident the problems are on our side. <br> <br> I will send a last e-mail with a link to a final report, as soon as we will have solved our local problems. <br> <br> Have a good NewYear <br> CP/V <br> <br> <br> <br> Gesendet: Freitag, 22. Dezember 2023 um 13:06 Uhr <br> Von: "Christoph Valentin via FreeWRL-develop" <<a href="mailto:fre...@li...">fre...@li...</a>> <br> An: "doug sanden" <<a href="mailto:hig...@ho...">hig...@ho...</a>> <br> Cc: "Christoph Valentin" <<a href="mailto:chr...@gm...">chr...@gm...</a>>, "<a href="mailto:r....@ka...">r....@ka...</a>" <<a href="mailto:r....@ka...">r....@ka...</a>>, "Kevin" <<a href="mailto:kl...@ya...">kl...@ya...</a>>, "Development for the FreeWRL X3D viewer." <<a href="mailto:fre...@li...">fre...@li...</a>>, "John Carlson" <<a href="mailto:yot...@gm...">yot...@gm...</a>> <br> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) <br> <br> And the .pcap from TEST-004, where the crash actually happened <br> <br> Gesendet: Freitag, 22. Dezember 2023 um 12:26 Uhr <br> Von: "Christoph Valentin via FreeWRL-develop" <<a href="mailto:fre...@li...">fre...@li...</a>> <br> An: "doug sanden" <<a href="mailto:hig...@ho...">hig...@ho...</a>> <br> Cc: "Christoph Valentin" <<a href="mailto:chr...@gm...">chr...@gm...</a>>, "<a href="mailto:r....@ka...">r....@ka...</a>" <<a href="mailto:r....@ka...">r....@ka...</a>>, "Kevin" <<a href="mailto:kl...@ya...">kl...@ya...</a>>, "Development for the FreeWRL X3D viewer." <<a href="mailto:fre...@li...">fre...@li...</a>>, "John Carlson" <<a href="mailto:yot...@gm...">yot...@gm...</a>> <br> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) <br> <br> Hi Doug, <br> <br> Thank you for the fast response. Please find my comments inline (marked with [CV]). <br> <br> Have a nice day <br> Christoph <br> <br> Gesendet: Donnerstag, 21. Dezember 2023 um 16:45 Uhr <br> Von: "doug sanden" <<a href="mailto:hig...@ho...">hig...@ho...</a>> <br> An: "Development for the FreeWRL X3D viewer." <<a href="mailto:fre...@li...">fre...@li...</a>> <br> Cc: "Christoph Valentin" <<a href="mailto:chr...@gm...">chr...@gm...</a>>, "<a href="mailto:r....@ka...">r....@ka...</a>" <<a href="mailto:r....@ka...">r....@ka...</a>>, "Kevin" <<a href="mailto:kl...@ya...">kl...@ya...</a>>, "John Carlson" <<a href="mailto:yot...@gm...">yot...@gm...</a>> <br> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) <br> <br> <br> <br> <br> <br> <br> <br> 1. why so noisy on the console <br> A. I don’t get the noise, can you send me a few lines and I’ll search for the strings <br> [CV]: Unfortunately, I do not know, where FreeWRL stores the logs (can you tell me?) So I took a screen shot (-> attached noisy-console.jpg) <br> <br> <br> <br> <br> <br> <br> <br> 2. why first avatar doesn’t show up in 2nd scene until it it moves? <br> A. CONFIRMED. I don’t know, but likely nothing in freewrl is triggering a send <br> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a> <br> L.2611 <br> if (!changed) { <br> return pdus; <br> } <br> - in general an app doesn’t know how many others are logged in, and when they log in/out <br> - in theory there could be a timespan whereby if you don’t move, it sends updates anyway, on a Heartbeat <br> - or it tracks events from others and when it sees a new user, sends a pose update <br> -- and that could be programmed in freewrl <br> [CV]: I'd suggest to send EntityState PDU for the user's/avatar's position regularly (e.g. every second), if the user does not move. This seems to be the simplest solution. However, we would have to check with the IEEE DIS standard, what they say about this. I would volunteer to do a re-test after this implementation. <br> [CV2]: at today's test session, we noticed that the avatar of the other user is not removed, when the other instance quits the FreeWrl player. That's another error, but probably the same root cause. <br> <br> <br> <br> <br> <br> <br> <br> 3. why timesensor is sent <br> A. good question. I think the freewrl programmer just did all sensor nodes because they all pass through the same choke point in freewrl. <br> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c%5Bhttps://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c%5D%5Bhttps://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c%5Bhttps://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c%5D%5D">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c][https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c]]</a> <br> L. 6872 sendSensorEvents() <br> There could be classes of sensors. Perhaps just the touch sinks should be sent. Or perhaps TimeSensor is special and needs to be synchronized in a special way. Or perhaps there needs to be a special Synch node that timesensors route through. <br> An easy fix would be to filter out timesensor events so they aren't sent and see how that works. <br> [CV]: I think, the idea of having classes of sensors is a good idea. Some sensors will generate events or state updates that are only of local interest, others would output their events/state updates on each and every scene instance. I would volunteer to do a proposal via x3d-public mailing list, OK? <br> <br> <br> <br> <br> <br> <br> <br> 4. why first scene bombs and avatar doesn’t move in 2nd scene <br> A. good question, I haven’t reproduced that error with elevator3.x3d. Elevator2.x3d bombs sometimes for me when I mouse-over a sensor. That could be the bug. It's bombing because freewrl programmer assumed the nodes would have DEF names <br> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c%5Bhttps://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c%5D%5Bhttps://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c%5Bhttps://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c%5D%5D">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c][https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c]]</a> <br> L.2565 <br> const char* def = getNodeName(fromnode); <br> int fromNode = hash37(def); <br> and it bombs when doing a hash37 on a NULL string. <br> [CV]: my first idea was it could be caused by malformed DIS Comment PDUs -> I attached the .pcap from TEST-003 (-> test-003-20231221-elevator3-single-user.pcap) -> Frame No. 247, 259, 281, 284 are malformed <br> [CV2]: CONFIRMED, the crash was caused by the missing DEF name in the <Transform> node that the <TouchSensor> is a child of. Malformed comment PDUs could still be found in the .pcap, even if the DEF name had been added <br> <br> -Doug <br> <br> <br> ________________________________________ <br> From: Christoph Valentin via FreeWRL-develop <<a href="mailto:fre...@li...">fre...@li...</a>> <br> Sent: December 21, 2023 4:15 AM <br> To: Development for the FreeWRL X3D viewer. <br> Cc: Christoph Valentin; <a href="mailto:r....@ka...">r....@ka...</a>; Kevin; John Carlson <br> Subject: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) <br> <br> Dear developers of FreeWrl, <br> <br> you find the information about today's test session at <a href="https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm%5Bhttps://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm%5D%5Bhttps://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm%5Bhttps://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm%5D%5D">https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm][https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm]]</a> <br> User: doug <br> Passwd: freewrl <br> <br> <br> <br> Follows a copy of the most important text: <br> <br> At a test session in the morning of Dec 21st, 2023, I tried to nail down the most important behavioral shortcomings of the elevator3.x3d scene, when using it on FreeWrl 6.4 on my private Windows laptop <br> <br> <br> <br> TEST-003: Single Instance Test, basic wireshark trace <br> <br> Demo Video: <a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY%5D%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY%5D%5D%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY%5D%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY%5D%5D%5D">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY]][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY]]]</a> <br> Cloud Password for the video: HalloWelt <br> <br> - Why does the FreeWrl 6.4 output that nasty logs that fill the whole display? <br> <br> - When assuming the DIS Comment PDUs are caused by both sensors of the scene, i.e. by the TouchSensor and by the TimeSensor, then the question arises: why do we need traffic for the TimeSensor, when we have already the touch event of the TouchSensor propagated thru the network? Isn't that redundant information? <br> <br> <br> <br> TEST-004: Two Instances Test (one machine), behavioral assessment <br> <br> Demo Video: <a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p%5D%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p%5D%5D%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p%5D%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p%5Bhttps://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p%5D%5D%5D">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p]][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p]]]</a> <br> Cloud Password for the video: HalloWelt <br> <br> - Why does the avatar of the first instance appear at the second instance, only after the user on the first instance moves a bit? <br> - Why does the elevator in the first instance NOT start to move, after I have touched the button in the second instance? <br> - Why does the first instance crash, soon after I touch the button in the second? <br> <br> Have a nice day <br> <br> Yours <br> CP/V <br> <br> <br> _______________________________________________ <br> FreeWRL-develop mailing list <br> <a href="mailto:Fre...@li...">Fre...@li...</a> <br> <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop%5Bhttps://lists.sourceforge.net/lists/listinfo/freewrl-develop%5D%5Bhttps://lists.sourceforge.net/lists/listinfo/freewrl-develop%5Bhttps://lists.sourceforge.net/lists/listinfo/freewrl-develop%5D%5D_______________________________________________">https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop][https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop]]_______________________________________________</a> FreeWRL-develop mailing list <a href="mailto:Fre...@li...">Fre...@li...</a> <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop%5Bhttps://lists.sourceforge.net/lists/listinfo/freewrl-develop%5D_______________________________________________">https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop]_______________________________________________</a> FreeWRL-develop mailing list <a href="mailto:Fre...@li...">Fre...@li...</a> <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop%5Bhttps://lists.sourceforge.net/lists/listinfo/freewrl-develop%5D">https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop]</a> <br> </blockquote> </div> </div> </blockquote></div></body> </html> |
From: John C. <yot...@gm...> - 2023-12-29 04:16:37
|
There might be a connect/disconnect PDU in DIS. On Thu, Dec 28, 2023 at 3:58 PM Christoph Valentin < chr...@gm...> wrote: > Dear Doug, Dear FreeWrl community, > > First and most important: you were right, the crash happened, because > FreeWrl expects DEF names (at least in the current experimental > implementation) on each sensor node and on each grouping node that a sensor > node is attached to (at least I could avoid the one crash, by adding a DEF > name to the <Transform> node that the <TouchSensor> is a child of). > > Second: I am adding a few notes inline, marked by [CV2], which might lead > to further discussion. > > Third: Currently, as of 2023-12-28 10pm CET, we are having problems with > the routing of IP multicast datagrams in our VPN, but we are confident the > problems are on our side. > > I will send a last e-mail with a link to a final report, as soon as we > will have solved our local problems. > > Have a good NewYear > CP/V > > > > Gesendet: Freitag, 22. Dezember 2023 um 13:06 Uhr > Von: "Christoph Valentin via FreeWRL-develop" < > fre...@li...> > An: "doug sanden" <hig...@ho...> > Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." < > r....@ka...>, "Kevin" <kl...@ya...>, "Development for the FreeWRL > X3D viewer." <fre...@li...>, "John Carlson" < > yot...@gm...> > Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) > > And the .pcap from TEST-004, where the crash actually happened > > Gesendet: Freitag, 22. Dezember 2023 um 12:26 Uhr > Von: "Christoph Valentin via FreeWRL-develop" < > fre...@li...> > An: "doug sanden" <hig...@ho...> > Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." < > r....@ka...>, "Kevin" <kl...@ya...>, "Development for the FreeWRL > X3D viewer." <fre...@li...>, "John Carlson" < > yot...@gm...> > Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) > > Hi Doug, > > Thank you for the fast response. Please find my comments inline (marked > with [CV]). > > Have a nice day > Christoph > > Gesendet: Donnerstag, 21. Dezember 2023 um 16:45 Uhr > Von: "doug sanden" <hig...@ho...> > An: "Development for the FreeWRL X3D viewer." < > fre...@li...> > Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." < > r....@ka...>, "Kevin" <kl...@ya...>, "John Carlson" < > yot...@gm...> > Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) > > > > > > > > 1. why so noisy on the console > A. I don’t get the noise, can you send me a few lines and I’ll search for > the strings > [CV]: Unfortunately, I do not know, where FreeWRL stores the logs (can you > tell me?) So I took a screen shot (-> attached noisy-console.jpg) > > > > > > > > 2. why first avatar doesn’t show up in 2nd scene until it it moves? > A. CONFIRMED. I don’t know, but likely nothing in freewrl is triggering a > send > > https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c > L.2611 > if (!changed) { > return pdus; > } > - in general an app doesn’t know how many others are logged in, and when > they log in/out > - in theory there could be a timespan whereby if you don’t move, it sends > updates anyway, on a Heartbeat > - or it tracks events from others and when it sees a new user, sends a > pose update > -- and that could be programmed in freewrl > [CV]: I'd suggest to send EntityState PDU for the user's/avatar's position > regularly (e.g. every second), if the user does not move. This seems to be > the simplest solution. However, we would have to check with the IEEE DIS > standard, what they say about this. I would volunteer to do a re-test after > this implementation. > [CV2]: at today's test session, we noticed that the avatar of the other > user is not removed, when the other instance quits the FreeWrl player. > That's another error, but probably the same root cause. > > > > > > > > 3. why timesensor is sent > A. good question. I think the freewrl programmer just did all sensor nodes > because they all pass through the same choke point in freewrl. > > https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c][https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c]] > L. 6872 sendSensorEvents() > There could be classes of sensors. Perhaps just the touch sinks should be > sent. Or perhaps TimeSensor is special and needs to be synchronized in a > special way. Or perhaps there needs to be a special Synch node that > timesensors route through. > An easy fix would be to filter out timesensor events so they aren't sent > and see how that works. > [CV]: I think, the idea of having classes of sensors is a good idea. Some > sensors will generate events or state updates that are only of local > interest, others would output their events/state updates on each and every > scene instance. I would volunteer to do a proposal via x3d-public mailing > list, OK? > > > > > > > > 4. why first scene bombs and avatar doesn’t move in 2nd scene > A. good question, I haven’t reproduced that error with elevator3.x3d. > Elevator2.x3d bombs sometimes for me when I mouse-over a sensor. That could > be the bug. It's bombing because freewrl programmer assumed the nodes would > have DEF names > > https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c][https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c]] > L.2565 > const char* def = getNodeName(fromnode); > int fromNode = hash37(def); > and it bombs when doing a hash37 on a NULL string. > [CV]: my first idea was it could be caused by malformed DIS Comment PDUs > -> I attached the .pcap from TEST-003 (-> > test-003-20231221-elevator3-single-user.pcap) -> Frame No. 247, 259, 281, > 284 are malformed > [CV2]: CONFIRMED, the crash was caused by the missing DEF name in the > <Transform> node that the <TouchSensor> is a child of. Malformed comment > PDUs could still be found in the .pcap, even if the DEF name had been added > > -Doug > > > ________________________________________ > From: Christoph Valentin via FreeWRL-develop < > fre...@li...> > Sent: December 21, 2023 4:15 AM > To: Development for the FreeWRL X3D viewer. > Cc: Christoph Valentin; r....@ka...; Kevin; John Carlson > Subject: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) > > Dear developers of FreeWrl, > > you find the information about today's test session at > https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm][https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm]] > User: doug > Passwd: freewrl > > > > Follows a copy of the most important text: > > At a test session in the morning of Dec 21st, 2023, I tried to nail down > the most important behavioral shortcomings of the elevator3.x3d scene, when > using it on FreeWrl 6.4 on my private Windows laptop > > > > TEST-003: Single Instance Test, basic wireshark trace > > Demo Video: > https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY]][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY]]] > Cloud Password for the video: HalloWelt > > - Why does the FreeWrl 6.4 output that nasty logs that fill the whole > display? > > - When assuming the DIS Comment PDUs are caused by both sensors of the > scene, i.e. by the TouchSensor and by the TimeSensor, then the question > arises: why do we need traffic for the TimeSensor, when we have already the > touch event of the TouchSensor propagated thru the network? Isn't that > redundant information? > > > > TEST-004: Two Instances Test (one machine), behavioral assessment > > Demo Video: > https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p]][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p]]] > Cloud Password for the video: HalloWelt > > - Why does the avatar of the first instance appear at the second instance, > only after the user on the first instance moves a bit? > - Why does the elevator in the first instance NOT start to move, after I > have touched the button in the second instance? > - Why does the first instance crash, soon after I touch the button in the > second? > > Have a nice day > > Yours > CP/V > > > _______________________________________________ > FreeWRL-develop mailing list > Fre...@li... > > https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop][https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop]]_______________________________________________ > FreeWRL-develop mailing list Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop]_______________________________________________ > FreeWRL-develop mailing list Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop] > |
From: Christoph V. <chr...@gm...> - 2023-12-28 21:59:15
|
Dear Doug, Dear FreeWrl community, First and most important: you were right, the crash happened, because FreeWrl expects DEF names (at least in the current experimental implementation) on each sensor node and on each grouping node that a sensor node is attached to (at least I could avoid the one crash, by adding a DEF name to the <Transform> node that the <TouchSensor> is a child of). Second: I am adding a few notes inline, marked by [CV2], which might lead to further discussion. Third: Currently, as of 2023-12-28 10pm CET, we are having problems with the routing of IP multicast datagrams in our VPN, but we are confident the problems are on our side. I will send a last e-mail with a link to a final report, as soon as we will have solved our local problems. Have a good NewYear CP/V Gesendet: Freitag, 22. Dezember 2023 um 13:06 Uhr Von: "Christoph Valentin via FreeWRL-develop" <fre...@li...> An: "doug sanden" <hig...@ho...> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." <r....@ka...>, "Kevin" <kl...@ya...>, "Development for the FreeWRL X3D viewer." <fre...@li...>, "John Carlson" <yot...@gm...> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) And the .pcap from TEST-004, where the crash actually happened Gesendet: Freitag, 22. Dezember 2023 um 12:26 Uhr Von: "Christoph Valentin via FreeWRL-develop" <fre...@li...> An: "doug sanden" <hig...@ho...> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." <r....@ka...>, "Kevin" <kl...@ya...>, "Development for the FreeWRL X3D viewer." <fre...@li...>, "John Carlson" <yot...@gm...> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) Hi Doug, Thank you for the fast response. Please find my comments inline (marked with [CV]). Have a nice day Christoph Gesendet: Donnerstag, 21. Dezember 2023 um 16:45 Uhr Von: "doug sanden" <hig...@ho...> An: "Development for the FreeWRL X3D viewer." <fre...@li...> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." <r....@ka...>, "Kevin" <kl...@ya...>, "John Carlson" <yot...@gm...> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) 1. why so noisy on the console A. I don’t get the noise, can you send me a few lines and I’ll search for the strings [CV]: Unfortunately, I do not know, where FreeWRL stores the logs (can you tell me?) So I took a screen shot (-> attached noisy-console.jpg) 2. why first avatar doesn’t show up in 2nd scene until it it moves? A. CONFIRMED. I don’t know, but likely nothing in freewrl is triggering a send https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c L.2611 if (!changed) { return pdus; } - in general an app doesn’t know how many others are logged in, and when they log in/out - in theory there could be a timespan whereby if you don’t move, it sends updates anyway, on a Heartbeat - or it tracks events from others and when it sees a new user, sends a pose update -- and that could be programmed in freewrl [CV]: I'd suggest to send EntityState PDU for the user's/avatar's position regularly (e.g. every second), if the user does not move. This seems to be the simplest solution. However, we would have to check with the IEEE DIS standard, what they say about this. I would volunteer to do a re-test after this implementation. [CV2]: at today's test session, we noticed that the avatar of the other user is not removed, when the other instance quits the FreeWrl player. That's another error, but probably the same root cause. 3. why timesensor is sent A. good question. I think the freewrl programmer just did all sensor nodes because they all pass through the same choke point in freewrl. https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c][https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c]] L. 6872 sendSensorEvents() There could be classes of sensors. Perhaps just the touch sinks should be sent. Or perhaps TimeSensor is special and needs to be synchronized in a special way. Or perhaps there needs to be a special Synch node that timesensors route through. An easy fix would be to filter out timesensor events so they aren't sent and see how that works. [CV]: I think, the idea of having classes of sensors is a good idea. Some sensors will generate events or state updates that are only of local interest, others would output their events/state updates on each and every scene instance. I would volunteer to do a proposal via x3d-public mailing list, OK? 4. why first scene bombs and avatar doesn’t move in 2nd scene A. good question, I haven’t reproduced that error with elevator3.x3d. Elevator2.x3d bombs sometimes for me when I mouse-over a sensor. That could be the bug. It's bombing because freewrl programmer assumed the nodes would have DEF names https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c][https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c[https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c]] L.2565 const char* def = getNodeName(fromnode); int fromNode = hash37(def); and it bombs when doing a hash37 on a NULL string. [CV]: my first idea was it could be caused by malformed DIS Comment PDUs -> I attached the .pcap from TEST-003 (-> test-003-20231221-elevator3-single-user.pcap) -> Frame No. 247, 259, 281, 284 are malformed [CV2]: CONFIRMED, the crash was caused by the missing DEF name in the <Transform> node that the <TouchSensor> is a child of. Malformed comment PDUs could still be found in the .pcap, even if the DEF name had been added -Doug ________________________________________ From: Christoph Valentin via FreeWRL-develop <fre...@li...> Sent: December 21, 2023 4:15 AM To: Development for the FreeWRL X3D viewer. Cc: Christoph Valentin; r....@ka...; Kevin; John Carlson Subject: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) Dear developers of FreeWrl, you find the information about today's test session at https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm][https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm[https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm]] User: doug Passwd: freewrl Follows a copy of the most important text: At a test session in the morning of Dec 21st, 2023, I tried to nail down the most important behavioral shortcomings of the elevator3.x3d scene, when using it on FreeWrl 6.4 on my private Windows laptop TEST-003: Single Instance Test, basic wireshark trace Demo Video: https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY]][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY][https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY]]] Cloud Password for the video: HalloWelt - Why does the FreeWrl 6.4 output that nasty logs that fill the whole display? - When assuming the DIS Comment PDUs are caused by both sensors of the scene, i.e. by the TouchSensor and by the TimeSensor, then the question arises: why do we need traffic for the TimeSensor, when we have already the touch event of the TouchSensor propagated thru the network? Isn't that redundant information? TEST-004: Two Instances Test (one machine), behavioral assessment Demo Video: https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p]][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p][https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p]]] Cloud Password for the video: HalloWelt - Why does the avatar of the first instance appear at the second instance, only after the user on the first instance moves a bit? - Why does the elevator in the first instance NOT start to move, after I have touched the button in the second instance? - Why does the first instance crash, soon after I touch the button in the second? Have a nice day Yours CP/V _______________________________________________ FreeWRL-develop mailing list Fre...@li... https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop][https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop]]_______________________________________________ FreeWRL-develop mailing list Fre...@li... https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop]_______________________________________________ FreeWRL-develop mailing list Fre...@li... https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop] |
From: Christoph V. <chr...@gm...> - 2023-12-22 12:07:04
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>And the .pcap from TEST-004, where the crash actually happened</div> <div> <div> <div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div style="margin:0 0 10px 0;"><b>Gesendet:</b> Freitag, 22. Dezember 2023 um 12:26 Uhr<br/> <b>Von:</b> "Christoph Valentin via FreeWRL-develop" <fre...@li...><br/> <b>An:</b> "doug sanden" <hig...@ho...><br/> <b>Cc:</b> "Christoph Valentin" <chr...@gm...>, "r....@ka..." <r....@ka...>, "Kevin" <kl...@ya...>, "Development for the FreeWRL X3D viewer." <fre...@li...>, "John Carlson" <yot...@gm...><br/> <b>Betreff:</b> Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004)</div> <div name="quoted-content"> <div style="font-family: Verdana;font-size: 12.0px;"> <div><br/> Hi Doug,<br/> <br/> Thank you for the fast response. Please find my comments inline (marked with [CV]).<br/> <br/> Have a nice day<br/> Christoph<br/> <br/> <br/> <br/> Gesendet: Donnerstag, 21. Dezember 2023 um 16:45 Uhr<br/> Von: "doug sanden" <hig...@ho...><br/> An: "Development for the FreeWRL X3D viewer." <fre...@li...><br/> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." <r....@ka...>, "Kevin" <kl...@ya...>, "John Carlson" <yot...@gm...><br/> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004)</div> <div> </div> <div> </div> <div>1. why so noisy on the console<br/> A. I don’t get the noise, can you send me a few lines and I’ll search for the strings</div> <div>[CV]: Unfortunately, I do not know, where FreeWRL stores the logs (can you tell me?) So I took a screen shot (-> attached noisy-console.jpg)</div> <div> </div> <div><br/> 2. why first avatar doesn’t show up in 2nd scene until it it moves?<br/> A. CONFIRMED. I don’t know, but likely nothing in freewrl is triggering a send<br/> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a><br/> L.2611<br/> if (!changed) {<br/> return pdus;<br/> }<br/> - in general an app doesn’t know how many others are logged in, and when they log in/out<br/> - in theory there could be a timespan whereby if you don’t move, it sends updates anyway, on a Heartbeat<br/> - or it tracks events from others and when it sees a new user, sends a pose update<br/> -- and that could be programmed in freewrl</div> <div>[CV]: I'd suggest to send EntityState PDU for the user's/avatar's position regularly (e.g. every second), if the user does not move. This seems to be the simplest solution. However, we would have to check with the IEEE DIS standard, what they say about this. I would volunteer to do a re-test after this implementation.</div> <div> </div> <div><br/> 3. why timesensor is sent<br/> A. good question. I think the freewrl programmer just did all sensor nodes because they all pass through the same choke point in freewrl.<br/> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c</a>[<a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c</a>]<br/> L. 6872 sendSensorEvents()<br/> There could be classes of sensors. Perhaps just the touch sinks should be sent. Or perhaps TimeSensor is special and needs to be synchronized in a special way. Or perhaps there needs to be a special Synch node that timesensors route through.<br/> An easy fix would be to filter out timesensor events so they aren't sent and see how that works.</div> <div>[CV]: I think, the idea of having classes of sensors is a good idea. Some sensors will generate events or state updates that are only of local interest, others would output their events/state updates on each and every scene instance. I would volunteer to do a proposal via x3d-public mailing list, OK?</div> <div> </div> <div> </div> <div>4. why first scene bombs and avatar doesn’t move in 2nd scene<br/> A. good question, I haven’t reproduced that error with elevator3.x3d. Elevator2.x3d bombs sometimes for me when I mouse-over a sensor. That could be the bug. It's bombing because freewrl programmer assumed the nodes would have DEF names<br/> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a>[<a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a>]<br/> L.2565<br/> const char* def = getNodeName(fromnode);<br/> int fromNode = hash37(def);<br/> and it bombs when doing a hash37 on a NULL string.</div> <div>[CV]: my first idea was it could be caused by malformed DIS Comment PDUs -> I attached the .pcap from TEST-003 (-> test-003-20231221-elevator3-single-user.pcap) -> Frame No. 247, 259, 281, 284 are malformed</div> <div> </div> <div><br/> <br/> -Doug<br/> <br/> <br/> ________________________________________<br/> From: Christoph Valentin via FreeWRL-develop <fre...@li...><br/> Sent: December 21, 2023 4:15 AM<br/> To: Development for the FreeWRL X3D viewer.<br/> Cc: Christoph Valentin; r....@ka...; Kevin; John Carlson<br/> Subject: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004)<br/> <br/> Dear developers of FreeWrl,<br/> <br/> you find the information about today's test session at <a href="https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm" target="_blank">https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm</a>[<a href="https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm" target="_blank">https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm</a>]<br/> User: doug<br/> Passwd: freewrl<br/> <br/> <br/> <br/> Follows a copy of the most important text:<br/> <br/> At a test session in the morning of Dec 21st, 2023, I tried to nail down the most important behavioral shortcomings of the elevator3.x3d scene, when using it on FreeWrl 6.4 on my private Windows laptop<br/> <br/> <br/> <br/> TEST-003: Single Instance Test, basic wireshark trace<br/> <br/> Demo Video: <a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>][<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>]]<br/> Cloud Password for the video: HalloWelt<br/> <br/> - Why does the FreeWrl 6.4 output that nasty logs that fill the whole display?<br/> <br/> - When assuming the DIS Comment PDUs are caused by both sensors of the scene, i.e. by the TouchSensor and by the TimeSensor, then the question arises: why do we need traffic for the TimeSensor, when we have already the touch event of the TouchSensor propagated thru the network? Isn't that redundant information?<br/> <br/> <br/> <br/> TEST-004: Two Instances Test (one machine), behavioral assessment<br/> <br/> Demo Video: <a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>][<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>]]<br/> Cloud Password for the video: HalloWelt<br/> <br/> - Why does the avatar of the first instance appear at the second instance, only after the user on the first instance moves a bit?<br/> - Why does the elevator in the first instance NOT start to move, after I have touched the button in the second instance?<br/> - Why does the first instance crash, soon after I touch the button in the second?<br/> <br/> Have a nice day<br/> <br/> Yours<br/> CP/V<br/> <br/> <br/> _______________________________________________<br/> FreeWRL-develop mailing list<br/> Fre...@li...<br/> <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>[<a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>]</div> </div> _______________________________________________ FreeWRL-develop mailing list Fre...@li... <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a></div> </div> </div> </div></div></body></html> |
From: Christoph V. <chr...@gm...> - 2023-12-22 11:26:54
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div><br/> Hi Doug,<br/> <br/> Thank you for the fast response. Please find my comments inline (marked with [CV]).<br/> <br/> Have a nice day<br/> Christoph<br/> <br/> <br/> <br/> Gesendet: Donnerstag, 21. Dezember 2023 um 16:45 Uhr<br/> Von: "doug sanden" <hig...@ho...><br/> An: "Development for the FreeWRL X3D viewer." <fre...@li...><br/> Cc: "Christoph Valentin" <chr...@gm...>, "r....@ka..." <r....@ka...>, "Kevin" <kl...@ya...>, "John Carlson" <yot...@gm...><br/> Betreff: Re: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004)</div> <div> </div> <div> </div> <div>1. why so noisy on the console<br/> A. I don’t get the noise, can you send me a few lines and I’ll search for the strings</div> <div>[CV]: Unfortunately, I do not know, where FreeWRL stores the logs (can you tell me?) So I took a screen shot (-> attached noisy-console.jpg)</div> <div> </div> <div><br/> 2. why first avatar doesn’t show up in 2nd scene until it it moves?<br/> A. CONFIRMED. I don’t know, but likely nothing in freewrl is triggering a send<br/> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a><br/> L.2611<br/> if (!changed) {<br/> return pdus;<br/> }<br/> - in general an app doesn’t know how many others are logged in, and when they log in/out<br/> - in theory there could be a timespan whereby if you don’t move, it sends updates anyway, on a Heartbeat<br/> - or it tracks events from others and when it sees a new user, sends a pose update<br/> -- and that could be programmed in freewrl</div> <div>[CV]: I'd suggest to send EntityState PDU for the user's/avatar's position regularly (e.g. every second), if the user does not move. This seems to be the simplest solution. However, we would have to check with the IEEE DIS standard, what they say about this. I would volunteer to do a re-test after this implementation.</div> <div> </div> <div><br/> 3. why timesensor is sent<br/> A. good question. I think the freewrl programmer just did all sensor nodes because they all pass through the same choke point in freewrl.<br/> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c</a>[<a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c</a>]<br/> L. 6872 sendSensorEvents()<br/> There could be classes of sensors. Perhaps just the touch sinks should be sent. Or perhaps TimeSensor is special and needs to be synchronized in a special way. Or perhaps there needs to be a special Synch node that timesensors route through.<br/> An easy fix would be to filter out timesensor events so they aren't sent and see how that works.</div> <div>[CV]: I think, the idea of having classes of sensors is a good idea. Some sensors will generate events or state updates that are only of local interest, others would output their events/state updates on each and every scene instance. I would volunteer to do a proposal via x3d-public mailing list, OK?</div> <div> </div> <div> </div> <div>4. why first scene bombs and avatar doesn’t move in 2nd scene<br/> A. good question, I haven’t reproduced that error with elevator3.x3d. Elevator2.x3d bombs sometimes for me when I mouse-over a sensor. That could be the bug. It's bombing because freewrl programmer assumed the nodes would have DEF names<br/> <a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a>[<a href="https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c" target="_blank">https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c</a>]<br/> L.2565<br/> const char* def = getNodeName(fromnode);<br/> int fromNode = hash37(def);<br/> and it bombs when doing a hash37 on a NULL string.</div> <div>[CV]: my first idea was it could be caused by malformed DIS Comment PDUs -> I attached the .pcap from TEST-003 (-> test-003-20231221-elevator3-single-user.pcap) -> Frame No. 247, 259, 281, 284 are malformed</div> <div> </div> <div><br/> <br/> -Doug<br/> <br/> <br/> ________________________________________<br/> From: Christoph Valentin via FreeWRL-develop <fre...@li...><br/> Sent: December 21, 2023 4:15 AM<br/> To: Development for the FreeWRL X3D viewer.<br/> Cc: Christoph Valentin; r....@ka...; Kevin; John Carlson<br/> Subject: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004)<br/> <br/> Dear developers of FreeWrl,<br/> <br/> you find the information about today's test session at <a href="https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm" target="_blank">https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm</a>[<a href="https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm" target="_blank">https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm</a>]<br/> User: doug<br/> Passwd: freewrl<br/> <br/> <br/> <br/> Follows a copy of the most important text:<br/> <br/> At a test session in the morning of Dec 21st, 2023, I tried to nail down the most important behavioral shortcomings of the elevator3.x3d scene, when using it on FreeWrl 6.4 on my private Windows laptop<br/> <br/> <br/> <br/> TEST-003: Single Instance Test, basic wireshark trace<br/> <br/> Demo Video: <a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>][<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY</a>]]<br/> Cloud Password for the video: HalloWelt<br/> <br/> - Why does the FreeWrl 6.4 output that nasty logs that fill the whole display?<br/> <br/> - When assuming the DIS Comment PDUs are caused by both sensors of the scene, i.e. by the TouchSensor and by the TimeSensor, then the question arises: why do we need traffic for the TimeSensor, when we have already the touch event of the TouchSensor propagated thru the network? Isn't that redundant information?<br/> <br/> <br/> <br/> TEST-004: Two Instances Test (one machine), behavioral assessment<br/> <br/> Demo Video: <a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>][<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>[<a href="https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p" target="_blank">https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p</a>]]<br/> Cloud Password for the video: HalloWelt<br/> <br/> - Why does the avatar of the first instance appear at the second instance, only after the user on the first instance moves a bit?<br/> - Why does the elevator in the first instance NOT start to move, after I have touched the button in the second instance?<br/> - Why does the first instance crash, soon after I touch the button in the second?<br/> <br/> Have a nice day<br/> <br/> Yours<br/> CP/V<br/> <br/> <br/> _______________________________________________<br/> FreeWRL-develop mailing list<br/> Fre...@li...<br/> <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>[<a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/freewrl-develop</a>]</div></div></body></html> |
From: John C. <yot...@gm...> - 2023-12-22 06:33:56
|
I think routes work on either name fields or DEF fields? On Thu, Dec 21, 2023 at 9:45 AM doug sanden <hig...@ho...> wrote: > 1. why so noisy on the console > A. I don’t get the noise, can you send me a few lines and I’ll search for > the strings > 2. why first avatar doesn’t show up in 2nd scene until it it moves? > A. CONFIRMED. I don’t know, but likely nothing in freewrl is triggering a > send > > https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c > L.2611 > if (!changed) { > return pdus; > } > - in general an app doesn’t know how many others are logged in, and when > they log in/out > - in theory there could be a timespan whereby if you don’t move, it sends > updates anyway, on a Heartbeat > - or it tracks events from others and when it sees a new user, sends a > pose update > -- and that could be programmed in freewrl > 3. why timesensor is sent > A. good question. I think the freewrl programmer just did all sensor nodes > because they all pass through the same choke point in freewrl. > > https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c > L. 6872 sendSensorEvents() > There could be classes of sensors. Perhaps just the touch sinks should be > sent. Or perhaps TimeSensor is special and needs to be synchronized in a > special way. Or perhaps there needs to be a special Synch node that > timesensors route through. > An easy fix would be to filter out timesensor events so they aren't sent > and see how that works. > 4. why first scene bombs and avatar doesn’t move in 2nd scene > A. good question, I haven’t reproduced that error with elevator3.x3d. > Elevator2.x3d bombs sometimes for me when I mouse-over a sensor. That could > be the bug. It's bombing because freewrl programmer assumed the nodes > would have DEF names > > https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c > L.2565 > const char* def = > getNodeName(fromnode); > int fromNode = hash37(def); > and it bombs when doing a hash37 on a NULL string. > > -Doug > > > ________________________________________ > From: Christoph Valentin via FreeWRL-develop < > fre...@li...> > Sent: December 21, 2023 4:15 AM > To: Development for the FreeWRL X3D viewer. > Cc: Christoph Valentin; r....@ka...; Kevin; John Carlson > Subject: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) > > Dear developers of FreeWrl, > > you find the information about today's test session at > https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm > User: doug > Passwd: freewrl > > > > Follows a copy of the most important text: > > At a test session in the morning of Dec 21st, 2023, I tried to nail down > the most important behavioral shortcomings of the elevator3.x3d scene, when > using it on FreeWrl 6.4 on my private Windows laptop > > > > TEST-003: Single Instance Test, basic wireshark trace > > Demo Video: > https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY] > Cloud Password for the video: HalloWelt > > - Why does the FreeWrl 6.4 output that nasty logs that fill the whole > display? > > - When assuming the DIS Comment PDUs are caused by both sensors of the > scene, i.e. by the TouchSensor and by the TimeSensor, then the question > arises: why do we need traffic for the TimeSensor, when we have already the > touch event of the TouchSensor propagated thru the network? Isn't that > redundant information? > > > > TEST-004: Two Instances Test (one machine), behavioral assessment > > Demo Video: > https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p] > Cloud Password for the video: HalloWelt > > - Why does the avatar of the first instance appear at the second instance, > only after the user on the first instance moves a bit? > - Why does the elevator in the first instance NOT start to move, after I > have touched the button in the second instance? > - Why does the first instance crash, soon after I touch the button in the > second? > > Have a nice day > > Yours > CP/V > > > _______________________________________________ > FreeWRL-develop mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freewrl-develop > |
From: doug s. <hig...@ho...> - 2023-12-21 15:45:50
|
1. why so noisy on the console A. I don’t get the noise, can you send me a few lines and I’ll search for the strings 2. why first avatar doesn’t show up in 2nd scene until it it moves? A. CONFIRMED. I don’t know, but likely nothing in freewrl is triggering a send https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c L.2611 if (!changed) { return pdus; } - in general an app doesn’t know how many others are logged in, and when they log in/out - in theory there could be a timespan whereby if you don’t move, it sends updates anyway, on a Heartbeat - or it tracks events from others and when it sees a new user, sends a pose update -- and that could be programmed in freewrl 3. why timesensor is sent A. good question. I think the freewrl programmer just did all sensor nodes because they all pass through the same choke point in freewrl. https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/main/MainLoop.c L. 6872 sendSensorEvents() There could be classes of sensors. Perhaps just the touch sinks should be sent. Or perhaps TimeSensor is special and needs to be synchronized in a special way. Or perhaps there needs to be a special Synch node that timesensors route through. An easy fix would be to filter out timesensor events so they aren't sent and see how that works. 4. why first scene bombs and avatar doesn’t move in 2nd scene A. good question, I haven’t reproduced that error with elevator3.x3d. Elevator2.x3d bombs sometimes for me when I mouse-over a sensor. That could be the bug. It's bombing because freewrl programmer assumed the nodes would have DEF names https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_DIS.c L.2565 const char* def = getNodeName(fromnode); int fromNode = hash37(def); and it bombs when doing a hash37 on a NULL string. -Doug ________________________________________ From: Christoph Valentin via FreeWRL-develop <fre...@li...> Sent: December 21, 2023 4:15 AM To: Development for the FreeWRL X3D viewer. Cc: Christoph Valentin; r....@ka...; Kevin; John Carlson Subject: [FreeWRL-develop] Test Session 2023-12-21 (TEST-003, TEST-004) Dear developers of FreeWrl, you find the information about today's test session at https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm User: doug Passwd: freewrl Follows a copy of the most important text: At a test session in the morning of Dec 21st, 2023, I tried to nail down the most important behavioral shortcomings of the elevator3.x3d scene, when using it on FreeWrl 6.4 on my private Windows laptop TEST-003: Single Instance Test, basic wireshark trace Demo Video: https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY] Cloud Password for the video: HalloWelt - Why does the FreeWrl 6.4 output that nasty logs that fill the whole display? - When assuming the DIS Comment PDUs are caused by both sensors of the scene, i.e. by the TouchSensor and by the TimeSensor, then the question arises: why do we need traffic for the TimeSensor, when we have already the touch event of the TouchSensor propagated thru the network? Isn't that redundant information? TEST-004: Two Instances Test (one machine), behavioral assessment Demo Video: https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p] Cloud Password for the video: HalloWelt - Why does the avatar of the first instance appear at the second instance, only after the user on the first instance moves a bit? - Why does the elevator in the first instance NOT start to move, after I have touched the button in the second instance? - Why does the first instance crash, soon after I touch the button in the second? Have a nice day Yours CP/V _______________________________________________ FreeWRL-develop mailing list Fre...@li... https://lists.sourceforge.net/lists/listinfo/freewrl-develop |
From: Christoph V. <chr...@gm...> - 2023-12-21 11:15:37
|
Dear developers of FreeWrl, you find the information about today's test session at https://lc-soc-lc.at/blackboard/member-space/yeti/private/freewrl-initialtests.htm User: doug Passwd: freewrl Follows a copy of the most important text: At a test session in the morning of Dec 21st, 2023, I tried to nail down the most important behavioral shortcomings of the elevator3.x3d scene, when using it on FreeWrl 6.4 on my private Windows laptop TEST-003: Single Instance Test, basic wireshark trace Demo Video: https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY[https://lc-soc-lc.at/owncloud/index.php/s/x0t3Hn4U5MYV1pY] Cloud Password for the video: HalloWelt - Why does the FreeWrl 6.4 output that nasty logs that fill the whole display? - When assuming the DIS Comment PDUs are caused by both sensors of the scene, i.e. by the TouchSensor and by the TimeSensor, then the question arises: why do we need traffic for the TimeSensor, when we have already the touch event of the TouchSensor propagated thru the network? Isn't that redundant information? TEST-004: Two Instances Test (one machine), behavioral assessment Demo Video: https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p[https://lc-soc-lc.at/owncloud/index.php/s/UxkgCKvWakBEg7p] Cloud Password for the video: HalloWelt - Why does the avatar of the first instance appear at the second instance, only after the user on the first instance moves a bit? - Why does the elevator in the first instance NOT start to move, after I have touched the button in the second instance? - Why does the first instance crash, soon after I touch the button in the second? Have a nice day Yours CP/V |
From: Christoph V. <chr...@gm...> - 2023-12-21 01:37:39
|
<html> <head> <meta name="viewport" content="width=device-width"> <meta http-equiv="Content-Type" content="text/vnd.ui.insecure+html;charset=utf-8"> </head> <body style="overflow-wrap:break-word; word-break: break-word;"><div class="mail_android_message" style="line-height: 1; padding: 0.5em">Hi John,<br/><br/>Thank you for your support.<br/><br/>I had a look to the .pcap I recorded.<br/><br/>I rather believe, one of the DIS Comment PDUs was malformed and the x3d player hung up therefore.<br/><br/>I will write a report on our society's internal web page and tell you the password, soon.<br/><br/>Give me two or three days, the time before Christmas is particularly busy, as every year :-).<br/><br/>Kr,<br/>CP/V<br/><br/>--<br/>Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.</div><div class="mail_android_quote" style="line-height: 1; padding: 0.3em"><html><body>Am 21.12.23, 01:11 schrieb John Carlson <yot...@gm...>:</body></html><blockquote class="gmail_quote" style="margin: 0.8ex 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div dir="auto"> I watched the video. Perhaps the cone got trapped in the elevator doorway? </div> <div dir="auto"> <br> </div> <div dir="auto"> John </div> <div> <br> <div class="gmail_quote"> <div class="gmail_attr" dir="ltr"> On Wed, Dec 20, 2023 at 11:41 AM Christoph Valentin via x3d-public <<a href="mailto:x3d...@we...">x3d...@we...</a>> wrote: <br> </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"> Doug, <br> <br> I have started with first tests of your elevator3.x3d example. <br> <br> Am now going to analyse the results. <br> <br> Here's a preliminary demo video: <a href="https://lc-soc-lc.at/owncloud/index.php/s/FQCi7ix1yUGHIUF">https://lc-soc-lc.at/owncloud/index.php/s/FQCi7ix1yUGHIUF</a> <br> <br> Cloud Password for the video: HalloWelt <br> <br> Have a nice holiday season <br> Christoph <br> <br> <br> <br> <br> Gesendet: Sonntag, 17. Dezember 2023 um 16:33 Uhr <br> Von: "Christoph Valentin via FreeWRL-develop" <<a href="mailto:fre...@li...">fre...@li...</a>> <br> An: "GPU Group" <<a href="mailto:gpu...@gm...">gpu...@gm...</a>> <br> Cc: "Christoph Valentin" <<a href="mailto:chr...@gm...">chr...@gm...</a>>, <a href="mailto:r....@ka...">r....@ka...</a>, "Kevin" <<a href="mailto:kl...@ya...">kl...@ya...</a>>, "Development for the FreeWRL X3D viewer." <<a href="mailto:fre...@li...">fre...@li...</a>> <br> Betreff: Re: [FreeWRL-develop] [x3d-public] web3d MMO > Sensor sharing via DIS <br> <br> Doug, <br> <br> Thank you for the information and for the suggestions. <br> <br> You can follow my project at our association's home page: <a href="https://lc-soc-lc.or.at/project-003-dexper/index.html">https://lc-soc-lc.or.at/project-003-dexper/index.html</a> <br> <br> <br> Today I entered following status: <br> <br> <br> 2023-12-17: started to analyse X3D v3.3 (ISO/IEC IS 19775-1:2013) - chapter 28 (DIS)2023-12-17: started to analyse elevator example from Doug S. <br> <br> Have a nice holiday season, <br> <br> Kr, <br> Christoph <br> <br> Gesendet: Sonntag, 17. Dezember 2023 um 15:39 Uhr <br> Von: "GPU Group" <<a href="mailto:gpu...@gm...">gpu...@gm...</a>> <br> An: "Christoph Valentin" <<a href="mailto:chr...@gm...">chr...@gm...</a>> <br> Cc: "Kevin" <<a href="mailto:kl...@ya...">kl...@ya...</a>>, "Development for the FreeWRL X3D viewer." <<a href="mailto:fre...@li...">fre...@li...</a>>, <a href="mailto:r....@ka...">r....@ka...</a> <br> Betreff: Re: Re: [x3d-public] web3d MMO > Sensor sharing via DIS <br> <br> Christoph,As long as using the same app for all communications, it's up to the app to choose a comment 'channel' number. I don't remember the exact terminology, but it seemed like there were plenty of channels, so an app can take one for its own purpose as long as no other app is using it in the same simulation. So it's not something the app user would need to worry about when using the same app for all instances. It's just when wanting to communicate between different apps, then app developers need to be coordinated on their use of channels. <br> -Doug <br> PS mor things that could be done on the topic: <br> 1. humanoid avatars. I used cones to represent the pose of avatars <br> 2. automated gait - automatically change standing/walking-pace/running motion of humanoid avatars based on speed of navigation - so as you navigate in your app, the other apps see your humanoid avatar walking/running fast enough to make sense for your speed <br> 3. inverse kinematics - as you mouse over a sensor to click, an arm would rise to point in the direction of the pointer, so other users can see you clicking <br> 4. conveyor-belt test - I did an elevator test in freewrl, but a conveyor test is harder, for example if your avatar gets in a vehicle that moves, does your avatar stay with the vehicle? I worked on something like it 15 years ago and found it a hard problem at that time and haven't tried it since <br> <br> On Sat, Dec 16, 2023 at 4:03 PM Christoph Valentin <<a href="mailto:chr...@gm...">chr...@gm...</a>[mailto:<a href="mailto:chr...@gm...">chr...@gm...</a>]> wrote:Hi Doug, <br> <br> May I ask a "silly question"? <br> <br> You write "[...]it broadcasts sensor events to other app instances via DIS CommentPdu[...]", <br> <br> where is this documented? I did not find anything in X3D v3.3 standard about CommentPdu. <br> <br> Would like to try it out during holiday season. <br> <br> Thanks <br> Christoph <br> <br> <br> Gesendet: Samstag, 17. Juni 2023 um 23:30 Uhr <br> Von: "GPU Group" <<a href="mailto:gpu...@gm...">gpu...@gm...</a>[mailto:<a href="mailto:gpu...@gm...">gpu...@gm...</a>]> <br> An: "Christoph Valentin" <<a href="mailto:chr...@gm...">chr...@gm...</a>[mailto:<a href="mailto:chr...@gm...">chr...@gm...</a>]> <br> Cc: "X3D Graphics public mailing list" <<a href="mailto:x3d...@we...">x3d...@we...</a>[mailto:<a href="mailto:x3d...@we...">x3d...@we...</a>]>, "Kevin" <<a href="mailto:kl...@ya...">kl...@ya...</a>[mailto:<a href="mailto:kl...@ya...">kl...@ya...</a>]>, "Roman Onic" <<a href="mailto:rom...@ko...">rom...@ko...</a>[mailto:<a href="mailto:rom...@ko...">rom...@ko...</a>]> <br> Betreff: Re: [x3d-public] web3d MMO > Sensor sharing via DIS <br> <br> Thanks Christoph. Hold on though -- I need to publish the current version of freewrl, could be a few weeks before I post .msi for windows. <br> -Doug <br> <br> On Sat, Jun 17, 2023 at 4:27 PM Christoph Valentin <<a href="mailto:chr...@gm...">chr...@gm...</a>[mailto:<a href="mailto:chr...@gm...">chr...@gm...</a>][mailto:<a href="mailto:chr...@gm...">chr...@gm...</a>[mailto:<a href="mailto:chr...@gm...">chr...@gm...</a>]]> wrote: <br> <br> Doug, <br> <br> This sounds really interesting. <br> <br> I hope I will find some time to try it soon. <br> <br> Will let you know my comments. <br> <br> Kr, <br> CP/V <br> -- <br> Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet. <br> <br> Am 18.06.23, 00:12 schrieb GPU Group <<a href="mailto:gpu...@gm...">gpu...@gm...</a>[mailto:<a href="mailto:gpu...@gm...">gpu...@gm...</a>][mailto:<a href="mailto:gpu...@gm...">gpu...@gm...</a>[mailto:<a href="mailto:gpu...@gm...">gpu...@gm...</a>]]>: <br> <br> <br> MMO - massively multiplayer online <br> DIS distributed interactive simulation - a web3d component 28 <br> CONCEPT: web3d browsers load identical scenes, and share sensor events, and each instance does its own routing diagram after sensor event is shared. <br> <a href="https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4%5Bhttps://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4%5D%5Bhttps://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4%5Bhttps://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4%5D%5D">https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4[https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4][https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4%5Bhttps://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4%5D]</a> <br> - 2 instances of freewrl with DIS activated, showing same elevator3.x3d scene <br> <a href="https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/%5Bhttps://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/%5D%5Bhttps://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/%5Bhttps://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/%5D%5D">https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/[https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/][https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/%5Bhttps://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/%5D]</a> <br> - in video we can see avatar of other instance as green cone <br> - when current scene clicks elevator up button, it relays that sensor click event to other app instance, which triggers the elevator in the other scene to go up at the same time <br> - the avatar in the other scene rides its elevator up, and sends its new avatar pose to the current scene, so appears they are riding up elevator together. <br> - the code sensor intercept point is general enough to capture TouchSensor, GeoTouchSensor, LineSensor, PointSensor (not web3d spec), PlaneSensor, MultiTouchSensor (not web3d spec), CylinderSensor, SphereSensor, ProximitySensor, GeoProximitySensor, Anchor. <br> - it broadcasts sensor events to other app instances via DIS CommentPdu, which has variable number of variable-length records. All sensor hits on a frame are queued, and when processing dis send events, it reads the queue and packs into a single CommentPdu and broadcastes. <br> - other app instances once per frame in dis_receive function parse the pdu stream, and direct all CommentPdus to the pdu2sensor function, which iterates over the CommentPdu variable records and calls the appropriate sensor functions for each sensor event. <br> -Doug <br> <br> _______________________________________________ x3d-public mailing list <a href="mailto:x3d...@we...">x3d...@we...</a>[mailto:<a href="mailto:x3d...@we...">x3d...@we...</a>][mailto:<a href="mailto:x3d...@we...">x3d...@we...</a>[mailto:<a href="mailto:x3d...@we...">x3d...@we...</a>]] <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org%5Bhttp://web3d.org/mailman/listinfo/x3d-public_web3d.org%5D_______________________________________________">http://web3d.org/mailman/listinfo/x3d-public_web3d.org[http://web3d.org/mailman/listinfo/x3d-public_web3d.org]_______________________________________________</a> FreeWRL-develop mailing list <a href="mailto:Fre...@li...">Fre...@li...</a> <a href="https://lists.sourceforge.net/lists/listinfo/freewrl-develop%5Bhttps://lists.sourceforge.net/lists/listinfo/freewrl-develop%5D">https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop]</a> <br> <br> _______________________________________________ <br> x3d-public mailing list <br> <a href="mailto:x3d...@we...">x3d...@we...</a> <br> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a> <br> </blockquote> </div> </div> </blockquote></div></body> </html> |
From: Christoph V. <chr...@gm...> - 2023-12-20 17:40:37
|
Doug, I have started with first tests of your elevator3.x3d example. Am now going to analyse the results. Here's a preliminary demo video: https://lc-soc-lc.at/owncloud/index.php/s/FQCi7ix1yUGHIUF Cloud Password for the video: HalloWelt Have a nice holiday season Christoph Gesendet: Sonntag, 17. Dezember 2023 um 16:33 Uhr Von: "Christoph Valentin via FreeWRL-develop" <fre...@li...> An: "GPU Group" <gpu...@gm...> Cc: "Christoph Valentin" <chr...@gm...>, r....@ka..., "Kevin" <kl...@ya...>, "Development for the FreeWRL X3D viewer." <fre...@li...> Betreff: Re: [FreeWRL-develop] [x3d-public] web3d MMO > Sensor sharing via DIS Doug, Thank you for the information and for the suggestions. You can follow my project at our association's home page: https://lc-soc-lc.or.at/project-003-dexper/index.html Today I entered following status: 2023-12-17: started to analyse X3D v3.3 (ISO/IEC IS 19775-1:2013) - chapter 28 (DIS)2023-12-17: started to analyse elevator example from Doug S. Have a nice holiday season, Kr, Christoph Gesendet: Sonntag, 17. Dezember 2023 um 15:39 Uhr Von: "GPU Group" <gpu...@gm...> An: "Christoph Valentin" <chr...@gm...> Cc: "Kevin" <kl...@ya...>, "Development for the FreeWRL X3D viewer." <fre...@li...>, r....@ka... Betreff: Re: Re: [x3d-public] web3d MMO > Sensor sharing via DIS Christoph,As long as using the same app for all communications, it's up to the app to choose a comment 'channel' number. I don't remember the exact terminology, but it seemed like there were plenty of channels, so an app can take one for its own purpose as long as no other app is using it in the same simulation. So it's not something the app user would need to worry about when using the same app for all instances. It's just when wanting to communicate between different apps, then app developers need to be coordinated on their use of channels. -Doug PS mor things that could be done on the topic: 1. humanoid avatars. I used cones to represent the pose of avatars 2. automated gait - automatically change standing/walking-pace/running motion of humanoid avatars based on speed of navigation - so as you navigate in your app, the other apps see your humanoid avatar walking/running fast enough to make sense for your speed 3. inverse kinematics - as you mouse over a sensor to click, an arm would rise to point in the direction of the pointer, so other users can see you clicking 4. conveyor-belt test - I did an elevator test in freewrl, but a conveyor test is harder, for example if your avatar gets in a vehicle that moves, does your avatar stay with the vehicle? I worked on something like it 15 years ago and found it a hard problem at that time and haven't tried it since On Sat, Dec 16, 2023 at 4:03 PM Christoph Valentin <chr...@gm...[mailto:chr...@gm...]> wrote:Hi Doug, May I ask a "silly question"? You write "[...]it broadcasts sensor events to other app instances via DIS CommentPdu[...]", where is this documented? I did not find anything in X3D v3.3 standard about CommentPdu. Would like to try it out during holiday season. Thanks Christoph Gesendet: Samstag, 17. Juni 2023 um 23:30 Uhr Von: "GPU Group" <gpu...@gm...[mailto:gpu...@gm...]> An: "Christoph Valentin" <chr...@gm...[mailto:chr...@gm...]> Cc: "X3D Graphics public mailing list" <x3d...@we...[mailto:x3d...@we...]>, "Kevin" <kl...@ya...[mailto:kl...@ya...]>, "Roman Onic" <rom...@ko...[mailto:rom...@ko...]> Betreff: Re: [x3d-public] web3d MMO > Sensor sharing via DIS Thanks Christoph. Hold on though -- I need to publish the current version of freewrl, could be a few weeks before I post .msi for windows. -Doug On Sat, Jun 17, 2023 at 4:27 PM Christoph Valentin <chr...@gm...[mailto:chr...@gm...][mailto:chr...@gm...[mailto:chr...@gm...]]> wrote: Doug, This sounds really interesting. I hope I will find some time to try it soon. Will let you know my comments. Kr, CP/V -- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet. Am 18.06.23, 00:12 schrieb GPU Group <gpu...@gm...[mailto:gpu...@gm...][mailto:gpu...@gm...[mailto:gpu...@gm...]]>: MMO - massively multiplayer online DIS distributed interactive simulation - a web3d component 28 CONCEPT: web3d browsers load identical scenes, and share sensor events, and each instance does its own routing diagram after sensor event is shared. https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4[https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4][https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4%5Bhttps://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/MMO_Sensor_sharing.mp4%5D] - 2 instances of freewrl with DIS activated, showing same elevator3.x3d scene https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/[https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/][https://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/%5Bhttps://freewrl.sourceforge.io/tests/28_Distributed_interactive_simulation/elevator/%5D] - in video we can see avatar of other instance as green cone - when current scene clicks elevator up button, it relays that sensor click event to other app instance, which triggers the elevator in the other scene to go up at the same time - the avatar in the other scene rides its elevator up, and sends its new avatar pose to the current scene, so appears they are riding up elevator together. - the code sensor intercept point is general enough to capture TouchSensor, GeoTouchSensor, LineSensor, PointSensor (not web3d spec), PlaneSensor, MultiTouchSensor (not web3d spec), CylinderSensor, SphereSensor, ProximitySensor, GeoProximitySensor, Anchor. - it broadcasts sensor events to other app instances via DIS CommentPdu, which has variable number of variable-length records. All sensor hits on a frame are queued, and when processing dis send events, it reads the queue and packs into a single CommentPdu and broadcastes. - other app instances once per frame in dis_receive function parse the pdu stream, and direct all CommentPdus to the pdu2sensor function, which iterates over the CommentPdu variable records and calls the appropriate sensor functions for each sensor event. -Doug _______________________________________________ x3d-public mailing list x3d...@we...[mailto:x3d...@we...][mailto:x3d...@we...[mailto:x3d...@we...]] http://web3d.org/mailman/listinfo/x3d-public_web3d.org[http://web3d.org/mailman/listinfo/x3d-public_web3d.org]_______________________________________________ FreeWRL-develop mailing list Fre...@li... https://lists.sourceforge.net/lists/listinfo/freewrl-develop[https://lists.sourceforge.net/lists/listinfo/freewrl-develop] |