Optimizing your Game for Low-end Devices
0 likes577 views
The document outlines essential guidelines for optimizing games for low-end devices, focusing on various aspects like graphics, physics, and sound. Key strategies include using image compression, reducing object count, and optimizing loading processes to improve performance. Additionally, it highlights the importance of profiling tools to monitor resource usage effectively.
Optimizing your Game for Low-end Devices
- 2. Optimizing your game for low-end devices Miguel Tomás – Bica Studios Catarina Macedo - Microsoft
- 3. … Or as we like to call it: “ The 13 awesomesauce rules to get your game running on any crappy phone ”
- 5. GAMES MADE WITH ENERGY
- 6. Platforms:
- 7. Lumia 520 90MB iPhone 4 160MB So Many…. 100MB
- 8. UI becomes Faster, Better, Stronger This pleases ar+sts
- 9. • Improve other mechanics • Opens doors for new ideas This pleases game designers
- 11. Be social Feel the art and work with the artists
- 12. Important! Game size doesn’t matter... BUT it is important
- 13. How?
- 14. SUCKS for 2D Games 1. Image Compression Uncompressed Compressed
- 15. It’s a paradise for 3D Games 1. Image Compression
- 16. Use what is known to users: Game Center Google Play Services 2. Game Services
- 17. Try not to use them • Antialiasing • Bloom • Blur • Cel-Shading 3. Post Effects
- 18. Forget current Unity GUI The new one is AWESOME! 4. GUI
- 19. Have at least 2 Cameras • UI Camera • Game Camera 5. Cameras
- 20. 6. Particles You can have them
- 21. 6. Particles BUT be careful
- 22. Keep your object count small Use 2D physics processing if your game is 2D Avoid Mesh Colliders 7. Physics
- 23. • Keep vertex count small • Avoid complex shaders • Use shadow projector to the floor • Use lightmaping textures • Compress textures • Batch objects sharing the same textures • Keep in memory only the playable zone 7. 3D Optimization
- 24. • Keep atlas count small • Aim your atlas to 1024x1024 (4MB) • Optimize your atlas • Batch objects sharing textures • Load what you need when you need it 8. 2D Optimization
- 25. Power to process an amount of objects at one time 9. Batching
- 26. Depends on the sound type • Music – Stream from disc (MP3) • Short Clips – Load into memory (WAV) • Longer Clips – Compressed in memory(MP3) 10. Sound Optimization
- 27. Only have what you need on scene 11. Loading
- 28. Load assets when you need new stuff 11. Loading
- 29. 11. Loading Instantiate when you need duplicates
- 30. 11. Loading Careful when you use coroutines • Don’t Resources.Load in a coroutine • Careful with looping coroutines
- 31. DON’T FORGET • Unload what you don’t need anymore • Garbage Collect periodically 11. Loading
- 32. In the beginning 12. Font Optimization
- 33. In the end it’s a mess • Chinese • Japanese • Cyrillic • Arabic 12. Font Optimization
- 34. Create an atlas font for each alphabet you are going to use Only loads the atlas font you are currently using When you change language, load the new font and unload the old one 12. Font Optimization
- 35. Use profiling tools, watch RAM very closely. Unity balances GPU and CPU == YAY! 13. Profiling Tools
- 36. RAM is HIGH –> optimize assets CPU is HIGH –> reduce objects in scene, Particles, Physics Quick Notes
- 37. GPU is HIGH –> optimize draw calls and simplify shaders; if it’s 3D reduce vertex count Quick Notes