next »

[tague]

So, I've seen a lot of debate online about whether scene graphs are some sort of hellish monster you should tear out of your engine or perfectly fine, and I'm a little confused about how you can not use one - as a general standard, don't many 3D assets used in games consist of multiple parented meshes w/ different materials? Wouldn't handling that kind of asset require some sort of scene graph, even if you're just keeping a graph per renderable component / "model" instead of one for the entire game and all entities?

[Schrompf]

Today's hot shit, as far as people even write a renderer themself anymore, is an Entity Component System. In this, the stuff to draw is a simple array. From my personal experience, this is almost always enough. There are some parent/child relations, but they're rare and thus better modeled via separate code that you can employ where necessary.

[tague]

I have been working with an ECS, I'm more so concerned about the model layer - for example, a "Player" entity might have a character model which consists of some main "body" mes, and one or more other meshes parented to it such as clothing, accessories, the eyeballs, etc.