[x3d-public] Metaverse > Multiuser web3d-browser > how sync state?

[GPU Group]

https://freewrl.sourceforge.io/tests/23_Navigation/collision/elevator/
- elevator.x3d test scene
- press a button in the elevator to go up
freewrl - OK if toolbar collision button is toggled on
view3dscene OK
Instant Player OK
Octaga FAILS
H3D FAILS


On Sun, Jun 4, 2023 at 8:34 AM GPU Group <gpugroup at gmail.com> wrote:

> Requirements for Mutli-Player system:
> 1. every player should be able to open / close a door / operate touch
> sensors
> 2. other avatars, and 1st person arms, rendered
> 3. option: survive elevator test - other and 1st person avatars should
> ride up on animated elevator or ride cart, not fall through floor
> (re-parenting?)
> 4. ability to communicate 2-way > a function of range a) vocally, b)
> writing/chat
>
>
> On Sat, Jun 3, 2023 at 8:03 AM GPU Group <gpugroup at gmail.com> wrote:
>
>> Assuming there's some method to transmit efficiently, how to keep
>> non-avatar states synchronized when there are timeSensors, particlePhysics,
>> touch and dragSensors, scripts etc - a lot of places where states can
>> change?
>> Does anyone have their web3d browser working as multi-user?
>> Is/are there a/some convenient choke-point/s to catch and distribute
>> state changes?
>> Thanks,
>> Doug
>> Avatar state changes seem more straightforward, with 1 avatar per
>> other-user joined (and arms for 1st person avatar), easier to keep track of
>> quantity.
>> DIS component is more intrusive / works on specific scene content / not
>> general, (but has detailed peer2peer connectivity design).
>> Web3d browsers have been traditionally designed around single user. How
>> hard is it to change them to multi-user?
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230604/db66a248/attachment.html>