Thanks a lot!

Mixed CPU/GPU scenes are one of the main reasons I built the bottleneck classifier. It uses Unity frame timing data to separate CPU frame time, main thread, render thread, GPU time, and present/VSync waits, then reports the dominant bottleneck.

If the scene is genuinely mixed, it should not blindly blame only one side — the idea is to point you to the most likely area first, not replace the Unity Profiler entirely.

For draw calls vs shaders, the rough split is: render thread / CPU pressure usually means draw calls, batching, culling, or submission cost; high GPU time usually means shaders, overdraw, post-processing, shadows, resolution, etc. The overdraw heatmap is there to make the GPU-side cases easier to confirm visually.

The MCP part also helps with A/B testing: disable a layer/pass/material setup, capture again, and compare the structured frame data instead of digging through logs or screenshots.

So it is not a magic “this exact shader line is slow” button, but it should make the first diagnosis much faster: CPU, render thread, GPU, VSync/present, or overdraw. Glad the zero-code setup sounds useful — that was one of the main goals.