Basically doing a grave disservice to developers. The reason is that it is a bandaid to hide a core problem under the rug and it lets the developer forget about needing to fix things up later. As result, when we refactored the loader in 2020.1 (iirc) it was at least disabled by default. The hope is that in some time (1 or 2 yrs) WebGPU is fully developed and embraced by all browsers.Ĭlick to expand.I have been very vocal in our team that we should delete the whole `Decompression Fallback` feature from Unity. They never continued development because they are focussing on WebGPU instead)įor Android WebGL 2.0 can be used on Chrome / Firefox. But it is not the most performant either.įor Apple devices, Safari is only supporting WebGL 1.0 (unless experimental WebGL 2.0 is enabled. WebGL Mobile is no longer blocked by an unsupported message. Old custom templates will be broken as far as I know. So yeah quite some changes have been made to 2020.1 WebGL, including the Template it uses. If you're running old configurations you're going to require a new configuration. So mimetypes have to be changed accordingly. Which brings me to my next point, they changed the extension a little bit. This is due to the fact that when filenames are converted to hashes they lose their. Even with the new web.config or htaccess file.
There is one bug where if you use "Filenames as hashes" together with a compressed build (gzip or brotli) then decompression will fail.
0 kommentar(er)
