Light Baking and project size on WebGL

I have to do light baking to get good performance because I have a huge map, but my problem is that I am building a game for WebGL And the Light Baking makes my project bigger by another 80MB.
Does anyone have any ideas? How can you shrink the size and still remain with reasonable quality.
8676540--1169463--upload_2022-12-20_18-15-38.png

1 Like

Check the Lighting tab. Primarily try to reduce the lightmap resolution / texture size.

A better option may be to bake the lighting of individual static objects into their textures. This only works with static lighting and static objects (ie don’t move or rotate).

But generally, don’t expect WebGL to get anywhere near mobile graphics quality. Maybe you’re aware but I keep mentioning that because so many devs have false expectations as to what’s realistically possible with WebGL. It’s qualitatively a time-warp back to the 2010-ish era of mobile graphics.

1 Like

Thanks!!!
waiting for WEBGPU :slight_smile:

1 Like

That made me think of “Waiting for Godot” … :smile:

Unity start to work on it.

1 Like

Haha, that was a good one! :smile:

1 Like

Anyhow, the problem with WebGPU or any Web standard is that it usually takes 3+ years for a standard from “first draft” to “v1.0” and while browser developers have been trying to follow or even lead these developments, supporting them to some degree even in draft stages in their browsers, these features usually either remain disabled by default or are severely lacking and in any case show huge differences in implementation maturity, completeness, stability and performance between browsers and across platforms.

Case in point: Safari on iOS finally started supporting WebGL 2.0 somewhere between 1-2 years ago, whereas the WebGL 2.0 standard was released almost 6 years ago.

1 Like