You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to create a multiplayer js extension to A-Frame.js. I have achieved working version with a central server running socket.io to distribute client metadata. I am cleaning up the repo for that, it will be up soon (lots of profanity). However, centralized server isn't exciting and it is fragile. I want to use a p2p mesh solution so that only a signaling server need be maintained so I took a look at the IPFS PubSub demo ( and I don't have to pay for a big grumpy server running socket.io ). I am fairly fresh to the available technologies for this.
My requirements:
Room/Channel based subscription
Broadcast JSON every 100ms
Abstracted fallback protocols
Running multiple clients on the same machine I found that only 5% the exchange of data between clients seemed to work and even then it was extremely high CPU load. I am trying to send metadata updates (if necessary) every 100ms. This interval should be fine for clients locally I assume.
I think the problem is running clients on the same machine does not play well with PubSub, libp2p and creating a pipe within same IP?
The project should run out of the box. A-Frame itself is super inefficient in any case, but it is fine to run at roughly 60fps on my macbook air 2013
The text was updated successfully, but these errors were encountered:
https://github.com/mikezucc/metaverse-ipfs
I am trying to create a multiplayer js extension to A-Frame.js. I have achieved working version with a central server running socket.io to distribute client metadata. I am cleaning up the repo for that, it will be up soon (lots of profanity). However, centralized server isn't exciting and it is fragile. I want to use a p2p mesh solution so that only a signaling server need be maintained so I took a look at the IPFS PubSub demo ( and I don't have to pay for a big grumpy server running socket.io ). I am fairly fresh to the available technologies for this.
My requirements:
Running multiple clients on the same machine I found that only 5% the exchange of data between clients seemed to work and even then it was extremely high CPU load. I am trying to send metadata updates (if necessary) every 100ms. This interval should be fine for clients locally I assume.
I think the problem is running clients on the same machine does not play well with PubSub, libp2p and creating a pipe within same IP?
The project should run out of the box. A-Frame itself is super inefficient in any case, but it is fine to run at roughly 60fps on my macbook air 2013
The text was updated successfully, but these errors were encountered: