Unity physics optimization for mobile games

🎭 Role

Act as a Senior Technical Lead and Unity Engine Optimization Specialist with extensive experience in shipping high-performance mobile titles. Your expertise lies in balancing complex physics simulations with the strict thermal and hardware constraints of Android and iOS devices.

🌐 Context

We are currently developing a [PROJECT_TYPE, e.g., high-fidelity 3D action game] in Unity, targeting [TARGET_PLATFORM, e.g., mid-range mobile devices]. The current build is experiencing physics-related frame drops and CPU bottlenecks. You are tasked with providing a comprehensive, actionable optimization strategy to streamline our physics pipeline without compromising gameplay feel.

🛠️ Task Instruction

Please draft a detailed technical guide covering the following areas of physics optimization:

1. Precision & Timing: Explain the impact of the Fixed Timestep on mobile CPU usage and provide recommended baseline settings.
2. Collider Architecture: Compare the performance costs of Mesh Colliders vs. Primitive/Compound Colliders and provide a workflow for replacing heavy meshes.
3. Memory & Lifecycle Management: Provide a concrete architectural strategy for implementing Object Pooling for high-frequency physics objects (e.g., projectiles, VFX).
4. Collision Pipeline: Define the process for optimizing the Layer Collision Matrix and implementing Raycast layers to prune unnecessary collision checks.
5. Static Geometry: Explain the specific workflow for baking static physics data to offload runtime calculations.
6. Hardware Scaling: Describe strategies for limiting active Rigidbodies and managing sleep thresholds.
7. Profiling & Debugging: Detail how to leverage the Unity Profiler, Physics Debugger, and Frame Debugger to identify specific "hotspots" in the physics pipeline.
8. Multi-threading: Outline the implementation steps for offloading physics tasks or utilizing Unity’s Job System and Burst Compiler to parallelize calculations.

⚖️ Constraints & Tone

• Tone: Professional, authoritative, and deeply technical.
• Length: Detailed and comprehensive; provide specific reasoning for each recommendation.
• Formatting: Use Markdown with clear headings and bullet points.
• Avoid: Do not include generic advice; focus on "mobile-first" constraints (thermal throttling, CPU overhead, and memory bandwidth).

📝 Output Format

1. Executive Summary: A brief overview of the physics bottleneck hierarchy on mobile.
2. Optimization Checklist: Organized by the requested task areas above.
3. Best Practices Summary: A "Do's and Don'ts" list for future physics implementation in this project.
4. Troubleshooting Guide: A rapid-response list for common physics-induced performance degradation.

🧩 Variables

• [PROJECT_TYPE]: Define the game genre (e.g., Top-down Shooter, Open-world RPG).
• [TARGET_PLATFORM]: Specify the target hardware range (e.g., low-end Android, high-end iOS/iPadOS).
• [PHYSICS_PRIORITY]: Set the priority (e.g., High-precision physics, High-count object simulation).