Rarebyte - How We Use Unity and Optimize Our Games
•
2 likes•1,185 views
Rainer Angermann is the co-founder of Rarebyte, a game development studio based in Graz and Vienna that has developed over 25 titles since 2006. Rarebyte focuses on agile development with low overhead costs and works on games, mobile apps, and public installations. In the past Rarebyte attempted to develop two large multiplayer online games called Greedy Fly and ParadiGm but these projects were never released. Rarebyte's first successful release was the 2006 game Waterstorm, developed using their own game engine and editor. Since then, Rarebyte has developed games using the Unity game engine and provides libraries and tools to help with common game development tasks like asset loading and localization.
Recommended
Recommended
More Related Content
Similar to Rarebyte - How We Use Unity and Optimize Our Games
Similar to Rarebyte - How We Use Unity and Optimize Our Games (20)
Recently uploaded
Recently uploaded (20)
Rarebyte - How We Use Unity and Optimize Our Games
- 3. • Games • Mobile apps • Public installations • Headquarters: Graz, Vienna • 25+ titles since 2006 • Agile, low overhead • Work for hire • Game porting • Game development from scratch RAREBYTE
- 4. • Rarebyte as unincorporated association since 1999 • ParadiGm – FPS, own engine, own editor, never released THE BEGINNING
- 5. GREEDY FLY • TPS MMO, own engine, own editor, never released
- 6. THINK BIG? • Reality-check your ideas • Manage your available resources • Do not start an MMO… ever…
- 7. • 2005 – Waterstorm development started WATERSTORM
- 8. • 2006 – Rarebyte company • 2008 – Waterstorm release WATERSTORM
- 10. Game Development in Unity
- 11. UNITY – WHY USE IT? • Focus on making games • Affordable • Community • Re-use code and assets • All major platforms
- 12. „Small“ Projects: • Setup scene in Unity • Write some code • Test in Unity editor • One target platform „Build and Run“ and you are done! BUILD PROCESS
- 13. • Build/device settings • Signing identity • Provisioning profiles iOS BUILDS Unity Xcode Device
- 14. BUILD SYSTEM • Unity (commandline) • Proprietary build configurator
- 15. • Game State System • UI Panel System • Webservices • Localization • Asset Bundle Loading • Logger • On-Screen Console RAREBYTE LIBRARIES
- 16. Performance Tips
- 17. PERFORMANCE OPTIMIZATION • Graphics/Shaders/Lighting • Assets/Textures/Meshes/Import Settings • Physics • Audio • Platform-specifics • Scripting/Game Code
- 18. • Gendarme • Unity rules STATIC CODE ANALYSIS https://github.com/fderudder/unity-gendarme
- 19. • Cache your components! • Avoid GetComponent() calls in Update() or FixedUpdate() CODING TIPS
- 20. • Avoid empty MonoBehaviour methods CODING TIPS
- 21. CODING TIPS • Use Coroutines • Avoid GameObject.Find (), GameObject.FindByTag() • Don‘t use SendMessage() (100x slower!)
- 22. PROFILER
- 23. PROFILER
- 24. POOLING • Expensive Instantiate() calls • Use a pool for game objects that need to be instantiated/killed frequently • https://unity3d.com/learn/tutorials/modules/beginner/live-training- archive/object-pooling
- 25. ADVANCED OPTIMIZATION • C# Memory and performance tips for Unity: http://www.somasim.com/blog/2015/04/csharp-memory-and- performance-tips-for-unity/ • for-each vs. for etc. • GC
- 26. GENERAL ADVICE • Code style/readability (format your code!) • Use English for all names etc. • Do not be afraid of refactoring/renaming • Use a portrait resolution if your game is portrait • MonoBehaviour/inspector: Use private members with [SerializeField] • Unity Console (errors/warnings)