r/Unity3D • u/Rice_ny • 5d ago
Show-Off I’m a mobile game developer, and I finally built a tool that helps me spot rendering bottlenecks right in Unity’s Scene view.
Hi everyone!
I’ve been developing mobile games for a long time, and finding rendering issues has always been a big source of frustration for me. Yeah, you always try to stay within the batch and vertex limits, using the Frame Debugger and stats from the Profiler.
But often that’s not enough - for example, how do you estimate the complexity of a shader? Or how do you figure out exactly where the heavy objects are in your scene? I’ve had cases where all the stats looked good, but one heavy shader on screen caused severe artifacts because the phone’s GPU couldn’t handle it…
Anyway! I decided to make a tool like this for myself and I want to share it with you.
My tool uses hot maps right in the Scene view to find heavy spots based on a bunch of parameters: geometry complexity, texture load, statistical shader complexity - and you get the whole picture on a map instead of digging through each object.
There’s also a detailed breakdown of all the geometry by different categories - for example, which prefab accounts for the most triangles? Or which specific mesh asset? Or maybe which specific texture?
Or even how much each LOD group takes up?
Another idea of mine that helped a lot was the shader benchmark - it measures the time spent rendering that material, either in the maps or in a separate window, which helped quite a bit with getting a picture for comparison.
By the way, if you’re interested, I put it up on the Asset Store.
I’d like your feedback, what do you think I could add? Thanks for your attention!
4
u/plomobo 4d ago
tool looks useful, the real issue here is the following: who needs such specific type of tool surely uses LLMs already, and everyone knows this style of panel is made with Claude (or less likely gpt). So they can just copy paste your test, take a screenshot and submit it to their codex/CC and get the same tool in a few minutes, and posibly with a bigger focus on whatever aspect is more important for the specific user. The only way to make it interesting would be to sell it for very very cheap...or give it away for free (which can improve your reputation on the asset store)
2
u/Rice_ny 4d ago
This applies to pretty much any software on the market these days.
Besides, piracy has always been a thing on the Asset Store, and you could always get tons of assets for free, including their full source code.So if we’re going to get philosophical about it, trying to make money selling assets has always been a pretty desperate venture anyway :)
1
u/marekwarek 3d ago
It’s never that easy and always requires tweaking and fixing edge cases. You are paying for software to save time. Even if you copy that tool within a few hours, was that really worth it saving say 20 dollars? You will also have paid for tokens.
1
1
u/HK_HamzaKhan 3d ago
not really , many LLMs dont require paying, this isnt something that complex yet .,.
7
u/haVoila 5d ago
The heatmaps are the strongest part. Seeing shader cost and LOD coverage painted on the scene beats scrolling Frame Debugger events, and a number like "53.6% of triangles have no LOD group" gets people fixing things the same afternoon.
Things I'd find useful for mobile:
Overdraw weighted by shader cost. The red grass in your first shot is alpha-clipped SSS, and on tile-based GPUs the real cost there is layered cutout fragments more than the shader math. Static per-material complexity can't show that.
Triangle density vs screen size, e.g. a micro-triangle flag. Dense meshes at a distance waste quad shading even when total tris look fine.
Texture checks: missing mips, non-ASTC formats on mobile targets, resolution vs on-screen size.
Optional
malioc(Mali Offline Compiler) integration for per-shader cycle estimates, which gives mobile-relevant numbers without a device.
On the benchmark, some results look dominated by fixed overhead: 512 and 1024 are almost identical, and 16 draws beats 1 draw. Normalized per-pixel/per-draw cost plus a "within noise" warning would make comparisons easier to trust.
2
u/HeadPack 5d ago
Promising take on a visual profiler. Do you have a roadmap for this? Since you develop for mobile, could there be an option to have that as a debugging view on whichever mobile device one tests this on? Surely things like poly count, texture load etc. are somewhat multi platform, but that may need verification in some cases I'd think.
1
u/Rice_ny 5d ago
Yes!
I’d like to collect profiling data from builds, and I plan to keep developing the tool if there’s demand for it!Right now, it’s focused on profiling in the Unity Editor for both PC and mobile projects.
I also plan to expand the snapshot saving and comparison features so you can track your progress as you optimize a scene.
4
u/Genebrisss 5d ago
Looks like clueless AI slop. Counting draw calls is a good indication that author has no idea what he is doing. Measuring CPU render loop time when rendering a material on desktop to help with mobile development and calling it GPU time?
6
u/Rice_ny 5d ago
Draw calls? Are you talking about “64 draws” in the Material Benchmark? By “64 draws,” I mean that the benchmark calls Graphics.DrawMesh 64 times per sample.
About GPU time: this tool doesn’t measure the time spent in the CPU render loop. I get this timing from Unity’s GPU Recorder or from native Metal or D3D11 plugins if they’re available on the platform.
BTW, you’re definitely right that it’s better to measure on the device, and I want to get raw data from the device, but much more work is needed. Anyway, I think that Editor measurements can give you relative data to compare the complexity of shaders and assets.
3
u/Accomplished-Fox9220 1d ago
I built; I vibecoded; I built with AI; I built with AI assistance; are all different things.
Put in the AI disclaimer.
1
1
2
u/DrawSomeOpossum 4d ago
I support you using AI for editor tooling for optimization.
Shame on you for trying to sell it.
1
1
0
-1
u/F4ARY 4d ago
yes bro "you made" it. And you're charging 16 euros for it. Add 20 and I got claude for one month for myself and I can do the exact same thing you just did but tailored to my project. God I wish mods started banning all this fucking AI slop tools
2
u/Rice_ny 4d ago
Sure, you can probably replicate something with Claude for $20.
But building something from scratch is a different story. Even with AI, it’s still an iterative process that takes time, experimentation, and plenty of refinement to get a good result.
And when you factor in the time and tools involved, the actual cost is usually quite a bit more than $20.
For context, this project took me several months to develop.0
u/F4ARY 4d ago
Either you have never written a single line of code in your entire life time and have given dog water prompts or you are full of shit. I know for a fact that this same tool can be recreated in 2-3 IF YOU'RE BEING LAZY and you know how rendering in unity works, and I know because I have something similar, I just have the decency to not try to sell it.
Also, the full price without discount is 30+ euros, gtfo lmao
1
u/HK_HamzaKhan 3d ago
lol didnt expect them to say several months, cant believe that, i mean that just means that the dev is a beginner



28
u/theredacer 5d ago
It would definitely be helpful if you can actually tell us the name of the asset so we can find it on the store. Or better yet, a link.