Hello.
I’d like to request a feature to be able to filter out certain methods from the profiler; for example, RClick on a method in the hierarchy → Hide. This entry should be then hidden from the graph and grayed out in the hierarchy (perhaps moved to the end regardless of values).
Why do I want this?
Sometimes when profiling, you get tons of calls, which will not be present in the final version of the game.
Let me give you an example:
You have a game, which is using URP. For some reason, URP is filled with ProfilerScope calls. Then, you look at the graph and find out, that your rendering is taking up 87% of the whole games performance. And what in the rendering? ProfilingScope.ctor(). Since you can profile only a development build, you can not get rid of this call. There is no #if you can call to disable this. Since it is inside the Unity’s package registry, you can’t add one either. What does this lead to? Incorrect profiling information in 100% of the time when using URP.
If I could hide the whole highlighted part of the graph, I could finally see where exactly is the problem, without having to click thru every frame, manually going thru the hierarchy.