- Home
- Skills
- Game Development
- Game Physics & Collision Optimization Analyst
Works with the AI Agents you already use
Game Physics & Collision Optimization Analyst
Expert analysis for game physics bottlenecks, collision spikes, and simulation stability across major engines.
$9.99
Game Physics & Collision Optimization Analyst
Example session with this skill installed
Analyze a Unity project where physics time spikes to 12ms when 50 rigid body crates are destroyed by an explosion. Using PhysX on PC. Fixed timestep is 0.02s. Solver iterations set to 6.
- Read your context and instructions
- Compiled the game physics
The 12ms spike during the crate explosion indicates a narrowphase or solver bottleneck triggered by sudden high-density contact generation and potential allocation storms during object destruction.
Physics Performance Analysis Report
| Category | Finding | Confidence | Priority |
|---|---|---|---|
| Narrowphase | Dense clusters of MeshColliders generating excessive contact pairs during explosion. | High | Critical |
| Solver | High penetration depth causing solver struggle; 6 iterations may be insufficient for stability. | Medium | High |
| Allocations | Potential OnCollisionEnter or OnTriggerEnter event storms during crate fragmentation. | Medium | Medium |
| Broadphase | Sudden influx of dynamic bodies into the spatial partition causing tree rebuild overhead. | Low | Low |
Recommended Optimization Plan
Collider Simplification: Replace Crate MeshColliders with BoxColliders. This reduces narrowphase complexity from mesh-triangle tests to simple primitive checks.
2.
Layer Collision Matrix: Ensure fragments/debris layers are set to ignore each other to prevent $O(N^2)$ collision checks within the explosion cloud.
3.
Contact Offset Tuning: Audit Contact Offset values to prevent deep penetration on the first frame of the explosion, reducing solver workload.
4.
Event Batching: Use a manager to handle explosion logic rather than individual OnCollision scripts to avoid per-object callback overhead.
Next steps
- Capture a deep profile trace specifically filtering for
Physics.ProcessingandPhysics.Simulate. - Toggle the Collision Matrix for the 'Debris' layer and measure the delta in p99 frame time.
- Verify that replacing mesh colliders with boxes does not negatively impact the visual alignment of the crates when stacked.
Connects securely to your tools. The creator never sees your data.
About this skill
Physics spikes and collision overhead frequently tank game performance, yet blind optimizations often break gameplay feel or introduce tunneling. This skill acts as a senior game physics analyst to diagnose bottlenecks and plan precise optimizations without sacrificing simulation stability.
What it does
- Analyze physics cost maps by breaking down CPU time across broadphase, narrowphase, solver integration, and query cycles.
- Identify root causes such as redundant collision checks, pathological mass ratios, or excessive mesh-to-mesh interactions.
- Rank optimization strategies based on measured evidence, implementation complexity, and risk to gameplay correctness.
- Plan validation tests to ensure performance gains do not introduce jitter, missed contacts, or multiplayer desynchronization.
How it works
- Input profiling data from Unity, Unreal, Godot, or custom engine traces along with target hardware constraints.
- Execute the diagnostic workflow to map costs across broadphase pairs, solver iterations, and repeated scene queries.
- Generate a prioritized report containing an executive diagnosis, ranked hypotheses, and a structured optimization plan.
Frameworks & tools
Supported engines include Unity (PhysX), Unreal Engine (Chaos), and Godot 3D/2D, as well as custom backends utilizing spatial hashing, BVH, or sweep-and-prune architectures.
Why this beats prompting it yourself
Generic prompts often suggest dangerous shortcuts like lowering solver iterations or increasing collision margins that ruin player feel. This skill enforces a "measure before changing" methodology, ensuring every recommendation includes specific validation steps and a rollback path.
Use cases
- Fixing frame spikes caused by dense object clusters or high-frequency raycast polling in combat scenes.
- Optimizing mobile performance by replacing expensive mesh colliders with primitive proxies or convex decompositions.
- Improving simulation stability for complex joint chains or rigid body stacks that currently jitter or explode.
- Audit collision matrices to remove redundant interaction checks between layers that never need to collide.
Known limitations
Requires specific engine versions and profiler counters to provide high-confidence recommendations. It cannot automatically apply code or asset changes to the project files.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.
Requires engine version and profiler data for high confidence. Does not directly modify project files or assets. Cannot fix issues caused by proprietary hardware-level driver bugs.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 7 days ago
Permissions
No special permissions declared or detected