r_lockView debug cvar

[stgatilov]

For easier inspection of various culling algorithms, I created a new debug cvar.

It fixes the camera position that renderer frontend uses for culling, but allows player to fly around and see the same objects from different view point. Don't expect perfectly valid/sane picture, but I think it reliably shows which objects are sent to OpenGL for rendering.

Here is the demonstration (bottom-left is clipped away in this video, but I hope it is clear anyway):

It will be available in the next dev build.
Maybe someone will find it useful for analyzing overdraw?

P.S. Aside from that, "r_showtris 2" + "r_useScissor 0" should be useful for overdraw analysis too.
It is questionable though whether you should disable r_useScissor in this case...

 

[datiswous]

Wow, this is amazing. I think it's also good for learning and understanding how it works.

[nbohr1more]

Look pretty useful to me!

On a related note, I think we need to resurrect r_showShadows.

Biker has been testing maps in both 2.12 and 2.11 and 2.12 always shows higher shadow tris in r_showprimitives even though 2.12 usually runs the missions better.

[stgatilov]

4 hours ago, nbohr1more said:

Biker has been testing maps in both 2.12 and 2.11 and 2.12 always shows higher shadow tris in r_showprimitives even though 2.12 usually runs the missions better.

That's because these counters are updated by calling special wrappers around draw calls.
I think the new backend does not call it everywhere --- maybe I changed something here.

So I'm afraid the performance counters are as reliable as we care about them when doing changed to the renderer... which is not great at this moment.