Entity manager size

Cris Kop · 2014-07-13T18:53:46

Hi all, While working out the design of my entity manager (yet to be implemented) for my 3d engine, something got me thinking. Up till this moment I thought I needed to redo my renderqueue, to make it possible to add extra mesh instances (linked to game objects), sort everything again etc., after changes are done in the entitymanager. But then I thought, let's say you have a level of a game, you will now on forehand how many game objects will be in the level, same for 'bad guys'/ enemies etc. Ok, there will be less, depending on the state of the game objects. But not taking mesh instances into account in a sorted list is easy (just leave out the ones that are not visible, for rendering, culling, physics etc). In short; do you see reasons why to have both an entity manager and renderqueue that are able to add new game objects (entities) / mesh instances (renderqueue)? The only reason I could think of is having a multiplayer game where new players are added. On the other hand, you can then take a 'max' of players and use these 'slots' so you don't need to add anyway (just 'enable'/ make them visible when needed). Any input is appreciated, since it will help me decide if redoing my renderqueue is worth all the effort.

Graphics and GPU Programming Programming

Started by cozzie July 12, 2014 08:55 AM

9 comments, last by cozzie 9 years, 9 months ago

cozzie

5,063

Author

July 13, 2014 06:53 PM

Thanks hodgman. That confirms my feeling that it's good to think ahead and have more mesh instance indices with groups of objects. So I can go through then for different purposes (like the ones you mentioned).

Crealysm game & engine development: http://www.crealysm.com

Looking for a passionate, disciplined and structured producer? PM me

Entity manager size

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Entity manager size

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines