Telegram-канал r_unity3d - r/Unity3D: Неотсортированное

r/Unity3D

15 апреля 2025 21:02

Turns out stuffing 1 GB of assets into our small 2D game wasn’t the best idea (how we fixed it) 😅

Hi, I'm Vladimir from Possum Riot. We recently released our first game on Steam — cozy puzzle Eyes That Hypnotise.

Eyes That Hypnotise gameplay

Since it's our first game, turned out we had quite a lot of performance and optimisation issues. So I wanted to share what I did to fix that. Maybe it’ll be useful for someone else making a 2D game in Unity.

# TL;DR:

🔧 Reduced build size from 1.15 GB → 175 MB

Downscaled sprites, used atlases, POT & crunch compression and deleted repeated animation frames
Converted audio to OGG + Vorbis with reduced compression ratio
Removed unused assets

🚀 Fixed FPS spikes (esp. on Steam Deck):

Replaced DOTween with PrimeTween
Switched coroutines/Tasks to [UniTask](https://github.com/Cysharp/UniTask)

⚡Result: Smaller, smoother build with no major visual loss

# Build size

Reduced from 1.15 GB to 175 MB.

The major part of the build (\~80%) was due to enormously large sprites we used, incorrect settings in the Unity importer, and just a lack of knowledge.

Visual assets optimisations

Deleted repeated frames in animations. Our animals’ “action” animations had the same first and last frames as their “idle” animation. Also 2nd and 4th frames were identical. So I deleted duplicated frames and just reused sprites for the “action” animation, and from 7 frames for each animal, it became only 4 frames.

Frames quantity for each animal $before and after$

Reduced sprite image resolution at least twice (in some cases by 4 times).
Changed sprite image resolution so it’s at least divisible by 4 (better for texture compression algos to work). Where possible did even better - made it a power of two (POT) and used crunch compression.
For related images (like UI and Chapter N animals), I used Unity sprite atlases that packed the images nicely into one POT texture and applied crunch compression with decent quality settings.
Used mipmaps for some sprites (like animals). Actually, that increases texture size (obviously), but not by much, and it helped fix the pixelated, janky look of images on 1080p and Steam Deck displays (as we originally targeted Mac Retina displays). Also, I didn’t bother with dynamic asset loading, although probably I should. I just still don’t have much experience with Unity, but I'll get there eventually, I think. So if you have any advice - please drop a comment 🙂

Those changes already reduced our build size from 1.15 GB to \~235 MB and (what’s most important) didn’t impact visual quality too much.

Further optimisation of build size was for the audio.

Audio optimisations

We have around 50 music tracks in our game (each 2–3 min long) and more than 100 short FX sounds (each animal has on average 4–5 unique sounds). That’s a lot of audio for a small game.

What I did with the audio to reduce build size:

Converted all audio in the game from MP3 to OGG format (better size/quality ratio).
Used the Vorbis compression format with about 60–70% compression ratio in the Unity importer.

Other small changes

There were some minor tweaks I did as well, like:

Deleted unused packages from the project.
Enabled code and shader stripping in Project Settings.

After all of that, we had a 175 MB Windows build size for the full game and 117 MB for the demo. So for now, the major part of the build size is mostly Unity engine stuff that we cannot get rid of. If we had done it in some lighter engine, like Phaser for example, the build size would be around 70–80 MB, I think (just because of the hand-drawn animations and a