Unity-optimization issues (1)

Recently, a small project requires that the package size cannot exceed 30 mb.

I did a small experiment in the evening, and the method was indeed very good. However, a lot of things I didn't understand are clear now. I'm a newbie! I hope this article will help you. Thank you!

Experiment results:

Experiment results:

1. There is only one naked cube in the scenario, which is released as PC: 10.7 MB

2. As shown in the preceding figure, Android: 7.8 MB (7880kb)

3. Zoom in the cube in 2 multiple times: 7.8 MB

4. Remove the Cube component (transform only): 7.8 MB

5. Remove the cube. In this scenario, only camera: 7.8 MB is used.

6.11 cubes: 7881kb

7. Different cube colors: 7881kb

8:. Empty 2D scenario: 7.8 MB

9. A female image is made of material on the cube, and the image import settings: 1024, compressed -- 8066kb

10. Image import settings: 1024, 16bit -- 8169kb

11. size unchanged, truecolor -- 8373kb

12. Size: 256, truecolor -- 8103kb

13. Size: 256, compressed -- 8019kb

I don't know. I was shocked!

It seems that you should be cautious when using resources in the future.