- The Android Game Developer's Handbook
- Table of Contents
- The Android Game Developer's Handbook
- Credits
- About the Author
- About the Reviewer
- www.PacktPub.com
- Preface
- 1. Android Game Development
- 2. Introduction to Different Android Platforms
- Exploring Android mobiles
- Exploring Android tablets
- Exploring Android televisions and STBs
- Exploring Android consoles
- Exploring Android watches
- Development insights on Android mobiles
- Development insights on Android tablets
- Development insights on Android TV and STBs
- Development insights on Android consoles
- Development insights on Android watches
- Platform-specific specialties
- Summary
- 3. Different Android Development Tools
- 4. Android Development Style and Standards in the Industry
- 5. Understanding the Game Loop and Frame Rate
- 6. Improving Performance of 2D/3D Games
- 2D game development constraints
- 3D game development constraints
- The rendering pipeline in Android
- Optimizing 2D assets
- Optimizing 3D assets
- Common game development mistakes
- 2D/3D performance comparison
- Summary
- 7. Working with Shaders
- 8. Performance and Memory Optimization
- Fields of optimization in Android games
- Resource optimization
- Design optimization
- Memory optimization
- Don't create unnecessary objects during runtime
- Use primitive data types as far as possible
- Don't use unmanaged static objects
- Don't create unnecessary classes or interfaces
- Use the minimum possible abstraction
- Keep a check on services
- Optimize bitmaps
- Release unnecessary memory blocks
- Use external tools such as zipalign and ProGuard
- Performance optimization
- Relationship between performance and memory management
- Memory management in Android
- Processing segments in Android
- Different memory segments
- Importance of memory optimization
- Optimizing overall performance
- Increasing the frame rate
- Importance of performance optimization
- Common optimization mistakes
- Best optimization practices
- Summary
- Fields of optimization in Android games
- 9. Testing Code and Debugging
- 10. Scope for Android in VR Games
- Understanding VR
- VR in Android games
- Future of Android in VR
- Game development for VR devices
- Introduction to the Cardboard SDK
- Basic guide to develop games with the Cardboard SDK
- VR game development through Google VR
- Android VR development best practices
- Challenges with the Android VR game market
- Expanded VR gaming concepts and development
- Summary
- 11. Android Game Development Using C++ and OpenGL
- 12. Polishing Android Games
- 13. Third-Party Integration, Monetization, and Services
- Google Play Services
- Multiplayer implementation
- Analytic tools
- Android in-app purchase integration
- Android in-game advertisements
- Monetization techniques
- Planning game revenue
- User acquisition techniques
- User retention techniques
- Featuring Android games
- Publishing Android games
- Summary
- Index
A 3D art asset has two parts to be optimized. A 2D texture part is to be optimized in the same 2D optimization style. The only thing the developer needs to consider is after optimization, the shader should have the same effect on the structure.
The rest of the 3D asset optimization entirely depends on the number of vertices and the model polygon.
It is very obvious that a large number of polygons used to create a mesh can create more details. However, we all know that Android is a mobile OS, and it always has hardware limitations.
The developer should count the number of polygons used in the mesh and the total number of polygons rendered on the screen in a single draw cycle. There is always a limitation depending on the hardware configuration.
So, limiting the polygon and vertex count per mesh is always an advantage in order to achieve a certain frame rate or performance.
Models are created with more than one mesh. Using a separate mesh in the final model always results in heavy processing. This is a major effort for the game artist. Multiple overlaps can occur if multiple meshes are used. This increases vertex processing.
Rigging is another essential part of finalizing the model. A good rigger defines the skeleton with the minimum possible joints for minimum processing.
-
No Comment