Does anyone know what ExtractRenderNodeQueue does and why it is killing performance?

Question

ExtractRenderNodeQueue shows up in the profiler between culling and rendering. Most of the time it takes .1 to .9 millisecond. However, if 25 (special) stones in my scene are enabled, it takes 20+ms and kills performance.

I have deleted everything out of my scene except light, camera, stones. There are 300 stones in the scene created from five different prefabs. Most of these stones cause no problems. However, there are 25 bad ones that, if enabled, cause this huge performance hit. There is nothing special about these stones. They are instances of the same prefab as the other stones. They use the same material. They are basic MeshFilter,MeshRenderer,Collider setup. The meshes range from 25 to 50 vertices. They are in a fairly ordinary location of the scene.

Does anyone have any idea what ExtractRenderNodeQueue does and why it might not like these stones?

Using Unity 5.4.1 on Windows building for Android.

Answer 1

Answer by Phong · Dec 23, 2016 at 06:34 PM

This appears to be caused by objects who's bound box center is not enclosed by light probes. My guess is Unity has a hard time finding good light probes to enclose these.

Add comment · Show 2 · Share

eDmitriy · Jul 10, 2017 at 12:54 PM 0

Share

Thank you, this helps. How did you find a source of the error? Profiler showing nothing.

MikeHergaarden · Sep 30, 2020 at 02:45 PM 0

Share

Thanks!

Can confirm this is the case. If some object is acting up it'll select some weird point instead of a correct lightprobe and ruin performance. For me this still happens on 2019.4.10 so I doubt Unity will fix this in the co$$anonymous$$g years

Does anyone know what ExtractRenderNodeQueue does and why it is killing performance?

1 Reply

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions