I am currently developing a multiplayer game using Badumna. I am using the latest version of Unity3d Pro.
As you know Badumna has problems with the WebPlayer (related to UDP socket support). I have read that this is work in progress and this issue will be solved.
However some time has already passed and I would like to ask you when do you expect this to be solved as running the game in a web browser is a requirement for our game.
It is a webplayer issue. and I did ask in badumna foruns, they told me it is a webplayer issue and that I should ask UT.
Also, this issue was discussed in this forum too, but some months ago and I just want to know what is the status of this.
I don´t want to be rude but, next time, please don´t try to kill a thread just by assumption. I really have the Unity Community in high consideration and I am really in need of this information.
Its a problem of badumna with the webplayer, not the webplayer with itself, as lidgren, smartfoxserver, Photon, ElectroServer, uLink and pure udp sockets wouldn’t work either if it was a unity webplayer problem. All you have to do is to comply to the sandbox.
So I would expect them to be at fault, as badumna was released prior the security sandbox and I’m not sure if it really complies to its requirements (the webplayer security policy and the available namespaces changed fundamentally between u2 (no security aside of basic no-system access) and u3 (more or less modern plugin security policy compliance)
I wasn´t trying to imply that it is a unity webplayer fault. But I have read there were conversations between Scalify and UT in order to solve this issue, and just yesterday I was told by Scalify that I should ask UT.
So I am kind of being “ping-ponged” around and I really need to know this… what can I conclude then?
Hi Edgar and others,
Its not so much a fault of UT or Badumna. You need to understand why is it an issue. As you know Badumna is based on a decentralised protocol, hence it relies on using UDP (sending and receiving) as part of its core offering. A security sandbox was introduced in the 3.x webplayer which prohibits UDP (especially listening). This means that it is impossible to connect webplayer nodes to each other in 3.x.
This means that not only Badumna but any other service that relies on UDP listening (such as p2p audio streaming or webcam support) would not work with this version of the webplayer,
Having said that, Badumna has a HTTP tunnel mode which would work in this setting but it forces Badumna to function in client-server mode and you are not getting all the benefits of scalability etc that Badumna offers.
In terms of making webplayer support UDP listening, we (Scalify) have had discussions with UT and a solution has been agreed that allows p2p communication while maintaining the security requirements of the webplayer. Its a matter of getting that into one of the future updates.
We will see if UT is going to break their security policy and risk their serious business usage reputation just for Badumna.
After the US Army Certification, I would definitely not hold my breath for UT to offer you a UDP Socket server and even less UDP Broadcast in webplayer and I personally would favor it not to happen either as it would make it harder again to get Unity through as an engine for gov funded projects that involve webplayers.
There is a higher chance of ending on the point where Badumna will just add the relevant points to the documentation mentioning that P2P is not going to work on webplayers due to current agreed web security standards.
Hi Dreamora,
If you read my post carefully, you will note that I mentioned that the solution agreed does not break the security requirements of the webplayer. I agree with you that it will be crazy to break the security requirements of the webplayer.