Nakama 2.x is no longer supported in WebGL (Potentially because of System.Threading in Nakama Dotnet) about nakama-unity HOT 13 CLOSED

Thanks @5un. This is fixed and will be part of the next client SDK.

from nakama-unity.

Hi @5un. You’re right we don’t have compatibility with WebGL exports in the client right now. It’s not too difficult to do but I’m curious why you need it?

It’s difficult for us to gauge how many studios make use of WebGL and Unity given the history of serious performance problems with it.

from nakama-unity.

We are seriously considering WebGL for distribution purposes, and yes, performance in Unity WebGL builds is such a headache. Thanks so much for the clarification!

from nakama-unity.

@5un Fair enough 😄 If you're interested to contribute WebGL support into the client have a look at the previous version for how we did it:

https://github.com/heroiclabs/nakama-unity/blob/6e70cd2d2681ae6535d3d1d7eaf2a6ccca758ff1/Nakama/NTransportJavascript.jslib

from nakama-unity.

@novabyte Thanks for pointing me to the transport class! I think I might take a stab at building WebGL support.

However, I was a bit confused when you mentioned that it was not too difficult to do. Do you mean patching nakama-dotnet to support WebGL builds or making the 0.x/1.x Unity clients to support 2.x protocol? I thought there's already a WebSocket transport in nakama-dotnet. Would be great if you could point out the easiest way to go about this. Thanks a lot!

from nakama-unity.

Hi. We are also interested in supporting Nakama 2 Webgl. My error - https://c2n.me/3Xrtf6m.png

from nakama-unity.

We also have the problem on our side. And if we look quickly at the code of the client, the client is not close from being compatible with WebGL Unity builds. Also, the asm.code.unityweb generated grows by more than 2MB when including the client + the .Net 4.x switch (about 1MB each), which really hurts when trying to limit the size of the app.

I think it should be documented that WebGL is not supported.

from nakama-unity.

@Moriel12 I have some ideas on how we can introduce support for WebGL within the client but we've had some trouble to justify the work because most games launch on mobile, desktop, or console with Unity and any that target the web really use a different game engine usually something JavaScript-based. Why did you choose Unity for a browser project?

from nakama-unity.

we release games for mobile platforms and social networks. we can not rewrite the project under javascript.

from nakama-unity.

@novabyte We chose Unity because we launch on mobile and browser.

from nakama-unity.

@novabyte +1 for this request. We also intend to run our game on web along with mobile.

from nakama-unity.

Can you also update the Jolly Roger Unity demo to work in WebGL? Thanks

from nakama-unity.

@logixworx Sure. Would you open the issue on the demo project repo?

from nakama-unity.