- Home
- Skills
- Game Development
- unreal performance surgeon
Works with the AI Agents you already use
unreal performance surgeon
Diagnostic tool for Unreal Engine 5 that identifies thread bottlenecks and proposes surgical performance optimizations.
$5.99
unreal performance surgeon
Example session with this skill installed
My game is running at 45fps on a 3060 Ti. stat unit shows GPU at 22ms and Game at 12ms. How do I fix the GPU bottleneck in the Thornfield night map?
- Read your context and instructions
- Compiled the unreal performance surgeon
I have analyzed the stat unit data. Your project is GPU-bound at 22ms per frame, significantly exceeding the 16.6ms target for 60fps.
Performance: Thornfield Night (2024-05-20)
Verdict
The GPU is the primary bottleneck, specifically driven by Shadow Depths and Lumen reflections. The Game thread has sufficient overhead.
Capture
- Hardware: RTX 3060 Ti
- Settings: High Scalability, 1080p, Screen Percentage 100%
- Commands:
stat unit,ProfileGPU,stat lightrendering
Findings
- Excessive Shadow Casting Lights
- Evidence:
ProfileGPU: ShadowDepths 7.2ms. 14 movable shadow-casting lights detected in view. - Cause: Multiple overlapping flashlights and streetlamps are redrawing the scene depth pass too many times.
- Evidence:
Fix: Disable "Cast Shadows" on the 4 smallest fill lights; reduce attenuation radius on streetlamps from 1200 to 800.
- Expected gain: 2.5ms (High confidence).
- Cost and risk: Small effort. Minor change to light bounce in corners.
- Verification: Run
stat shadowrenderingbefore and after.
- Lumen Reflection Quality
- Evidence:
stat lumen: Reflection 4.8ms. - Cause: High surface complexity in the rear hangar is forcing expensive trace hits.
- Fix: Set
r.Lumen.Reflections.MaxRoughnessToTraceto 0.3 for this interior volume. - Expected gain: 1.2ms (Medium confidence).
- Cost and risk: Medium effort. Reflections on duller surfaces will fall back to probes.
- Evidence:
Quick wins
- Reduce
r.Shadow.CSM.MaxCascadesfrom 4 to 3. - Execute
r.Streaming.PoolSize 3000to prevent texture thrashing observed in logs.
Next steps
- Apply the shadow casting radius limits to the
BP_StreetLampactor. - Run the
Scripts/MegaLights/MEGALIGHTS_AB.batscript to compare classic shadow costs against the new MegaLights path. - Provide a new
ProfileGPUcapture after these changes.
Connects securely to your tools. The creator never sees your data.
About this skill
Stop guessing why your frame rates are dropping. This skill treats performance optimization as a diagnostic science, moving beyond generic advice to find the specific bottleneck dragging down your Unreal Engine 5 project. It identifies whether you are bound by the GPU, game thread, or RHI thread before proposing surgical fixes with projected millisecond gains.
What it does
- Thread triage analyzes
stat unitdata to determine if performance hits stem from draw calls, game logic, GPU load, or RHI submission. - Lighting audit evaluates Lumen, MegaLights, and shadow casting radii to find expensive movable lights and shadow depth costs.
- Asset profiling identifies oversized textures, high-instruction shaders, and meshes missing Nanite or LODs that bloat memory and GPU time.
- Logic bottlenecking scans Blueprints and C++ for expensive ticks, unnecessary actor replication, and high-frequency searches like
GetAllActorsOfClass. - Hitch detection investigates stuttering caused by shader compilation, garbage collection, or texture pool thrashing.
How it works
- Initial triage using
stat unitandstat unitgraphto identify the bottlenecked thread. - Evidence capture via console commands like
ProfileGPU,stat game, or Unreal Insights traces to isolate the specific cost. - Categorized hunt through lighting, materials, Niagara, or world partition settings to find the primary offender.
- Surgical proposal delivered as a ranked list of fixes including expected ms gain and implementation cost.
Frameworks & tools
Specifically designed for Unreal Engine 5 projects. Uses Unreal Insights, ProfileGPU, memreport, and built-in stat systems.
Why this beats prompting it yourself
Generic prompts suggest lowering settings for everyone. This skill uses specific engine commands to prove exactly which light, material, or Blueprint node is the problem, ensuring you don't compromise visual quality for a "fix" that doesn't target the actual bottleneck.
Use cases
- Optimizing night scenes where multiple shadow-casting movable lights or flashlights kill the GPU.
- Reducing hitching during level streaming or when new VFX trigger shader compilation spikes.
- Reclaiming game thread time by finding and disabling ticks on distant or invisible actors.
- Memory management for projects hitting texture pool limits or experiencing long load times.
Known limitations
Does not support editing C++ source during active builds. Blueprint logic changes are descriptive only. Optimization excludes specific protected project assets like live saves or core maps.
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.
Cannot edit source during builds. Uses isolated directories. Visual/logic changes are proposals. Optimized for UE5 stat systems. Does not delete core assets or live saves.
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 9 days ago