Collider Debug Draw Performance

Code (CSharp):

1. Debug Draw rendering is now significantly faster and should be able to handle much more complicated scenes with ease.

What is a "much more complicated scene"? I have a scene with MeshColliders that should display ~500k tris and is completly unuseable for me as it locks the whole editor up.

While the scene renders with 100fps without the debug display

and enabling it causes unity to almost freeze

where

I clearlyget less than the displayed 22 FPS, as it feels like it takkes 500ms to render a single frame, which would be more like 2FPS.

 

Try a terrain collider. I actually have to force quit Unity if I forget to disable our terrain collider before debugging that's how slow it is.

 

Hey all! Unfortunately Debug display is not finished yet, we've made some progress and it's still slower than we'd like it to be, but it's also not correct in all cases. We'll definitely be looking into it more in the future releases.

One alternative I can suggest for now is to temporarily switch to Havok and use Havok Visual Debugger to review your colliders and stuff.

 

Add in the ability to select which collider types to display. Not only provides a work around for the worst cases right now that can bring down Unity, but it's just generally useful. I hacked it in at one time but got tired of updating it on every release, so now I just do a one line hack to disable terrains.