Sign in to follow this  
Quat

Optimizing Editor

Recommended Posts

Hello,

I need to optimize our level editor. I have found that the application CPU side is actually the bottleneck, not the GPU. The problem is all the API/Draw submissions using DX9.

In the editor, we do not really have "static" geometry in the typical sense because the user can select individual objects and edit them. We don't merge objects with the same materials until export to minimize Draw calls.

I'm wondering how editor authors handle this. Is it best to have a cost on insert/deletion of objects and group objects with the same material into one mesh? I might also try using the instancing API.

Share this post


Link to post
Share on other sites
You need to design your engine to support both cases:
- one where objects are real static objects
- and the other for dynamic objects (your Editor "static" objects should fall in this group, but in the game these static objects will be rendered by the real static objects path in your engine)

(It goes without saying that your engine is used both by the game and the editor in this scenario)

Grouping objects of similar material into 1 mesh is the way to go. But remember to send their transform matrices in your shader and index them there (or you could pre-transform them before you do add/merge them into the single mesh).

Hope this helps.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this