WebGL Roadmap

FireFox is updated to 52 with supporting WebAssembly: https://www.mozilla.org/en-US/firefox/52.0/releasenotes/

 

So it's available on Firefox and Chrome 57, so we are only waiting for it to drop on Edge and Unity 5.6?

 

When wasm is finally official is the idea that where available it will be used but if an older browsers is still active UnityLoader will fall back to non wasm, or do we need to handle that ourselves? I'm assuming UnityLoader.js does all that but just checking.

 

So we can use it in production safely or we must wait after the official release?

 

And that's what I came to this thread to check. How often is the post you want on the last page?

The "Network" inspector confirms successful delivery in FF 52.0.2 from here.
Gasp. A pluginless platform for the web. Like on the horizon?
Thanks for including the support in 5.6. much appreciated.

No bugs so far

 

Is there a way to monitor how the browser vendors are getting on with this ?

 

Chrome Version 57.0.2987.133 seems to support it on my side

 

Hmm, I can see it support this: WEBGL_compressed_texture_s3tc
But not WEBGL_compressed_texture_s3tc_sgrb which I assume is different

 

My bad

 

Looks like it's available in Chrome Canary, it might be a while until it reaches stable channels.

Chrome Version 59.0.3067.0

 

WOO!!!

 

Hi,

I am checking standard shader results with WebGL and WebGL 2.0 and I have a question:

are Standard shader DETAIL MAPS (albedo and normal) visualized by WebGL and WebGL 2.0?

 

Chrome 58 has been released and web assembly is now enabled by default so I made a build to try it and Im getting errors, I know its experimental and there might be bugs.

http://infestedland.s3-website-us-east-1.amazonaws.com/test/

 

Chrome was the first to remove the unity web player plugin and now, 2 year after that, we still can't have something "stable" for our webgl game.... unbelievable....

Well, for you case, i have try an another game build with the web assembly support and it have also the red message :

but his game run fine. For you, the error happen when you try to join the room infestedland, so you must have an error somewhere in your code. Try to debug your game to see from where it happen.

 

Hey roka, its definitely something with web assembly since the regular webgl version works fine, I also have seen other unity demos with wasm working tho.

This is the same game without WASM and works fine: http://infestedland.s3-website-us-east-1.amazonaws.com/ it has been working fine since a while.

 

Hum.... then https://forum.unity3d.com/threads/w...erflow-integer-result-unrepresentable.461484/

They said "This is a known issue. You can follow the resolution process here"
This bug has been submited a month ago ^^
Funny joke ^^

Maybe we will be able to get something stable in 2025 when all web browser vendors will stop to use webgl for something else .... it's unbelievable ...

 

Well Im not complaining, webgl is very stable for me right now, Im just reporting this for Web Assembly.

 

Please, @Marco-Trivellato can you give me an hand?

 

Yeah, but this bug has been submitted the March 15 and it's still not fixed. Now i can finally build my game with the version 5.6 but i got the same error ^^ Just have to wait.

 

Done: https://forum.unity3d.com/threads/standard-shader-detail-maps-for-webgl-and-webgl-20.468127/
Thanks!

 

In the original thread you said this:

A very common question we get is when we plan to support mobiles with Unity WebGL. While we currently don’t do anything in order to prevent running content on mobiles (other than show a warning), in general, success rates are rather low (some high-end Android mobiles yield decent results, but most everyday end-user devices - not so much.). We don’t expect to see much change here before the above points on memory and performance see some significant improvements and performance of mobiles will have improved in general, so we cannot give any ETA on mobile support. We do believe that it will inevitably happen as technology progresses in the future, though.​

What's Unity's current view on mobile WebGL support?

 

Any idea on when it's likely to move from experimental to official, it sounds like even though things are still improving it does currently work to some degree. I know it's on by default now in Chrome and Firefox.
Will that be part of the 5.6 cycle at least?

 

Since Chrome 57 lauched I have try develop my app with webgl test with some android and ios device.
Success rate could be considered good on android. But it seriously too long compile time. I use progressbar to know that load time is just less than 10 second but then it freeze for more than 5 minutes in mobile. I'm sure that whole JIT compiler take on unity's webassembly

The worst is. using assetbundle reduce overall time consume. But then in ios device it will crash after finish loading assetbundle. I don't know why yet

Still it rather promising when I use on android. Performance is really usable.

But I think the most problem is unity has ridiculous webgl build process

From C# to C++ to emscripten to webgl. All those step decrease performance and increase garbage library. It seriously took 10 to 30 minutes just to build and run a small project. 5 minutes to load on device. Just changing 1 line of logic is waste my life like nightmare

And seriously, the plugin system for webgl (jslib) is worse than junk. It cannot even take dynamic callback lambda

 

@Marco-Trivellato - has there been any movement on SPLIT_MEMORY support? (esp. in WASM it seems like that's a core part of the spec, but as best we can see Unity isn't using it yet); for our use, it's really a critical feature, and it'd be great to have out of the box.

EDIT: SPLIT_MEMORY or memory growth. Seems like both aren't enabled.

 

From my experience experiment. WebAssembly almost always faster than normal webgl build. Even take the compile time to account. Performance for webgl js build cannot be acceptable in my machine. But webassembly is somehow good

 

with web assembly my game runs with 30 fps on 1Ghz dual core, otherwise it drops to 5fps hehe
Also found a statistic about support webgl 2.0, which is near 50% on desktops source : http://webglstats.com/
anyone knows how about the roadmap of webgl 2.0?

 

Hey @Marco-Trivellato
any chance the web GL road map can get updated. Seems majorly out of date.
Also I noticed the other day that Microsoft Edge works crazy good now. Great performance, it even caches the game. The only reason why its unusable is the mouse doesn't work? when the mouse goes into the webGL container box it disappears. Certainly that should be fixable?

 

The memory profiler is still a bit touch and go for us with WebGL - still getting lots of issues where it's impossible to get a debug dump out of it.

We're chasing a memory leak at the moment, which we suspect is related to UnityWebRequest's GetTextures function not releasing memory (started in 5.6, wasn't present in 5.5); and having a reliable memory profiler would be a big help.

The other big request I'd like to put in is "support" for SPLIT_MEMORY (or an equivalent - it seems WebAssembly should support this particular functionality well) out of the box - even if Chrome is a bit funky with it.

 

Is there any chance of having webgl working on mobile browsers?

 

There's a good chance I'm talking nonsense here, but after seeing that Unity developed an extension to WebGL to support linear rendering.. Is there a possibility of providing an extension to support geometry shaders, or is this something that we'll have to wait for Khronos to introduce in a future WebGL version?

 

+1

 

@Marco-Trivellato
Ahh I guess i was talking about the roadmap on the first post of this entire thread lmao. My bad.

 

Are there any plans for theards? In the upcoming versions

 

From the first post:

--Eric

 

It will be cool, if we can reduce time on starting WebGL loading. All resources has been loaded from bundles, but what about the code?
All code(50k+) is in one file .asm.code.unityweb and when it's stat repacking - it take a long time and crash on week laptop. How can I fix it?